IBM Support

IT10713: JMS NODES USING XA CONNECTIONS ARE UNABLE TO RECONNECT AFTER AN OUTAGE WITH ACTIVEMQ OR WEBLOGIC

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • when there is a server or network outage with ActiveMQ or
    WebLogic, a JMS node is unable to reconnect automatically after
    the outage has been resolved. The following error message
    repeats:
    
    [BIPmsgs:4362] BIP4362E: Java node error: Broker
    '<Broker>';
    Execution Group '<Execution Group Name>'.Error message
    generated by user Java node.  Contact the node provider for
    further details. : Could not getXAResource for JMS provider
    proprietary API (1).
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • Stop and Start the Integration Server to clean up the broken
    JMS connection.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus using the JMS or SOAP nodes to
    connect to ActiveMQ or Weblogic JMS providers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a connection between IIB and an ActiveMQ or Weblogic JMS
    provider is broken, for example if the JMS provider goes down,
    or if there is a network outage then IIB will fail to reconnect
    to the server when the server is made available again.
    
    The problem is caused by a failure to refresh connection objects
    when a failure is encountered obtaining a valid XA resource
    during the setup of a JMS global or local transaction.
    
    
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • IBM Integration Bus has been modified so that a connection will
    be re-established to ActiveMQ or Weblogic JMS servers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.6
    v9.0       9.0.0.6
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT10713

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-14

  • Closed date

    2016-09-01

  • Last modified date

    2016-09-01

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020