WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Managing failed JMS events

When problems processing a JMS request or response message create a failed JMS event in the Recovery subsystem, you must decide how to manage that event. Use the information in this topic to help you identify and fix the error and clear the event from the Recovery subsystem.

About this task

To manage a failed JMS event, perform the following steps.
Procedure
  1. Use the failed event manager to locate information about the failed JMS event, taking note of the exception type.
  2. Locate the exception type in Table 1 to determine the location and possible causes of the error, as well as suggested actions for managing the failed event.
    Table 1. Failed JMS events
    Exception type Location of error Possible cause of error Suggested action
    FaultServiceException Fault handler or fault selector There is malformed data in the JMS message.
    1. Inspect the JMS message and locate the malformed data.
    2. Repair the client that originated the message so it creates correctly formed data.
    3. Resend the message.
    4. Delete the failed event.
    There was an unexpected error in the fault handler or fault selector.
    1. Debug the custom fault selector or fault handler, fixing any errors identified.
    2. Resubmit the failed event.
    ServiceRuntimeException Fault handler The fault selector and runtime exception handler are configured to interpret the JMS message as a runtime exception. This is an expected exception. Look at the exception text to determine the exact cause, and then take appropriate action.
    DataBindingException or DataHandlerException Data binding or data handler There is malformed data in the JMS message.
    1. Inspect the JMS message and locate the malformed data.
    2. Repair the client that originated the message so it creates correctly formed data.
    3. Resend the message.
    4. Delete the failed event.
    There was an unexpected error in the data binding or data handler.
    1. Debug the custom data binding or data handler, fixing any errors identified.
    2. Resend the message.
    3. Delete the failed event.
    SelectorException Function selector There is malformed data in the JMS message.
    1. Inspect the JMS message and locate the malformed data.
    2. Repair the client that originated the message so it creates correctly formed data.
    3. Resend the message.
    4. Delete the failed event.
    There was an unexpected error in the function selector.
    1. Debug the custom function selector, fixing any errors identified.
    2. Resend the message.
    3. Delete the failed event.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/recovery/tadm_managingfailedjmsevents.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).