IT32733: BIP2112E MAX CMP HANDLERS REACHED AFTER TIMEOUTS REQUESTING EXECUTIONGROUPPROXY INSTANCE

APAR status

• Closed as program error.

Error description

• The integration node bipbroker process (AdminAgent) maintains a
  pool of threads to handle incoming local connections from
  clients using the Integration API (IAPI, formally known as
  CMP). These clients include message flows, running in
  integration servers belonging to the integration node, using
  the integration API from JavaCompute nodes to retrieve
  information about the integration node and resources. By
  default the thread pool size is 100, but this limit can be
  configured by changing the value of the maxLocalIAPIClients
  property of the agent's DeployThreadManager object using the
  mqsichangeproperties command. If the maximum number of local
  IAPI client connections has been reached, and a new connection
  request is received, the bipbroker process rejects the request
  and the following error is reported in the system log:
  
  
  BIP2112E: Integration node internal error: diagnostic
  information 'Could not launch a handler for a local CMP
  connection'
  
  The lifetime of these threads is typically short,
  with well behaving clients connecting, retrieving the required
  information and disconnecting when finished, but it has been
  seen that some CMP receiver threads in the bipbroker process
  appear to be left running, waiting for data, indefinitely. This
  can occur if the client has requested a connection using a call
  to call ExecutionGroupProxy.getLocalInstance() but the request
  has timed out and the call returns 'null'. A possible reason
  for the timeout is that the integration node has a very large
  number of integration servers (execution groups) that need to
  be filtered.
  
  The following exceptions may be seen reported in
  the integration server's console.txt/stdout file:
  
  
  com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException:
  Communication problems with the
  broker
  detailMessage=Communication problems with the broker
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10 using the Integration API.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The integration node bipbroker process (AdminAgent) maintains a
  pool of threads to handle incoming local connections from
  clients using the Integration API (IAPI, formally known as CMP).
  These clients include message flows, running in integration
  servers belonging to the integration node, using the integration
  API from JavaCompute nodes to retrieve information about the
  integration node and resources. By
  default the thread pool size is 100, but this limit can be
  configured by changing the value of the maxLocalIAPIClients
  property of the agent's DeployThreadManager object using the
  mqsichangeproperties command. If the maximum number of local
  IAPI client connections has been reached, and a new connection
  request is received, the bipbroker process rejects the request
  and the following error is reported in the system log:
  
  BIP2112E: Integration node internal error: diagnostic
  information 'Could not launch a handler for a local CMP
  connection'
  
  The lifetime of these threads is typically short, with well
  behaving clients connecting, retrieving the required information
  and disconnecting when finished, but it has been seen that some
  CMP receiver threads in the bipbroker process appear to be left
  running, waiting for data, indefinitely. This can occur if the
  client has requested a connection using a call to call
  ExecutionGroupProxy.getLocalInstance() but the request has timed
  out and the call returns 'null'. A possible reason for the
  timeout is that the integration node has a very large number of
  integration servers (execution groups) that need to be filtered.
  
  The following exceptions may be seen reported in the integration
  server's console.txt/stdout file:
  
  com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException:
  Communication problems with the broker
  detailMessage=Communication problems with the broker
  

Problem conclusion

• The Integration API has been modified to improve the performance
  of the ExecutionGroupProxy.getLocalInstance() call when there
  are many integration servers, and if the call does timeout and
  return a null object, the BrokerProxy connection is disconnected
  before the return.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.21
  
  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 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