Java monitor: How to read the graphs and use its info optimally.

[dkumar2]

http://java-monitor.com/postedimages/ce1aa556-ccd0-4c6e-a1e4-cc732be95bcd.png

Hi experts,

I have started using Java monitor today. I am not able to understand the info available in graph completely.
I wanna make optimal use of it. I have got some issues with tomcat and deployed application. I came across java monitor and thought of using it.

Does Java monitor gives info about the process stack and thread name e.g. Thread-x of process-y has taken xx mSec ??

Do help me out. Thanks.

[kjkoster]

Dear dkumar2,

Unfortunately, there is no comprehensive documentation of the graphs. You'll have to learn as you go along. If you read back some of the questions that other people asked, you may get quite some helpful information.

Or you can just ask as you did just now. :)

This graph shows the number of concurrent HTTP sessions on your application server. The 'max' of -1 means that there is no upper limit to the number of sessions (other than your heap size). The green line shows that you had one session for a while, then zero and then one again. Not a terribly busy server. :)

The way to use this graph is to hold it next to the heap memory graph. If you see large heap usage and at the same time a large number of HTTP sessions, perhaps you should look at what state is being kept in HTTP sessions.

Hope this helps.
Kees Jan

[dkumar2]

Thanks for passing info Sir.

The very purpose for which i thought of using Java monitor is:

I have a J2EE application running on the tomcat. Now the problem is - application is getting slow over period of time say every 2 weeks. When user is trying to log in the application sometimes its quite slow and also got hung for significant number of times. So i have scheduled tomcat restart.

Now the best part is same application is running on tomcat is other environments with similar configuration, very smoothly.

To investigate into this issue, i need to monitor every aspect of it. I gone through Java monitor features, and thought of using it. But right now having bit hard time to understand the graphs :) Hope i will make optimal use of it.

[kjkoster]

Dear dkumar2,

In that case you need to install Java-monitor on the problematic server and wait for the problems to begin. You may have to switch off the automated Tomcat to diagnose this.

Once the problems start, check the heap memory graph and see if you have enough memory allocated. Also check the database connection graph for connection leakage.

Are you on UNIX? If so, you can see the load graph to decide if Tomcat is loading your machine heavily during the problems, or if Tomcat is idling.

Best wait for the problems to manifest and then post the graphs I mentioned on the forum. Perhaps we can help.

Kees Jan

[dkumar2]

Thanks Sir.
I would definitely do that and will keep posted.