IT17745: A MIGRATED BROKER MAY REPORT INTEGRATION SERVERS AS STOPPED BUT THEY ARE ACTUALLY RUNNING.

APAR status

• Closed as program error.

Error description

• If for any reason an integration server's process state was not
  updated to stopped before migration to V10 it is possible that
  the integration server would not be in stopped state when the
  broker is started on V10.
  
  A defect exists such that the administration component is still
  using the old dynamic state to represent whether the
  integration server is stopped.
  This means:
  - bipbroker will start the integration server as it believes it
  needs to run
  - the Toolkit and WebUI will report the integration server as
  stopped
  - mqsistartmsgflow/mqsistopmsgflow will have no effect
  - mqsilist will show the integration server as stopped
  - mqsideploy will fail with a BIP2851
  

Local fix

• To workaround this problem, when the Broker is last stopped on
  the previous version, a check should be made that all
  integration servers are stopped successfully.  If all stopped
  integration servers have a process state of stopped then they
  will be in stopped state in V10.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10.0 migrating from a previous
  version of the product where an integration server's process
  state was not stopped prior to migration.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If an integration server is in stopped state then a
  DataFlowEngine process will not be launched for the integration
  server. Also, the Toolkit and WebUI will show the integration
  server as stopped and any commands issued against the stopped
  integration server will indicate it is stopped.
  
  In versions prior to IBM Integration Bus v10.0 WebSphere MQ was
  used to send asynchronous administration messages between the
  components, so multiple persistent values were used to represent
  that an integration server was stopped. Firstly a dynamic state
  would be set to stopped to indicate the integration server had
  been asked to stop. Then once the DataFlowEngine had actually
  stopped within the expected timeframe, the process state would
  be updated to stopped. If the integration server did not stop in
  the expected timeframe then it is possible the process state
  would not be updated to stopped. On restart of the broker the
  dynamic state and process state would be aligned and the
  integration server's process state would be stopped.
  
  IBM Integration Bus v10.0 uses a synchronous administration
  component, so only the process state represents the state of the
  integration server. If for any reason the process state was not
  updated to stopped before migration to v10.0, it is possible
  that the integration server would not be in stopped state when
  the broker is started on v10.0.
  
  A defect exists such that the administration component is still
  using the old dynamic state to represent whether the integration
  server is stopped.
  This means that:
  - bipbroker will start the integration server as it believes it
  needs to run
  - The Toolkit and WebUI will report the integration server as
  stopped
  - mqsistartmsgflow/mqsistopmsgflow will have no effect
  - mqsilist will show the integration server as stopped
  - mqsideploy will fail with a BIP2851
  

Problem conclusion

• The administration component no longer uses the old dynamic
  state for a migrated integration server's process state.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.7
  
  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

• RA00 PSY

     UP