IBM Support

IT31937: LONG RUNNING TRANSACTION IN THE JMS RECEIVE OR JMSINPUT NODES

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 the JMS Receive node is invoked but does not receive a
    message, or when the JMSInput Node polls for a message but does
    not receive one the session is not committed. This can lead to a
     long running transaction on the remote JMS Provider.
    Some providers such as Weblogic may expire the session after a
    period of inactivity and if this occurs the node will
    periodically receive an error like the following:
    BIP4648 Failure to obtain a JMS Session. Text:Broker
    : Failure to obtain a JMS Session. Text:Broker Failure to obtain
    a JMS Session. Text:Broker Failure to obtain a JMS Session.
    Text:Broker
    Text:weblogic.jms.common.TransactionRolledBackException. Text:
    Attempt to resume an inactive transaction:
    BEA1-0A0237DC419902904099:error resuming transacted session's
    internal transaction, Failure to obtain a JMS Session.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 using the JMS Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When the JMS
    Receive node is invoked but does not receive a </span><span
    style="background-color:rgb(255, 255, 255)">message, or when the
    JMSInput Node polls for a message but does </span><span
    style="background-color:rgb(255, 255, 255)">not receive one the
    session is not committed. This can lead to a </span><span
    style="background-color:rgb(255, 255, 255)">long running
    transaction on the remote JMS Provider.
      </span>
    <span style="background-color:rgb(255, 255, 255)">Some providers
    such as Weblogic may expire the session after a </span><span
    style="background-color:rgb(255, 255, 255)">period of inactivity
    and if this occurs the node will </span><span
    style="background-color:rgb(255, 255, 255)">periodically receive
    an error like the following:              </span>
    
    <span style="background-color:rgb(255, 255, 255)">BIP4648
    Failure to obtain a JMS Session. Text:Broker  </span><span
    style="background-color:rgb(255, 255, 255)">: Failure to obtain
    a JMS Session. Text:Broker Failure to obtain </span><span
    style="background-color:rgb(255, 255, 255)">a JMS Session.
    Text:Broker Failure to obtain a JMS Session. </span><span
    style="background-color:rgb(255, 255, 255)">Text:Broker
                                                       </span>
    <span style="background-color:rgb(255, 255,
    255)">Text:weblogic.jms.common.TransactionRolledBackException.
    Text: </span><span style="background-color:rgb(255, 255,
    255)">Attempt to resume an inactive transaction:  </span><span
    style="background-color:rgb(255, 255,
    255)">BEA1-0A0237DC419902904099:error resuming transacted
    session's </span><span style="background-color:rgb(255, 255,
    255)">internal transaction, Failure to obtain a JMS Session.
            </span>
    

Problem conclusion

  • The JMS Receive node now registers the session as having work
    performed even if a message is not received. This causes the
    session to be committed at the end of the message flow and
    avoids having a long running transaction on the JMS Provider
    side.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.21
    v11.0      11.0.0.9
    
    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

    IT31937

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-13

  • Closed date

    2020-05-18

  • Last modified date

    2020-05-18

  • 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

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 May 2020