IBM Support

IC98254: IDLE SAP CONNECTIONS NOT PURGED AS EXPECTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When connecting to SAP (or Siebel / PeopleSoft), you can
    configure a connectionIdleTimeout property in the configurable
    service. This is the number of seconds for which a connection
    can be idle before it is closed by IBM Integration Bus.
    
    A Java exception can occur in the processing associated with
    closing these connections, which results in idle connections not
    getting closed as expected. This exception (as reported in
    Service trace) is a java.util.ConcurrentModificationException.
    
    This can lead to connections continuing to accumulate, and
    eventually saturating the back-end server (for example the SAP
    R/3 server).
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker v8.0 and IBM Integration
    Bus v9.0 who use the Adapter nodes to connect to SAP, Siebel or
    PeopleSoft EIS systems, and have the connectionIdleTimeout
    property configured.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When connecting to SAP (or Siebel / PeopleSoft), you can
    configure a connectionIdleTimeout property in the configurable
    service.  This is the number of seconds for which a connection
    can be idle before it is closed by IBM Integration Bus.
    
    A Java exception can occur in the processing associated with
    closing these connections, which results in idle connections not
    getting closed as expected.  This exception (as reported in
    Service trace) is a java.util.ConcurrentModificationException.
    
    This can lead to connections continuing to accumulate, and
    eventually saturating the back-end server (for example the SAP
    R/3 server).
    
    
    
    <i>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</i>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC98254

  • 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

    2013-12-11

  • Closed date

    2014-01-28

  • Last modified date

    2016-04-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

    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:
28 April 2016