IBM Support

IT26533: IIB NODE MIGRATED TO V10 FAILS TO START AFTER ENABLED MQTT SERVER FAILS TO CONNECT

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

  • After an in place migration from IIB V9 to IIB V10, an
    Integration Node is unable to start because of a failure
    starting an enabled MQTT Server.
    

Local fix

  • Configure a port number for the MQTTServer as follows:
      mqsichangeproperties -b pubsub -o MQTTServer  -n port -v true
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users migrating an existing Integration Node to V10 when an
    MQTT server was previously enabled at the earlier product level.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When starting the migrated Integration Node which had a MQTT
    server enabled at the earlier level , the following sequence of
    errors may be seen:
    
    BIP9152S: Unable to connect to the MQTT broker owned by node:
    '<Integration Node Name>'
    
    BIP2826E: Integration server termination wait timer reached.
    There are '<number>' threads still executing.
    
    BIP2228E: Severe error:
    /build/S1000_slot1/S1000_P/src/CommonServices/Unix/ImbAbend.cpp
    1318 non-fatal signal received Abend file:
    /var/mqsi/common/errors/TBCOM.agent.12427.1.abend action: abort
    
    It was not possible to shut down the Integration node using the
    mqsistop command, because it will not terminate the biproker and
    bibpservice processes.
    
    It may be necessary to terminate the brokers processes manually
    using the kill -9 system command.
    
    The problem is caused by an incorrect default value for the port
    number of the MQTT server that is set during the migration
    process.
    

Problem conclusion

  • The product now automatically starts an embedded MQTT server
    for an Integration Node that has been migrated to V10, and which
    previously ran with an MQTT server enabled.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.18
    v11.0      11.0.0.6
    
    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

    IT26533

  • 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

    2018-10-15

  • Closed date

    2019-09-30

  • Last modified date

    2019-09-30

  • 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

[{"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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 September 2019