IBM Support

IT33109: ERROR WHILST STARTING OR STOPPING MULTIPLE APPLICATIONS THAT HAVE BEEN DEPLOYED TO A REMOTE INTEGRATION NODE

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

  • If you use the IBM Integration Toolkit to start or stop
    multiple applications or message flows that have been on a
    remote Integration Node, you may get an error popup that says
    "Error occurred when sending the message to the Integration
    Node"
    
    An Integration API trace shows the following stack
    
    com.i
    bm.broker.config.proxy.ConfigManagerProxyLoggedException: Error
    occurred when sending the message to the Integration Node
    
     at c
    om.ibm.broker.config.proxy.IIBCommandSocket.send(IIBCommandSocke
    t.java:152)
     at com.ibm.broker.config.proxy.WebSocketSender.send
    (WebSocketSender.java:191)
     at com.ibm.broker.config.proxy.SendM
    anager.send(SendManager.java:170)
     at com.ibm.broker.config.prox
    y.RequestBatchingCoordinator.send(RequestBatchingCoordinator.jav
    a:421)
     at com.ibm.broker.config.proxy.AdministeredObject.setPro
    perties(AdministeredObject.java:1188)
     at com.ibm.broker.config.
    proxy.AdministeredObject.setProperties(AdministeredObject.java:1
    085)
     at com.ibm.broker.config.proxy.ApplicationProxy.stop(Appli
    cationProxy.java:283)
     at com.ibm.broker.config.proxy.Applicatio
    nProxy.stop(ApplicationProxy.java:257)
     at com.ibm.etools.mft.br
    oker.runtime.model.ApplicationModel$2.run(ApplicationModel.java:
    79)
     at java.lang.Thread.run(Thread.java:812)
    
    Also you may see
    the entry "Blocking message pending 10000 for BLOCKING" in the
    Integration API trace
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM integration Bus v10.0 trying to stop or start
    multiple applications or messageflows from toolkit
    
    
    Platforms affected:
    Linux on x86-64 platform, Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">Using IBM
    Integration Toolkit stop or start </span><span
    style="background-color:rgb(255, 255, 255)">multiple
    applications or message flows that have been on a </span><span
    style="background-color:rgb(255, 255, 255)">remote Integration
    Node, you may get an error popup that says
    
     </span><span style="background-color:rgb(255, 255, 255)">"Error
    occurred when sending the message to the Integration
    N</span><span style="background-color:rgb(255, 255, 255)">ode"
                                                             </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">An Integration
    API trace shows the following stack             </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255,
    255)">com.i</span><span style="background-color:rgb(255, 255,
    255)">bm.broker.config.proxy.ConfigManagerProxyLoggedException:
    Error </span><span style="background-color:rgb(255, 255,
    255)">occurred when sending the message to the Integration Node
         </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">at
    c</span><span style="background-color:rgb(255, 255,
    255)">om.ibm.broker.config.proxy.IIBCommandSocket.send(IIBComman
    dSocke</span><span style="background-color:rgb(255, 255,
    255)">t.java:152)
         </span>
    <span style="background-color:rgb(255, 255, 255)">at
    com.ibm.broker.config.proxy.WebSocketSender.send</span><span
    style="background-color:rgb(255, 255,
    255)">(WebSocketSender.java:191)
         </span>
    <span style="background-color:rgb(255, 255, 255)">at
    com.ibm.broker.config.proxy.SendM</span><span
    style="background-color:rgb(255, 255,
    255)">anager.send(SendManager.java:170)
         </span>
    <span style="background-color:rgb(255, 255, 255)">at
    com.ibm.broker.config.prox</span><span
    style="background-color:rgb(255, 255,
    255)">y.RequestBatchingCoordinator.send(RequestBatchingCoordinat
    or.jav</span><span style="background-color:rgb(255, 255,
    255)">a:421)                        </span><span
    style="background-color:rgb(255, 255, 255)">            </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">Also, you may
    see a log </span><span style="background-color:rgb(255, 255,
    255)">"Blocking message pending 10000 for BLOCKING" in the
    </span><span style="background-color:rgb(255, 255,
    255)">Integration API trace
    
    This issue lies in the integration API's occasional failure to
    handle multi-threaded executions against remote integration
    node. So the error can happen in other scenarios like refreshing
    the deployed resources under an integration server. Also, it is
    applicable to any other java multi-threaded applications using
    integration API. </span>
    

Problem conclusion

  • The integration API failure has been fixed and hence the toolkit
    will no longer throw an unexpected error while stopping or
    starting multiple applications or flows.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.22
    
    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

    IT33109

  • 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

    2020-06-08

  • Closed date

    2020-09-23

  • Last modified date

    2020-09-23

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
24 September 2020