Gaming News | Gaming Opinion | Playstation 4 | Xbox One | PS Vita | Film | Media

monitoring support of J2SE 5.0

The management and monitoring support of J2SE 5.0 is very comprehensive, with the capabilities of remote for Java platform and for the applications that run on this. A remote minioring system called Java Management Extensions (JMX) is included in the J2SE 5.0. It is a fresh addition to the monitoring capabilities’ list on the JVM. The specification for JMX is the Java Specification Request 160 for the remote monitoring of JMX. It concentrates on the remote access mechanism by building an API for remote client for an agent who is based on JMX.
The Tomcat 5.5 is fashioned to make advantage of the built-in capabilities of JMX in J2SE 5.0. The Version 5.5 enforces the latest specifications of JavaServer Pages (2.0) and Servlet (2.4) and is the outcome of an extensive refactoring and redesign of the architecture of the Tomcat server. It proves to be more stable and improves upon the Tomcat 4.x with advanced reliability, scalability and performance, application deployment, clustering of the integrated session and JMX monitoring.
With the advanced versions of the JMX capabilities of J2Se 5.0 and Tomcat, one can make the methods and attributes of the servlet container and methods that are available through JMX while decreasing the JMX-related code’s complexity at the same time.


A cluster of Tomcat consists of six important components: deployer, replication valve, receiver, sender, membership and cluster.
The Tomcat 5.5 offers few improvements over the predecessors of it (The Tomcat versions 5.0 and 4.1) in terms of manageability, server monitoring, session relication and clustering. In the Tomcat 4, several components of the server (like service, engine and host) can be supervised using the MBeans. But in the Tomcat 5.5, Filip Hanik, Yoav Shapira and the other developers of Tomcat wrote the implementations of JMX.


The JMX client is the graphical user interface (thin client or server/client) that is used to connect to an agent of JMX (who is running on a remote or local machine). An ideal client of JMX should contain the features stated hereunder to monitor the application server more effectively without subjecting to any extra overhead:
• Very low overhead on network and system resources
• Ability to maintain the system performance and stability
• Very minimum or even no extra configuration is required (if any settings are needed to be configured, they should be done declaratively instead of programmatically)
• Excellent reporting features

The J2SE 5.0 comes with a client tool of JMX called the JConsole which can be used to look into the details of the runtime JVM. The installation of Tomcat includes a servlet of JMX called called JMXProxyServlet which can view as well as update the attributes of the Tomcat MBeans . It is a very lightweight proxy to view and manipulate the MBeans that is running inside a Tomcat container and turns out to be helpful in the integrating command line scripts for changing and monitoring the Tomcat internals. The JMX Set and Query commands can be utilized to query MBeans and change their operations and attributes respectively. Want to Learn More about Java Programming and computer networking read here technical articles

Leave a Comment