IC86648: JNDI LOOKUPS FAIL WHEN SAP ASSURED DELIVERY IS ACTIVE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When a SAP .inadapter is deployed to an execution with the
    "assured delivery" property set then all other JNDI lookups in
    the Execution Group will fail.
    
    This could cause JDBC, LDAP and JMS functionality to not work
    correctly.
    
    In the case of the JMS Output Node this results in the flow
    failing silently with no indication that anything has gone wrong
    in the syslog.
    

Local fix

  • To workaround deploy all flows using SAP with assured delivery
    in separate execution groups from flows using JMS,
    LDAP, JDBC or other JNDI based functionality.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V7.0 or higher using the
    SAP Input Node with assured delivery enabled.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM SUMMARY:
    When a SAP .inadapter is deployed to an execution group with the
    "assured delivery" property set then all other JNDI lookups in
    the Execution Group will fail.
    
    This could cause JDBC, LDAP and JMS functionality to not work
    correctly.
    
    In the case of the JMS Output Node this results in the flow
    failing silently with no indication that anything has gone wrong
    in the syslog.
    

Problem conclusion

  • WebSphere Message Broker has been modified so that JNDI
    lookups no longer fail when a SAP adapter is deployed with the
    "assured delivery" property enabled.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.0
    --------           --------------------
    Multiplatforms     7.0.0.6
    
    Platform           v8.0
    --------           --------------------
    Multiplatforms     8.0.0.2
    
    The latest available maintenance can be obtained from
    'WebSphere Message Broker Recommended Fixes'
    http://www.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 in 'WebSphere Message
    Broker Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC86648

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0510

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-19

  • Closed date

    2013-03-01

  • Last modified date

    2013-03-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

    WEB MESSAGE BRO

  • Fixed component ID

    5724J0510

Applicable component levels

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker

Software version:

7.0

Reference #:

IC86648

Modified date:

2013-03-01

Translate my page

Machine Translation

Content navigation