IBM Support

IT23748: AFTER AN UPGRADE, IBM STERLING B2B INTEGRATOR NODE 1 IS NOT AVAILABLE

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

  • During system maintenance and after a successful OS upgrade,
    node 1 is not available but node 2 restarts.
    It hangs at step "Waiting for ServicesController node1", while
    the previous steps ("Pre Register node1", "Starting IBM Sterling
    B2B Integrator Server node1", "Waiting for IBM Sterling B2B
    Integrator JNDI node1", "Initializing Security node1", "Waiting
    for IBM Sterling B2B Integrator Server node1") are successfully
    executed.
    

Local fix

  • RTC NO:  552559
    
    
    1). Check the servicesctl.log file and look at the last line in
    the log.
    It will give the name of the Adapter that is failing to start.
    
    
    2). Disable the adapter with the following command:
    
    From /si/install/bin
    ./db_exec.sh "update service_instance set active_status=0 where
    service_name = '<ADAPTER_NAME>' "
    
    sample:
    ./db_exec.sh "update service_instance set active_status=0 where
    service_name = 'SFTP_SERVER_ADAPTER' "
    
    
    Try starting the application with ./run.sh
    
    Repeat these steps until SI is able to start again.
    
    
    3). Then enable the Adapters that you disabled.
    You can do this from the user interface or by command line
    From the install directory (one level aboive /bin) /si/install/
     bin/opscmd.sh -nnode1 -cSTARTADAPTER -pid=<ADAPTER_NAME>
    
     sample:
     bin/opscmd.sh -nnode1 -cSTARTADAPTER -pid=SFTP_SERVER_ADAPTER
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    During system maintenance and after a successful upgrade of
    the OS, node 1 is not available but node 2 restarts.
    Deadlock can occur if XpathBPLauncherEventListener is configured
    for event listner in a cluster.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    
    Delivered In:
    5020601_10
    5020602_6
    5020603_6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23748

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-16

  • Closed date

    2018-04-25

  • Last modified date

    2018-07-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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
15 July 2018