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. |
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. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
No recovery is done because the JMS destination is closed. |
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. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
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. |
Problem |
See message. |
Problem |
The events are not processed, and the current transaction is marked for rollback. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
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. |
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. |
Problem |
The event is not processed, and the current transaction is marked for rollback. |
Problem |
The JMS message is not processed, and the current transaction is marked for rollback. |
Problem |
The message is not processed, and the current transaction is marked for rollback. |
Problem |
See message. |
Problem |
See message. |
Problem |
The event is not processed, and the current transaction is marked for rollback. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
The event server continues to operate normally, but the event server does not send event notifications to the specified event group. |
Problem |
The event server continues to operate normally, but the event server does not send event notifications to the specified event group. |
Problem |
The event server attempts to publish the event notification to other JMS destinations. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
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. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
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. |
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. |
Problem |
A query operation was attempted for the specified event group, but persistence is not enabled in the configuration settings for that event group. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |