# ObserverJVM Subsystem Messages

The ObserverJVM1.0 catalog contains messages in the range BEA2015400 - BEA2015499.
BEA-2015400 | Info: The bundle name has successfully started.
Description | The bundle name has successfully been started by the OSGi framework.
Cause | Normal operation.
Action | No Action Required.
BEA-2015401 | Info: The LOC service name has been prepared.
Description | The LOC service name has successfully been prepared by the OSGi framework of the LOC processs.
Cause | Normal operation.
Action | No Action Required.
BEA-2015402 | Info: The LOC service name has been activated
Description | The LOC service name has successfully been activated by the OSGi framework of the LOC process.
Cause | Normal operation.
Action | No Action Required.
BEA-2015403 | Warning: Attempt to collect an undefined attribute: name.
Description | The attribute that was requested to be collected: "name" is not serviced by the ResourcePoolObserver. Skipping.
Cause | This should not happen. Invalid attributes should be validated and removed by the logic prior to any attempts to collect them.
Action | The product will continue to function correctly, but with a slight additional overhead and additional log messages. It would be helpful if you notify BEA support so we will be sure to fix this issue as soon as possible.
BEA-2015404 | Error: Failed to connect to LVM stat server for process: jvm.
Description | A request was made to access the LVM stat server but that server was unavailable. Any requested LVM stat values will be returned as 0 until a connection can be established.
Cause | The LVM stat server is unavailable.
Action | It should be determined why the server is unavailable. As a possible aid, setting the JVMObserver debug flag will cause a stack trace to be printed whenever this error occurs.
BEA-2015499 | Info: The bundle name has successfully been stopped.
Description | The bundle name has successfully been stopped by the OSGi framework.
Cause | Normal operation.
Action | No action required.