IBM Support

IT28578: TCPIP NODES FAIL TO START WHEN MIGRATED USING DEFAULT POLICY

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 using TCPIP Nodes with default policy, for example when
    migrating from a previous version of IBM Integration Bus, the
    message flow fails to start with the following error:
    
    BIP3557E: Message flow attempted to use 'TCPIPClient' policy
    'Default.TCPIPClient', which exists but failed to be created
    when the integration node started.
    
    Examining trace shows the root cause to be the following
    exception:
    
     java.lang.NullPointerException at
    com.ibm.broker.tcpip.ConnectionDetails.<init>(ConnectionDetails.
    java:168) at
    com.ibm.broker.tcpip.ServerConnectionDetails.<init>(ServerConnec
    tionDetails.java:44) at
    com.ibm.broker.tcpip.TCPIPDirector.getServerServicesHashtable(TC
    PIPDirector.java:585) at
    com.ibm.broker.tcpip.TCPIPDirector.initialize(TCPIPDirector.java
    :105) at
    com.ibm.broker.tcpip.TCPIPDirector.<init>(TCPIPDirector.java:98)
    at
    com.ibm.broker.tcpip.TCPIPDirector.<clinit>(TCPIPDirector.java:9
    5)
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise using the TCPIP Nodes
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using TCPIP Nodes with default policy, for example when
    migrating from a previous version of IBM Integration Bus, the
    message flow fails to start with the following error:
    
    BIP3557E: Message flow attempted to use 'TCPIPClient' policy
    'Default.TCPIPClient', which exists but failed to be created
    when the integration node started.
    
    Examining trace shows the root cause to be the following
    exception:
    
    java.lang.NullPointerException at
    com.ibm.broker.tcpip.ConnectionDetails.<init>(ConnectionDetails.
    java:168) at
    com.ibm.broker.tcpip.ServerConnectionDetails.<init>(ServerConnec
    tionDetails.java:44) at
    com.ibm.broker.tcpip.TCPIPDirector.getServerServicesHashtable(TC
    PIPDirector.java:585) at
    com.ibm.broker.tcpip.TCPIPDirector.initialize(TCPIPDirector.java
    :105) at
    com.ibm.broker.tcpip.TCPIPDirector.<init>(TCPIPDirector.java:98)
    at
    com.ibm.broker.tcpip.TCPIPDirector.<clinit>(TCPIPDirector.java:9
    5
    

Problem conclusion

  • App Connect Enterprise has been modified so that the
    NullPointerException is no longer thrown and a message flow
    containing a TCPIP Node that uses the default policy will now
    start correctly.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.4
    
    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

    IT28578

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-26

  • Closed date

    2019-10-18

  • Last modified date

    2019-10-21

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 October 2019