WebSphere Application Server Enterprise Edition Asynchronous Beans service creates several MBeans. Two of these MBeans control the thread pools associated with each configured WorkManager object -- the WorkManager thread pool and the AlarmManager thread pool. Both of these pools can be modified at run time by using a Java Management Extension (JMX) MBean. Each pool has an MBean that can be looked up independently and are named: "WorkManager:<Workmanager_name>" and "<Workmanager_name>:Alarm Pool" respectively, where, <WorkManager_name> is the name field of the configured WorkManager.
Because the name for the MBean is not a legal JMX 1.2 ObjectName, AsynchBeans and the ThreadPool manager have been updated to automatically convert all illegal characters to periods ("."). For example, if a WorkManager name is Central WorkManager: Finance,Admin, the actual MBean name and mbeanIdentifier becomes Central WorkManager. Finance.Admin.
When looking up a WorkManager ThreadPool MBean, all queries for these objects change from:
wsadmin>$AdminControl queryNames "WebSphere:*,type=ThreadPool,name=WorkManager:Central WorkManager: Finance,Admin"or
wsadmin>$AdminControl queryNames "WebSphere:*,mbeanIdentifier=WorkManager:Central WorkManager: Finance,Admin"to
wsadmin>$AdminControl queryNames "WebSphere:*,type=ThreadPool,name=WorkManager.Central WorkManager. Finance.Admin"or
wsadmin>$AdminControl queryNames "WebSphere:*,mbeanIdentifier=WorkManager.Central WorkManager. Finance.Admin"
To provide interoperability with the product
Version 5.0.2 of these MBeans, apply interim fix PQ80354, which changes the
MBean names to use the updated format.