Review possible problems with nodes using JMS transport.
Use Activity log as the first step in diagnosing a problem when something unexpected happens in a JMS message flow. Activity log shows recent activities in your message flows and associated external resources, and can show you at a high level any problems with your JMS resources. You can also view the event log for information about errors that occur.
In all cases of error, if the underlying cause is a JMS exception that has been thrown by the JMS provider, the broker BIP event message includes the text message from the JMS exception to help diagnosis.
If a message cannot be processed by the JMS input node, or has been rolled back as part of an XA coordinated transaction, the message is backed out to the source destination. The message is then delivered again to the input node.
Property | Description |
---|---|
Backout destination | This property specifies a JMS destination to
which backed out messages are routed if the JMS message property JMSX_DeliveryCount,
which is set by the JMS provider, exceeds the backout threshold. The JMS destination must be applicable to the message model being used by the node; for example, if a subscription topic has been configured on the node, the JMS destination must also be a topic. |
Backout threshold | This property specifies the integer value that controls a message that is sent to the backout destination. A threshold value of 3 indicates that if the input node receives a message where the value of the JMSX_DeliveryCount property exceeds 3, the message is sent to the backout destination and is removed from the source destination. See Configuring the backout threshold property. |
This problem is not applicable to z/OS®.
In addition to the broker service trace, another trace log is provided to diagnose problems that could occur when a node using JMS transport participates in an XA coordinated message flow transaction. That is, at least one JMS node in the message flow has the Transaction Mode property set to Yes, and the message flow property Coordinated Transaction set to yes.
XAJMS_TRACEFILE = c:\JMSSwitchLog
The previous example produces a file called JMSSwitchLog2596.txt, where the queue manager start up process ID is 2596.
Neither of these trace files require extra formatting.
Description of problem: The JMS node is unable to obtain the Initial Context Factory or a JNDI administered object, such as the Connection Factory or JMS destination, and message BIP4640 is issued.
mqsireportproperties IB9NODE -c JMSProviders -o JMSProvider –r
Description of problem: A JMS node is unable to connect for a JMS provider and issues message BIP4648.
Description of problem: A JMS node is unable to obtain a JMS destination and issues message BIP4642.
Description of problem: A JMS input node does not attempt to reconnect to a JMS provider following a connection failure, or a restart of the JMS provider.
Corrective action: If the JMS provider is implemented by using a model that pushes on the JMS client, rather than a traditional polling model, the JMS provider might not throw an exception when calling receive() on a broker connection. To resolve this problem, set the jmsAsyncExceptionHandling property of the JMSProviders configurable service to true for this JMS provider.