IT18004: EXECUTION GROUPS REPEATEDLY FAIL TO START DUE TO CORRUPT PORT VALUE IN REGISTRY

APAR status

• Closed as program error.

Error description

• On Message Broker startup, all execution groups start briefly
  and then terminate without any error or abend file being
  generated. The AdminAgent process logs BIP2060W messages
  repeatedly to indicate that the execution group processes were
  started but have terminated. Attempts to trace the execution
  groups starting up produce no output.
  
  A core file might be generated with the following call stack
  which indicates that there was a problem converting a registry
  value, in this case the HTTPS listener port, to an integer:
  
  IOT/Abort trap in pthread_kill at 0x900000000510e94 ($t1)
  0x900000000510e94 (pthread_kill+0xd4) e8410028          ld
  r2,0x28(r1)
  (dbx) where
  pthread_kill(??, ??) at 0x900000000510e94
  _p_raise(??) at 0x9000000005106c8
  raise.raise(??) at 0x90000000002c9cc
  abort() at 0x900000000083444
  std::myabort()() at 0x9000000009fbf0c
  std::terminate()() at 0x9000000009fb46c
  exceptio.std::terminate().terminate()() at 0x9000000009fc00c
  __DoThrowV6() at 0x9000000009fe428
  ImbUtility.imbWcsToInt(ImbWstring::ConstIterator,ImbWstring::Con
  stIterator)(??, ??, ??, ??) at 0x90000003639d7b4
  ImbInitialisationData::GetBrokerHTTPSListenerPort() const(??)
  at  0x90000003660a930
  ImbStartParameters::ImbStartParameters(ImbWstring,ImbWstring,Imb
  Wstring, ImbWstring)(??, ??, ??, ??, ??) at 0x900000036a5cbc8
  ImbStartParameters::createStartParameters(ImbWstring,ImbWstring,
  ImbWstring,ImbWstring)(??, ??, ??, ??, ??) at 0x900000036a5afc8
  main(??, ??) at 0x100000a64
  
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• Use the following command to reset the registry port value to a
  valid integer:
  
  mqsiservice brokerName -r HTTPListener/HTTPSConnector/port=7083
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V8.0 and IBM Integration
  Bus V9 and V10.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  On Message Broker startup, all execution groups start briefly
  and then terminate without any error or abend file being
  generated. The AdminAgent process logs BIP2060W messages
  repeatedly to indicate that the execution group processes were
  started but have terminated. Attempts to trace the execution
  groups starting up produce no output because tracing has not
  been initialized yet.
  
  A core file might be generated with the following call stack
  which indicates that there was a problem converting a registry
  value, in this case the HTTPS listener port, to an integer:
  
  IOT/Abort trap in pthread_kill at 0x900000000510e94 ($t1)
  0x900000000510e94 (pthread_kill+0xd4) e8410028          ld
  r2,0x28(r1)
  (dbx) where
  pthread_kill(??, ??) at 0x900000000510e94
  _p_raise(??) at 0x9000000005106c8
  raise.raise(??) at 0x90000000002c9cc
  abort() at 0x900000000083444
  std::myabort()() at 0x9000000009fbf0c
  std::terminate()() at 0x9000000009fb46c
  exceptio.std::terminate().terminate()() at 0x9000000009fc00c
  __DoThrowV6() at 0x9000000009fe428
  ImbUtility.imbWcsToInt(ImbWstring::ConstIterator,ImbWstring::Con
  stIterator)(??, ??, ??, ??) at 0x90000003639d7b4
  ImbInitialisationData::GetBrokerHTTPSListenerPort() const(??)
  at  0x90000003660a930
  ImbStartParameters::ImbStartParameters(ImbWstring,ImbWstring,Imb
  Wstring, ImbWstring)(??, ??, ??, ??, ??) at 0x900000036a5cbc8
  ImbStartParameters::createStartParameters(ImbWstring,ImbWstring,
  ImbWstring,ImbWstring)(??, ??, ??, ??, ??) at 0x900000036a5afc8
  main(??, ??) at 0x100000a64
  
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product no longer abends on startup due to corrupt
  HTTPListener port values. It continues startup with the default
  values, and a message is written to the AdminAgent stderr file.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.11
  v8.0       8.0.0.9
  v9.0       9.0.0.9
  
  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

  WEB MESSAGE BRO

• Fixed component ID

  5724J0520

Applicable component levels