IBM Support

IC68174: FAILED EVENT DUE TO JCA FAILING TO ALLOCATE A CONNECTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JMS failed event is seen with the following exception
    ServiceRuntimeException: javax.jms.JMSException CWSIA0005E: The
    JCA runtime failed to allocate a connection.
    com.ibm.ws.sca.internal.jms.SbstractJMSInboundImpl.addCallbackMe
    ssage"
    

Local fix

  • -
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
    *                 and WebSphere Process Server v6.2 and V7     *
    *                 who use JMS or MQ bindings.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the JMS or MQ Import binding sends   *
    *                      a message but the messaging engine      *
    *                      goes down before the callback message   *
    *                      is put on the callback queue, the       *
    *                      binding sends a request and also        *
    *                      raises  a failed event. This results    *
    *                      in failed events that cannot be         *
    *                      replayed and responses that cannot      *
    *                      be correlated.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A JMS or MQ failed event is seen with the following exception
    ServiceRuntimeException: javax.jms.JMSException CWSIA0005E: The
    JCA runtime failed to allocate a connection.
    com.ibm.ws.sca.internal.jms.SbstractJMSInboundImpl.
    addCallbackMessage"
    This is because the import binding has been able to send the
    request message but the Messaging Engine has failed before the
    corresponding callback message has been put on the callback
    queue.
    This causes a Failed Event to be generated. As the request was
    sent this Failed Event cannot be replayed.
    When the response from the request is received it
    cannot be processed as there is no callback message.
    The correct behaviour here is to rollback the message rather
    than generate a Failed Event.
    

Problem conclusion

  • The code was modified such that the message is rolled back
    rather than a failed event being generated in this situation
    
    There are no known side effects associated with this fix.
    There is no known alternative workaround should you encounter
    this problem.
    
    This code fix was targeted to be included in the following fix
    packs:
         6.2.0 Fix Pack 3 (v6.2.0.3)
         7.0.0 Fix Pack 3 (v7.0.0.3)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68174

  • Reported component name

    WEB ESB FOR WIN

  • Reported component ID

    5724I8200

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-27

  • Closed date

    2010-05-28

  • Last modified date

    2010-05-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEB ESB FOR WIN

  • Fixed component ID

    5724I8200

Applicable component levels

  • R100 PSN

       UP

  • R200 PSN

       UP

  • R300 PSN

       UP

  • R612 PSN

       UP

  • R620 PSY

       UP

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 March 2023