We are trying to debug a production system.  The JVM crashes occur every 1-3 days, so 
our temporary workaround has been to restart Tomcat every night.   I will look into 
RootCause and see if there are others I can come up with.  Does anyone else know of 
other profilers designed for production environment?
 
Regards,
Roman
 

        -----Original Message----- 
        From: Eric J. Pinnell [mailto:[EMAIL PROTECTED] 
        Sent: Wed 6/11/2003 1:22 PM 
        To: Tomcat Users List 
        Cc: Roman Fail 
        Subject: Re: JVM Profilers
        
        

        Something to think about is whether or not you are trying to debug a
        production system or a dev system.  Does it crash in dev or do you only
        see if after a few days being up in prod?
        
        If you only see it in prod, you might want to think about something a
        little more lightwieght than the profilers you mention.  Those are mainly
        for developers.  And as far as the ones you name off it's really personal
        preference.
        
        There is a flavor of profilers that are made for more production envs.
        An example is RootCause.  But there are several of those types of
        profilers out there.
        
        -e
        
        On Wed, 11 Jun 2003, Roman Fail wrote:
        
        > I am considering purchase of JProfiler, OptimizeIt 5.5, or JProbe.  Does 
anyone have wisdom to share on the features of each?  Are there other good profilers I 
should consider?
        >
        > We have been experiencing regular JVM crashes on our production Tomcat 
4.1.24 installation.  Originally we were running the Sun HotSpot 1.4.1_02 client, then 
server (on RH Linux 8.0).  Now we've switched to BEA JRockit 8.1 and are still having 
crashes, clearly something is bad in our code - or perhaps we need to start 
load-balancing.  We have tuned obvious kernel parameters like file-max, and have 2GB 
physical memory (1GB is given to tomcat's heap), dual Intel processors.  Besides a few 
small Java-based daemons on the server, it is dedicated to tomcat.
        >
        > We recently migrated from a Windows 2000/ServletExec 3.1/Sun HotSpot client 
1.3.1 environment which didn't have these problems - I'm not sure what to think at 
this point.
        >
        > Please reply directly to me (and cc the list) as I receive only the digest 
version.
        >
        > Thanks!
        >
        > Roman Fail
        > POS Portal, Inc.
        > Sacramento, CA USA
        >
        >
        

Reply via email to