Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Integration Server Built-In Services | Event Folder | Summary of Elements in this Folder | pub.event:jmsReceiveErrorEvent
 
pub.event:jmsReceiveErrorEvent
WmPublic. Specification for a JMS retrieval failure event handler.
Input Parameters
triggerName
String Specifies the name of the JMS trigger that executed the trigger service for which the JMS retrieval failure event occurred.
triggerDestinationIndex
java.lang.Integer Specifies the index for the destination from which the JMS trigger receives messages. A JMS trigger that specifies a join type can listen for messages from multiple destinations. The first destination listed has an index of 0, the second destination listed has an indices of 1, etc.
deliveryCount
java.lang.Integer Number of times the JMS provider delivered the message to the JMS trigger at the time the event occurred.
time
String Date and time that the event occurred, in the format yyyy/MM/dd HH:mm:ss.SS
exceptionClass
String Name of the class that caused the failure. This may be useful to determine programmatically why the error occurred.
exceptionMessage
String Message contained in the exception.
data
Document A document (IData) containing the JMS message being processed when the error occurred.
Key
Description
JMSMessage
A document reference (IData) to the pub.jms:JMSMessage document type.
Output Parameters
None
Usage Notes
A JMS retrieval failure event occurs in the following situations:
*A trigger service executed by a JMS trigger throws a non-transient error and the watt.server.jms.trigger.raiseEventOnException property is set to true (the default).
*A trigger service associated with a JMS trigger ends because of a transient error, all retry attempts have been made, and the JMS trigger is configured to throw an exception on retry failure. In addition, the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
*The maximum delivery count from the JMS provider has been met for the message and the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
The watt.server.jms.trigger.maxDeliveryCountproperty specifies the maximum number of times the JMS provider can deliver a message to Integration Server. The default is 100. In a JMS message, the property JMSXDeliveryCount specifies the number of times the JMS provider delivered the message. Most JMS providers set this value.
*While performing exactly-once processing, the connection to the document history database is unavailable, and transient error handling for the JMS trigger is configured to Throw exception (non-transacted JMS trigger) or Recover only (transacted JMS trigger). In addition, the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
*While performing exactly-once processing, the document resolver service ends with an ISRuntimeException, and transient error handling for the JMS trigger is configured to Throw exception (non-transacted JMS trigger) or Recover only (transacted JMS trigger). In addition, the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
*While performing exactly-once processing, the document resolver service ends with an exception other than an ISRuntimeException. In addition, the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
Remember to register your event handler with the Event Manager.
Use the watt.server.event.jmsRetrievalError.async server parameter to indicate whether event handlers for JMS retrieval failure events are invoked synchronously or asynchronously. When this parameter is set to true, Integration Server invokes the event handlers that subscribe to JMS retrieval failure events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to the JMS retrieval failure events synchronously. The default is true (asynchronous).
See Also
pub.jms:JMSMessage