Licensed Materials - Property of IBM (C)Copyright IBM Corporation 2004,2005. All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 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: event_group_name
JMS connection factory JNDI name: destination_factory_jndi_name
JMS destination JNDI name: destination_jndi_name
Context: context_name

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.

Ensure that the JNDI names are correct for the following resources as appropriate:

  • Topic connection factory
  • Topic
  • Queue connection factory
  • Queue
 No event notifications were sent because the event server could not connect to the JMS destination.
Event group name: event_group_name
JMS connection factory JNDI name: destination_factory_jndi_name
JMS destination JNDI name: destination_jndi_name

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.

Ensure that the event group definition contains a valid JMS destination. Also, ensure that the JMS provider is working properly.

The event server failed to create a JMS message for the event notification being sent to the JMS destination.
Event group name: event_group_name
Events: event_instances
JMS connection factory JNDI name: destination_factory_jndi_name
JMS destination JNDI name: destination_jndi_name

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

Ensure that the event group definition contains a valid JMS destination.

The event server failed to publish the event notification to the JMS destination.
Event group name: event_group_name
Events: event_instances
JMS Message: event_instance
JMS connection factory JNDI name: destination_factory_jndi_name
JMS destination JNDI name: destination_jndi_name

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

Ensure that the event group definition contains a valid JMS destination.

The event server failed to disconnect from the JMS destination.
Event group name: event_group_name
JMS connection factory JNDI name: destination_factory_jndi_name
JMS destination JNDI name: destination_jndi_name
Exception message: exception_message

No recovery is done because the JMS destination is closed.

If this is a recurring problem, ensure that the JMS provider is working properly.

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: exception_message
Events: event_list

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.

If this is a recurring problem, inspect the source of the event to determine if the source is creating duplicate global instance IDs.

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: data_store_jndi_name
Exception message: exception_message
Events: event_list

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

Ensure that the data store exists at the specified JNDI name. Also, see the exception message for additional information about the cause of the problem.

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: data_store_jndi_name
Exception message: exception_message
Events: event_list

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

See the exception message for additional information about the cause of the problem.

The event server failed to distribute an event notification.
Exception message: exception_message
Events: event_list

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

See the exception message for additional information about the cause of the problem.

The JMS message did not contain a value in the JMS message type property.
JMS message: message

See message.

If this is a recurring problem, inspect the source of the event to determine if the source is creating JMS messages that are not valid.

The JMS message did not contain an event.
JMS message: message

See message.

If this is a recurring problem, inspect the source of the event to determine if the source is creating JMS messages that are not valid.

The JMS message was not processed because the value in the JMS message type property is not valid.
JMS message: message

See message.

If this is a recurring problem, inspect the source of the event to determine if the source is creating JMS messages that are not valid.

The creation of a JMS message for an event batch failed.
Events: event_list

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.

See the exception message for additional information about the cause of the problem.

The notification helper failed to set the event selector because the event selector is not in the correct format.
Event selector: event_selector
Exception message: exception_message

See message.

Ensure that the calling application is passing a valid event selector.

Event selectors are specifed by an XPath expression which must be of the form CommonBaseEvent[...]. If the event selector does not start with CommonBaseEvent or if it contains values that are not valid, the event selector is rejected.

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: global_instance_ID
Event version: event_version
Event server version: event_server_version
Events: event_list

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

If this is a recurring problem, inspect the source of the event to determine the cause of the problem.

The method event access method failed because the data store component is not enabled.

See message.

If the data store should be enabled, modify the event server profile by selecting Enable Data Store .

The configured data store could not be found using the specified JNDI name.
JNDI name: jndi_name
Context: context

See message.

Ensure that the correct JNDI name is configured for the data store. Also, ensure that the data store is deployed to the specified JNDI name.

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: datastore_cbe_version
Event server version: eventserver_cbe_version

See message.

The event server must use a data store that supports the same event version.

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.

See message.

See the exception message for additional information about the cause of the problem.

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

See message.

See the exception message for additional information about the cause of the problem.

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: jndi_name
Event server configuration object: configuration_object

See message.

Update the configuration of the event server profile to either disable the data store or to provide a valid data store JNDI name.

The configuration object for the event server at the specified JNDI name could not be found.
JNDI name: jndi_name

See message.

Verify that the Common Event Infrastructure service started. Also, ensure that the failing enterprise bean has a correct EJB reference in the deployment descriptor to the event server configuration object.

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: jndi_name

See message.

Verify that the Common Event Infrastructure service started. Also, ensure that the failing enterprise bean has a correct EJB reference in the deployment descriptor to the event server configuration object.

The reference obtained from the specified JNDI name is not a reference to a notification helper factory.
JNDI name: jndi_name

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.

See the exception message for additional information about the cause of the problem.

The event server failed to decode the JMS message because the message does not contain a valid message type.
JMS message: message
Message type: message_type

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.

If this is a recurring problem, check the source of the message to determine the cause of the problem.

The event server failed to retrieve an event from the JMS message.
JMS message: message
Exception message: exception_message

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

See the exception message for additional information about the cause of the problem.

The event server failed to process a JMS message.
Exception message: exception_message
JMS Message: message

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

