AdminClient JMX API intended for single threaded use
 Technote (troubleshooting)
 
Problem(Abstract)
IBM® WebSphere® Application Server administrative APIs provide control of the operational aspects of your distributed system as well as the ability to update your configuration. An administrative client program must invoke methods on the AdminService object that is running in the deployment manager (or the Application Server in the base installation). The AdminClient class provides a proxy to the remote AdminService object through one of the supported Java™ Management Extensions (JMX) connectors.

The AdminClient JMX API might be very useful in developing a custom administrative client program; however, there are issues when attempting to use this API with multiple threads.
 
Cause
This API is intended for single thread use.
 
Resolving the problem
The AdminClient is intended to be used by a single thread. If it is used across multiple threads, it is the responsibility of the creator of the AdminClient to control synchronized access.

For more information on thread synchronization, refer to the following java.net site: Java Tech: The ABCs of Synchronization

For more information on using the Administrative client API, refer to:
Information Center: Developing an Administrative Client Program
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Management Extensions (JMX) or JMX client API
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1178190
IBM Group: Software Group
Modified date: Aug 31, 2004