WebSphere Process Server messages     Operating Systems: All supported

CEIES

CEIES0003W: The event server failed to initialize a JMS destination for an event group because the specified JMS destination could not be found in JNDI. Event group name: {0} JMS connection factory JNDI name: {1} JMS destination JNDI name: {2} Context: {3}
Problem

The event server failed to initialize a JMS destination for an event group. The event server will not use the destination when distributing event notifications. This failure does not stop the event server from publishing event notifications to other JMS destinations assigned to the event group. The event server will use all valid JMS destinations assigned to an event group when distributing event notifications for the event group.

CEIES0004E: No event notifications were sent because the event server could not connect to the JMS destination. Event group name: {0} JMS connection factory JNDI name: {1} JMS destination JNDI name: {2}
Problem

Before sending event notifications, the event server tries to connect to all JMS destinations for any event groups that an event matches. If during this processing one of the connection attempts fail, the event notification is not sent to any of the matching event groups and the transaction is marked for rollback.

CEIES0005E: The event server failed to create a JMS message for the event notification being sent to the JMS destination. Event group name: {0} Events: {1} JMS connection factory JNDI name: {2} JMS destination JNDI name: {3}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0006E: The event server failed to publish the event notification to the JMS destination. Event group name: {0} Events: {1} JMS Message: {2} JMS connection factory JNDI name: {3} JMS destination JNDI name: {4}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0007W: The event server failed to disconnect from the JMS destination. Event group name: {0} JMS connection factory JNDI name: {1} JMS destination JNDI name: {2} Exception message: {3}
Problem

No recovery is done because the JMS destination is closed.

CEIES0008E: The event server failed to store any events in the data store because the global instance ID in an event already exists in the data store. Exception message: {0} Events: {1}
Problem

The global instance ID uniquely identifies the event in the data store. It is assumed that one of the passed events is a duplicate of an event that already exists in the data store. Therefore, the events are not processed, and the current transaction is marked for rollback.

CEIES0009E: The event server failed to store any events in the data store because the data store could not be found using the specified JNDI name. JNDI name: {0} Exception message: {1} Events: {2}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0010E: The event server failed to store any events in the data store referenced by the JNDI name because the configured data store threw an exception. JNDI name: {0} Exception message: {1} Events: {2}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0011E: The event server failed to distribute an event notification. Exception message: {0} Events: {1}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0012E: The JMS message did not contain a value in the JMS message type property. JMS message: {0}
Problem

See message.

CEIES0013E: The JMS message did not contain an event. JMS message: {0}
Problem

See message.

CEIES0014W: The JMS message was not processed because the value in the JMS message type property is not valid. JMS message: {0}
Problem

See message.

CEIES0015E: The creation of a JMS message for an event batch failed. Events: {0}
Problem

The JMS provider threw an exception when the event server tried to create a JMS message to contain an event notification. Because the event server was unable to send the event notification for a single event all notifications will be stopped. The global transaction is marked for roll back, so if persistence is enabled the events are not stored in the persistent store.

CEIES0016E: The notification helper failed to set the event selector because the event selector is not in the correct format. Event selector: {0} Exception message: {1}
Problem

See message.

CEIES0018E: The event server failed to process an event batch because the event server does not support the event version specified in the event. Global Instance Id: {0} Event version: {1} Event server version: {2} Events: {3}
Problem

The events are not processed, and the current transaction is marked for rollback.

CEIES0019E: The {0} event access method failed because the data store component is not enabled.
Problem

See message.

CEIES0021E: The configured data store could not be found using the specified JNDI name. JNDI name: {0} Context: {1}
Problem

See message.

CEIES0023E: The event server failed to create an instance of the configured data store because the data store event version and the event server event version are not compatible. Data store version: {0} Event server version: {1}
Problem

See message.

CEIES0024E: The event server failed to create an instance of the configured data store because the component metadata could not be retrieved from the data store.
Problem

See message.

CEIES0025E: The event server failed to create an instance of the configured data store.
Problem

See message.

CEIES0026E: The configuration of the event server is not valid because the data store is enabled but the data store JNDI name is null. It is not valid to enable the data store and to have a null data store JNDI name. Event server JNDI name: {0} Event server configuration object: {1}
Problem

See message.

CEIES0027E: The configuration object for the event server at the specified JNDI name could not be found. JNDI name: {0}
Problem

See message.

CEIES0028E: The configuration object for the event server could not be found when accessing the configuration of event group list at the specified JNDI name. JNDI name: {0}
Problem

See message.

CEIES0029E: The reference obtained from the specified JNDI name is not a reference to a notification helper factory. JNDI name: {0}
Problem

An application attempted to look up a notification helper factory from a JNDI namespace, but the object found in the specified location was not a reference to a notification helper factory.

CEIES0030W: The event server failed to decode the JMS message because the message does not contain a valid message type. JMS message: {1} Message type: {0}
Problem

The message is not processed, and the current transaction is marked for rollback causing the message to be returned to the JMS provider for handling.

CEIES0031E: The event server failed to retrieve an event from the JMS message. JMS message: {1} Exception message: {0}
Problem

The event is not processed, and the current transaction is marked for rollback.

CEIES0032E: The event server failed to process a JMS message. Exception message: {0} JMS Message: {1}
Problem

The JMS message is not processed, and the current transaction is marked for rollback.

CEIES0033E: The event server failed to process the JMS message. JMS message: {1} Exception message: {0}
Problem