See the exception message for additional information about the cause of the problem.

The event server failed to process the JMS message.
JMS message: message
Exception message: exception_message

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

See the exception message for additional information about the cause of the problem.

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: jndi_name
Context: context

See message.

Ensure that the event bus message driven bean has a correct EJB reference in the deployment descriptor to the event bus.

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

See message.

See the exception message for additional information about the cause of the problem.

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: event_instance
Exception message: exception_message

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

See the exception message for additional information about the cause of the problem.

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: event_group
JNDI name: jndi_name

See message.

Ensure that the event group is configured correctly.

 The event server failed to create an instance of event distribution because it could not be found using the specified JNDI name.
JNDI name: jndi_name
Context: context

See message.

Ensure that the event bus has a correct EJB reference in the deployment descriptor to the event distribution.

The event server failed to create an instance of event distribution.

See message.

See the exception message for additional information about the cause of the problem.

The event group is not defined in the event group list that the event server instance is using.
Event group: event_group_name

See message.

Ensure that the event group is defined for this instance of the event server. Also, restart the application server that is running the instance of the event server to incorporate the latest configuration.

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: event_group_name
Event selector: event_selector
Exception message: exception_message

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

Event selectors are specifed by an XPath expression which must be of the form CommonBaseEvent[...]. If the event selector does not start with CommonBaseEvent or if it contains values that are not valid, the event selector is rejected.

Correct the event selector for the specified event group to match the CommonBaseEvent[...] format. Also, restart the application server that is running the instance of the event server to incorporate the latest configuration.

The event server received an exception when initializing an event group.
Event group name: event_group_name
Exception message: exception_message

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

See the exception message for additional information about the cause of the problem.

The event server failed to publish the event notification to a JMS destination in the event group.
Event group name: event_group_name
Event: event_instance
Exception message: exception_message

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

See the exception message for additional information about the cause of the problem.

The event server failed to retrieve a needed configuration object.
Configuration object class: configuration_classname

See message.

See the exception message for additional information about the cause of the problem.

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

See message.

Verify that the Common Event Infrastructure service started. Also, see the exception message for additional information about the cause of the problem.

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

See message.

Verify that the Common Event Infrastructure service started.

The data store returned more than the requested number of events for an event query.
Requested number of events: maximum_number
Returned number of events: number_returned
JNDI name: data_store_jndi_name

See message.

Contact the provider of the data store to correct the error.

The eventExists event access method failed.
Event group: event_group
Event selector: event_selector
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

The purgeEvents event access method failed.
Event group: event_group
Event selector: event_selector
Transaction size: transaction_size
Number events purged: number_events_purged

See message.

See the exception message for additional information about the cause of the problem.

The queryEventByGlobalInstanceId event access method failed.
Global instance ID: global_instance_id
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

The queryEventsByAssociation event access method failed.
Association Type: association_type
Global instance ID: global_instance_id
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

The queryEventsByEventGroup event access method failed.
Event group: event_group
Event selector: event_selector
Ascending Order: ascending_order
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

The event access method queryEventsByEventGroup failed.
Event group: event_group
Event selector: event_selector
Ascending Order: ascending_order
Maximum Number: maximum_number
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

The notification helper failed to read the event group configuration from the event server.
Event group: event_group

See message.

Verify that the Common Event Infrastructure service started. See the exception message for additional information about the cause of the problem.

The notification helper failed to read an event from the JMS message because the JMS message type is not known.
JMS message: jms_message

See message.

The message is not processed by the notification helper because the notification helper cannot determine if the message contains an event.

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: event_group_name
JNDI name: jndi_name
JMS class: jms_class

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.

Ensure that the JNDI names are correct for the following resources:

  • Topic connection factory
  • Topic
  • Queue connection factory
  • Queue
 The event update failed because the configured data store does not support event updates.
Data Store JNDI name: jndi_name

See message.

Upgrade the data store to support event updates.

The updateEvents event access method failed.
Event Change Requests: event_change_requests
Exception message: exception_message

See message.

See the exception message for additional information about the cause of the problem.

A profile property was specified but did not have the expected type. The property was ignored.
Profile property name: property_name
Specified type: specified_type
Expected type: expected_type

See message.

Specify the property with the correct type.

The event service was unable to retrieve events from the XML string.
XML String: xml_string

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.

See the exception message for more information about the cause of the problem. If this is a recurring problem, inspect the source of the XML event string to make sure the source is creating valid XML.

 Two events with the global instance identifier global_id have been submitted.
First event: event1
Second event: event2

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.

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

 The method event access method failed because the data store component is not enabled for event group method.

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

If query operations need to be supported, modify the configuration of the event group to enable persistence. Otherwise, specify a different event group for the query.

 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:jndi_name

See message.

Verify that the Common Event Infrastructure service started. Also, ensure that the failing enterprise bean has a correct EJB reference in the deployment descriptor to the event server configuration object.

 Successfully initialized custom event selector filter .
Class :class_name

See message.

Successfully initialized custom event selector filter.

 Failure to initialize custom event selector filter .
Class :class_name

See message.

Verify if the class is added at the event group properties. Verify that the corect class name is added at the event group properties. Verify if the class is in the correct classpath.