In all cases of error, if the underlying cause is a JMSException that has been thrown by the JMS provider, the broker bip event message will include the text message from the JMSException to aid diagnosis.
If a message cannot be processed by the JMSInput node, or has been rolled back as part of a Global transaction, the message is backed out to the source destination. The message is then redelivered to the JMSInput node.
To prevent badly formed messages from interrupting the processing of valid messages, the node properties can be configured as follows:
Backout Destination | This is a JMS destination where 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 is the integer value that controls a message is sent to the backout destination. A threshold value of 3 means that, if the JMSInput 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. |
In addition to the broker service trace, another trace log is provided to diagnose problems that could occur when a JMSInput or JMSOutput node participates in a global message flow transaction. That is, at least one JMSInput or JMSOutput node in the message flow has the Transaction Mode property set to global and the message flow attribute Coordinated Transaction set to yes.
XAJMS_TRACEFILE = c:\JMSSwitchLog
Using the above example value for the variable produces a file called JMSSwitchLog2596.txt, where the Queue Manager start up process ID was 2596.
This is not applicable to Z/OS.
Description of problem: The JMSInput or JMSOutput node is unable to obtain the Initial Context Factory or a JNDI administered object such as the Connection Factory or JMS Destination, and a bip4640 message is issued.
Description of problem: A JMSInput or JMSOutput Node is unable to connect for a JMS provider and issues a bip4648 message.
Description of problem: A JMSInput or JMSOutput Node is unable to obtain a JMS destination and issues a bip4642 message.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac24877_ |