The message is not processed, and the current transaction is marked for rollback.

CEIES0034E: The event server failed to create an instance of the event bus because it could not be found using the specified JNDI name. JNDI name: {0} Context: {1}
Problem

See message.

CEIES0035E: The event server failed to create an instance of the event bus.
Problem

See message.

CEIES0036E: The event server failed to create an instance of the event bus. The event was not persisted, and it was not published to any message consumers. Event: {2} Exception message: {1}
Problem

The event is not processed, and the current transaction is marked for rollback.

CEIES0042E: The notification helper failed to retrieve the JMS destinations for the specified event group because the event group configuration could not be found in JNDI. Event group: {0} JNDI name: {1}
Problem

See message.

CEIES0044E: The event server failed to create an instance of event distribution because it could not be found using the specified JNDI name. JNDI name: {0} Context: {1}
Problem

See message.

CEIES0045E: The event server failed to create an instance of event distribution.
Problem

See message.

CEIES0048E: The event group is not defined in the event group list that the event server instance is using. Event group: {0}
Problem

See message.

CEIES0050E: The event server failed to initialize an event group because the event selector for the event group is not in the correct format. Event group name: {0} Event selector: {1} Exception message: {2}
Problem

The event server continues to operate normally, but the event server does not send event notifications to the specified event group.

CEIES0051E: The event server received an exception when initializing an event group. Event group name: {0} Exception message: {1}
Problem

The event server continues to operate normally, but the event server does not send event notifications to the specified event group.

CEIES0052E: The event server failed to publish the event notification to a JMS destination in the event group. Event group name: {0} Event: {1} Exception message: {2}
Problem

The event server attempts to publish the event notification to other JMS destinations.

CEIES0053E: The event server failed to retrieve a needed configuration object. Configuration object class: {0}
Problem

See message.

CEIES0054E: The notification helper received an exception while looking up the event server in JNDI.
Problem

See message.

CEIES0056E: The notification helper failed to locate the event bus in JNDI.
Problem

See message.

CEIES0057E: The data store returned more than the requested number of events for an event query. Requested number of events: {0} Returned number of events: {1} JNDI name: {2}
Problem

See message.

CEIES0058E: The eventExists event access method failed. Event group: {0} Event selector: {1} Exception message: {2}
Problem

See message.

CEIES0059E: The purgeEvents event access method failed. Event group: {0} Event selector: {1} Transaction size: {2} Number events purged: {3}
Problem

See message.

CEIES0060E: The queryEventByGlobalInstanceId event access method failed. Global instance ID: {0} Exception message: {1}
Problem

See message.

CEIES0061E: The queryEventsByAssociation event access method failed. Association Type: {0} Global instance ID: {1} Exception message: {2}
Problem

See message.

CEIES0062E: The queryEventsByEventGroup event access method failed. Event group: {0} Event selector: {1} Ascending Order: {2} Exception message: {3}
Problem

See message.

CEIES0063E: The event access method queryEventsByEventGroup failed. Event group: {0} Event selector: {1} Ascending Order: {2} Maximum Number: {3} Exception message: {4}
Problem

See message.

CEIES0064E: The notification helper failed to read the event group configuration from the event server. Event group: {0}
Problem

See message.

CEIES0065E: The notification helper failed to read an event from the JMS message because the JMS message type is not known. JMS message: {0}
Problem

See message.

CEIES0066E: The event server failed to initialize an event group. The specified JNDI name does not point to an instance of the correct JMS class. Event group name: {0} JNDI name: {1} JMS class: {2}
Problem

The event server failed to initialize an event group for distribution of events, and the event server does not use the event group when distributing event notifications. This failure does not stop the event server from processing events. The event server uses all valid event groups when distributing event notifications.

CEIES0067E: The event update failed because the configured data store does not support event updates. Data Store JNDI name: {0}
Problem

See message.

CEIES0068E: The updateEvents event access method failed. Event Change Requests: {0} Exception message: {1}
Problem

See message.

CEIES0070W: A profile property was specified but did not have the expected type. The property was ignored. Profile property name: {0} Specified type: {1} Expected type: {2}
Problem

See message.

CEIES0071E: The event service was unable to retrieve events from the XML string. XML String: {0}
Problem

The event service encountered an exception when trying to retrieve events from the received XML string. This could mean that the XML data was not valid or was corrupted.

CEIES0072E: Two events with the global instance identifier {0} have been submitted.First event: {1}Second event: {2}
Problem

Multiple events with the same global instance identifier were submitted as part of a batch. Each event instance must have a unique global instance identifier. All of the events in the submitted batch have been rejected.

User response

Make sure each event has a unique global instance identifier and submit the batch again.

CEIES0073E: The {0} event access method failed because the data store component is not enabled for event group {1}.
Problem

A query operation was attempted for the specified event group, but persistence is not enabled in the configuration settings for that event group.

CEIES0074E: The configuration object for the event service could not be found when accessing the configuration of data store profile at the specified JNDI name.JNDI name:{0}
Problem

See message.

CEIES0075I: Successfully initialized custom event selector filter .Class :{0}
Problem

See message.

CEIES0076E: Failure to initialize custom event selector filter .Class :{0}
Problem

See message.

Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 10:01:53 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.ws.61.cei.messages.doc/com.ibm.events.messages.CeiEventServerMessages.html

© Copyright IBM Corporation 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)