PI94999: HMGR0232E EXCEPTIONS HAPPEN WHEN CREATING CORE GROUP BRIDGES IN A CELL

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• When more than one coregroups are configured in one cell and
  coregroup bridges will be configured between all these
  coregroups, HMGR0232E exceptions may happen at runtime.
  
  Sample exception:
  
  [2/5/18 13:04:09:008 CET] 0000006f GlobalBBoardB E   HMGR0232E:
  The active coordinator received a message from
  TEST_WAS90_CELL\TEST\nodeagent indicating this process is a core
  group bridge; however, there are no core group bridges currently
  configured.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere coregroups at version 9.0     *
  *                      bridged to coregroups at versions       *
  *                      prior to 9.0 may not function properly  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A change went into WebSphere version 9.0 to change the default
  wire format and HA protocol versions to the highest available
  values. This should only have affected the configurable
  protocol values for the main corestack, but also changed the
  non-configurable protocol values for the internal Access Point
  Group corestack. As a result, when a coregroup at version 9.0
  is bridged to a coregroup at a version prior to 9.0, the
  Access Point Group will contain a mix of v9.0 and non-v9.0
  servers and may result in a protocol version mismatch.
  

Problem conclusion

• Code was changed to return the protocol versions for the
  Access Point group corestack to the lowest protocol values for
  compatibility when bridging coregroups at version 9.0 to
  coregroups at versions prior to 9.0.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.8.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP