CEMEM0001E: The object associated with the emitter factory JNDI lookup is null.
Explanation: "null" has been bound into JNDI.
User Action: Consult the message log.

 

CEMEM0002E: An exception occurred while obtaining an emitter factory. See the nested exception for more information: {0}
Explanation: An error occurred while locking the emitter factory.
User Action: Check the nested exception and consult the message log.

 

CEMEM0003E: The specified emitter factory was not found in JNDI. See the nested exception for more information: {0}
Explanation: An error occurred with the event infrastructure.
User Action: Consult the message log.

 

CEMEM0004E: The object associated with the event factory registered in JNDI is incorrect. See the nested exception for more information: {0}
Explanation: The wrong object has been bound into JNDI.
User Action: Run the application with the correct object bound into JNDI.

 

CEMEM0005E: An exception occurred while obtaining an emitter. See the nested exception for more information: {0}
Explanation: An exception occurred while calling the emitter factory.
User Action: Check the message log.

 

CEMEM0010E: The value of property "{0}" cannot be reset or cleared by this process.
Explanation: The WebSphere work area service only allows a property to be reset or cleared by the process that created it.
User Action: Change the application so that properties are reset or cleared only by the originating process.

 

CEMEM0014E: An error occurred while parsing this imported XML: {0}
Explanation: The XML does not conform to the required XSD schema. A class loader error might have occurred.
User Action: Check that the XML is valid by reading it into a browser. It might have been corrupted.

 

CEMEM1001I: The events service started successfully.
Explanation: The events service started successfully as part of the normal server startup process.
User Action: None.

 

CEMEM1002E: The events service failed to start.
Explanation: The events service encountered errors during startup of the server.
User Action: See the error log to determine the problems encountered during startup. Verify that all of the necessary classes are in the class path and that the JNDI is available.