PK89162: CORE GROUP BRIDGE IS NOT REBUILT WHEN ONLY ONE BRIDGE EXISTS IN A CORE GROUP

6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The sequence that initiates bridge rebuild (retrieval of state
  from peer core groups) during startup is triggered by the
  starting of a peer bridge in the local core group.  Therefore,
  if a peer bridge is not started, the rebuild sequence will also
  not start.  This can occur in environments where only one bridge
  exists in a core group.
  
  This fix will initiate bridge rebuild when only one bridge
  exists in a core group.
  

Local fix

• Start a second bridge in the core group
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of the core group bridge in       *
  *                  IBM WebSphere Application Server            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When only one core group bridge is      *
  *                      started in a core group, the bridge     *
  *                      may not receive state info from other   *
  *                      core groups.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When only one bridge is started in a core group and the bridge
  is the last bridge to start in the topology, there is a chance
  that the bridge will not receive state information from
  other core groups in the topology.
  

Problem conclusion

• The problem was fixed to ensure that a single bridge will
  always receive state information during startup.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.0.2.39, 6.1.0.29, and 7.0.0.7.  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

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP