IBM Support

IT17657: ABEND IN JMSINPUT NODE WHEN TRYING TO EMIT A ROLLBACK MONITORINGEVENT AFTER A JMS CONNECTION FAILURE

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

  • If a JMSInput node is configured to emit monitoring events on
    start or rollback which include message data, and encounters a
    problem connecting to the JMS provider then the following abend
    may be seen as it tries to emit the event:
    
     MessageServices!?refreshHeadersFromElements@ImbMessage
     MessageServices!?addBitstreamDataToEventData@ImbEventGatherer
     MessageServices!?constructMonitoringEvent@ImbEventGatherer
     MessageServices!?notifyMsgEventInner@ImbEventGatherer
     imbjplg!?emitRollbackEvents@ImbJniNode
     imbjplg!?dispatcher@ImbJniNode
     imbjplg!?run@Parameters@ImbJniNode
     CommonServices!?run
     CommonServices!?threadRun
     CommonServices!?threadBootStrap
    

Local fix

  • Disable montoring on the input node for rollback events
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 who use the JMSInput node
    and have monitoring events configured.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a JMSInput node is configured to emit monitoring events on
    start or rollback which include message data, and encounters a
    problem connecting to the JMS provider then an abend may be seen
    as it tries to emit the event.
    This occurs because the JMSInput node tries to emit events even
    when there has been no message received and it also tries to
    reference uninitialized storage which should be protected.
    
    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

  • The product no longer emits monitoring events from the JMSInput
    node when there has been no message received, and protection has
    also been added to stop the abend if a monitoring event is
    emitted when the message has not been initialised.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.8
    
    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

    IT17657

  • 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

    2016-10-25

  • Closed date

    2017-03-15

  • Last modified date

    2017-03-15

  • 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

  • RA00 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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020