PM46347: MBEAN METHOD MISSING FOR GETTING THE ACTIVE CONNECTION POOL WHEN USING DATASOURCE FAILOVER

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• No way to know if the datasouce has failed over to the
  alternate or if its failed back.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 using resource routing.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is no way to know if a resource   *
  *                      fail over had occurred.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A resource fail over may have occurred, but to find out which
  resource is currently being used trace enablement may have
  been required.
  

Problem conclusion

• An MBean attribute currentActivePool has been provided to see
  which resoucre is being used when a resource has failed over
  or back.  String getCurrentActivePool() was added for getting
  the active connection pool.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP