PM56484: FILTER OUT NOTIFICATION REGISTRATIONS FROM JSR160 CLIENT

Fixes are available

APAR status

Closed as program error.

Error description

When a JSR160RMI client connects to a deployment manager,
performance issues may arise depending on the size of the
network deployment cell, because the implementation of the JMX
notification buffer registers as a listener for all MBeans in
the cell.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server versions 6.1, 7.0 and 8.0            *
****************************************************************
* PROBLEM DESCRIPTION: When a JSR160 client connects to a      *
*                      deployment manager, the Java            *
*                      Management Extensions (JMX)             *
*                      notification buffer registers every     *
*                      managed bean (MBean) as a notificaton   *
*                      listener causing performance issue.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a JSR160 client connects to a deployment manager, the JMX
notification buffer registers every MBean as a notificaton
listener causing performance issue such as high CPU load.

Problem conclusion

A new Java Virtual Machine custom property,
com.ibm.websphere.management.remote.filter.mbean.type, is
provided to specify MBean types not to be registered as
notification listeners. To specify multiple MBean types,
separate each MBean type with a ":". Testing has shown that
filtering out the RASLoggingService MBean type improves
performance. Other MBean types could be added to the filter
list as needed in the customer's environment.

To enable the custom property in the Administrative Console:
In a Network Deployment environment, the system property
needs to be set on the deployment manager. System
administration --> Deployment manager --> Java and Process
Management --> Process Definition --> Java Virtual Machine -->
Custom Properties --> New
Name : com.ibm.websphere.management.remote.filter.mbean.type
Value : <enter the MBean type(s)>

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.45, 7.0.0.23, and 8.0.0.4.  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 number
PM56484
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-20
Closed date
2012-03-15
Last modified date
2012-03-15

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM56484: FILTER OUT NOTIFICATION REGISTRATIONS FROM JSR160 CLIENT

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?