tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randhir Singh <randhir.si...@sterlite.com>
Subject Re: How to monitor performance of tomcat
Date Tue, 20 May 2014 11:01:48 GMT
Hi,

I had another point to add in this other than the reply sent by me in the
earlier mail is that if the JVM crashes as pointed out by you, would a JVM
process get started when Tomcat is started.

Also, how to check if 2 processes are sharing a common JVM. The 2 processes
referred to with the context of our environment would be JBoss & Tomcat.

I hope my query is clear.

Requesting a reply.


On Mon, Apr 28, 2014 at 4:16 PM, Randhir Singh
<randhir.singh@sterlite.com>wrote:

> Thanks for your valuable inputs. I am a bit of a novice to this. When this
> problem happens, it is quite a loss of face in front of the users who are
> widely spread geographically. I checked the catalina.out logs on the 2 days
> that the problem happened on 23rd & 25th April, the findings are as below:
>
> 23rd April '14:
>
> The catalina.out log showed the message like,
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------
> Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out.
> Waited 300000 milliseconds for response while calling on InvokerLocator
> [socket://<hostname of our
> machine>:4173/?invokerDestructionDelay=5000&timeout=300000]; nested
> exception is:
>         java.net.SocketTimeoutException: Read timed out
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 3 times among other exceptions in a span of around 2 minutes.
>
> 25th April '14:
>
> The errors captured in the logs were like,
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------
> java.lang.OutOfMemoryError: GC overhead limit exceeded
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 4 times among other exceptions in a span of around 2 minutes.
>
> Requesting a reply on this.
>
> Regards
>
> -----Original Message-----
> From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
> Sent: Monday, April 21, 2014 7:26 PM
> To: 'Tomcat Users List'
> Subject: RE: How to monitor performance of tomcat
>
> > -----Original Message-----
> > From: Randhir Singh [mailto:randhir.singh@sterlite.com]
> > Sent: Monday, April 21, 2014 5:17 AM
> > To: Tomcat Users List
> > Subject: RE: How to monitor performance of tomcat
> >
> > Hi,
> >
> > I wanted input from the experts on my query below that the port 8891
> > does not respond when the command,
> >
> > jconsole 10.101.17.79:8891
> >
> > is issued when the application hangs and stops responding.
> >
> > Requesting inputs so that the root cause analysis of this issue can be
> > found out.
> >
> > Regards
> >
> Randhir -
> Your actual first request in this thread was apparently a request for
> opinions on monitoring tools.
> This problem of actual hangs wasn't brought up until a week later.
> Here is what I've usually found when Tomcat stops responding and even the
> monitoring port is unreachable via jconsole and other tools: Your JVM has
> crashed for some reason.
> At this point, you need to refer to the Tomcat logs, your application logs,
> etc. in order to find the root cause.  If the JVM is still "running", try
> taking a couple of thread dumps and review them to find your root cause.
> Jeff
>
> ----------------------------------------------
> T ususcib, -mil uer-ususcib@tmct.paheor
> oraditonl omans,e-ai: ses-el@tmct.paheor
>

-- 

*STL Disclaimer:*
The content of this message may be legally privileged and confidential and 
are for the use of the intended recipient(s) only. It should not be read, 
copied and used by anyone other than the intended recipient(s). If you have 
received this message in error, please immediately notify the sender, 
preserve its confidentiality and delete it. Before opening any attachments 
please check them for viruses and defects. No employee or agent is 
authorised to conclude any binding agreement on behalf of Sterlite 
Technologies Limited with another party by email without express written 
confirmation by authorised person. Visit us at www.sterlitetechnologies.com 
 Please consider environment before printing this email !





Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message