agreed ..Diagnostic tools are a good ideaAlso if you determine you're using too
many threads take a look at implementing ThreadPools which allows you to
configure min_spare_threads, max_threads and max_spare_threads/ connector
http://marc.info/?l=tomcat-user&m=103598932529887&w=2
HTH/Martin______________________________________________Disclaimer and
confidentiality noteEverything in this e-mail and any attachments relates to
the official business of Sender. This transmission is of a confidential nature
and Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within this
transmission.> Subject: RE: javax/mail/address> Date: Fri, 23 Nov 2007 13:08:18
-0500> From: [EMAIL PROTECTED]> To: users@tomcat.apache.org> > Thanks for the
suggestion, I'll get this running this afternoon and see> what I can find.> >
-dustin > > -----Original Message-----> From: Katilie, John [mailto:[EMAIL
PROTECTED] > Sent: Friday, November 23, 2007 11:58 AM> To: Tomcat Users List>
Subject: RE: javax/mail/address> > I know this may be a little out of context
but have you tried using> JCONSOLE to monitor Tomcat? It's a nice little GUI
and can easily show> you the threads, the stack trace and Locking conditions.
I'm no expert,> I just started using it in the last week or so. It's pretty
easy to set> up to monitor a JVM like Tomcat when JCONSOLE and TOMCAT are
running on> the same machine. That is how I've been using it. There is a little
more> to set up if JCONSOLE and TOMCAT are on different machine which I have>
not tried yet.> > Just a thought, sorry if I'm out of line. Note: JCONSOLE is
part of the> JVM so no additional product needs to be installed or purchased.>
> Jfk.> > -----Original Message-----> From: Caldarale, Charles R [mailto:[EMAIL
PROTECTED]> Sent: Friday, November 23, 2007 11:13 AM> To: Tomcat Users List>
Subject: RE: javax/mail/address> > > From: Dustin Fortin [mailto:[EMAIL
PROTECTED]> > Subject: RE: javax/mail/address> > > > "Finalizer" daemon prio=10
tid=0x08081800 nid=0x1107 in Object.wait()> > > [0xb5592000..0xb55930a0]> >
java.lang.Thread.State: WAITING (on object monitor)> > at
java.lang.Object.wait(Native Method)> > - waiting on <0x15e70528> (a>
java.lang.ref.ReferenceQueue$Lock)> > The above is the normal state for the
Finalizer thread, so it's not your> problem. You'll see several (possibly many)
threads in a WAITING> condition, which usually just means they're ready to
accept work from> some other thread. You'll need to look at the others.
Comparison with> a thread dump from a normally running Tomcat instance may be
of some> help.> > - Chuck> > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL
AND/OR OTHERWISE PROPRIETARY> MATERIAL and is thus for use only by the intended
recipient. If you> received this in error, please contact the sender and delete
the e-mail> and its attachments from all computers.> >
---------------------------------------------------------------------> To start
a new topic, e-mail: users@tomcat.apache.org To unsubscribe,> e-mail: [EMAIL
PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]> > >
---------------------------------------------------------------------> To start
a new topic, e-mail: users@tomcat.apache.org To unsubscribe,> e-mail: [EMAIL
PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]> > >
---------------------------------------------------------------------> To start
a new topic, e-mail: users@tomcat.apache.org> To unsubscribe, e-mail: [EMAIL
PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]>
_________________________________________________________________
Put your friends on the big screen with Windows Vista® + Windows Live™.
http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_102007
