PM67129: JMX NOTIFICATION LISTENER FOR J2CMESSAGEENDPOINT IS NOT CALLED WHEN ACTIVATION SPECIFICATION CHANGES STATUS.

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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

• The admin client addNotificationListener does not work for the
  ObjectName returned for any J2CMessageEndpoint. Migrated
  applications use activation specifications and are able to
  request the current status using the corresponding MBean of type
  J2CMessageEndpoint. However, as the provided operation
  'getStatus' is not implemented as an attribute but as an
  operation, any notification does not return the ObjectName for
  any J2CMessageEndpoint.
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The J2CMessageEndpoint managed bean     *
  *                      (MBean) does not send notification      *
  *                      when the MBean is puased or             *
  *                      resumed.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the admin client uses the addNotificationListener method
  to listen to any notification sent by J2CMessageEndpoint , it
  does not work. The J2CMessageEndpoint MBean does not emit any
  notification when the MBean is puased or resumed.
  Added changes to emit below notifications when puase() and
  resume() is called on J2CMessageEndpoint  Mbean .
  j2ee.state.starting : J2CMessageEndpoint is being resumed.
  j2ee.state.running  : J2CMessageEndpoint is resumed.
  j2ee.state.stopping : J2CMessageEndpoint is being paused.
  j2ee.state.stopped  : J2CMessageEndpoint is paused.
  

Problem conclusion

• Added changes to the MBean to emit notifications.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.5 and 8.5.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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP