Fixes are available
APAR status
Closed as program error.
Error description
MBeans provided by the Liberty profile can be accessed by remote clients and applications via an MBeanServerConnection instance, but the management interfaces are not exposed as public APIs
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V8.5 * * Liberty profile users working with JMX * * MBeans * **************************************************************** * PROBLEM DESCRIPTION: Liberty profile MBeans do not provide * * management interfaces as public APIs * **************************************************************** * RECOMMENDATION: * **************************************************************** MBeans provided by the Liberty profile can be accessed by remote clients and applications via an MBeanServerConnection instance, but the management interfaces are not exposed as public APIs, nor are the interfaces documented. This means that a user can work the MBeans via an MBeanServerConnection but cannot create a proxy object which allows for cleaner, simpler code. The affected MBeans are those identified by the following ObjectNames or ObjectName patterns: WebSphere:name=com.ibm.ws.jmx.mbeans.generatePluginConfig WebSphere:service=com.ibm.ws.kernel.filemonitor.FileNotification MBean WebSphere:service=com.ibm.websphere.application.ApplicationMBean ,name=* WebSphere:type=JvmStats WebSphere:type=ServletStats,name=* WebSphere:type=ThreadPoolStats,name=Default Executor
Problem conclusion
Management interfaces have been exported as public API, complete with Javadoc, and are available from the jars in wlp/dev/ibm-api. All MBeans provided by the Liberty profile are now documented in the Information Center and each lists the name of the management interface. These interfaces can be used to obtain a proxy object and they are exposed via the application classloader when the related feature is enabled, so they are available for external JMX clients and applications alike. The interfaces exported, in the same order as the MBeans listed above, are: com.ibm.websphere.webcontainer.GeneratePluginConfigMBean com.ibm.websphere.filemonitor.FileNotificationMBean com.ibm.websphere.application.ApplicationMBean com.ibm.websphere.monitor.jmx.JvmMXBean com.ibm.websphere.webcontainer.ServletStatsMXBean com.ibm.websphere.monitor.jmx.ThreadPoolMBean The fix for this APAR is currently targeted for inclusion in fix pack 8.5.0.1. 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
PM70106
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-02
Closed date
2012-10-03
Last modified date
2012-10-03
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
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 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":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 October 2021