Darn, I was hoping you had some other quick trick.  Well, since I figured 
that viewing thread dumps would be a usefull thing for not only development 
but maybe even for the daily operations of JBoss, I've add JMX accessible 
method to the "Info" MBean so that it will give you that dump.  I also have 
it giving you the memory useage.  But the memory usage that it is reporting 
seems off.  Anybody have any clue to how the Runtime.totalMemory() function 
relates the amount of memory that is used by the java process??

Regards,
Hiram


>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev] JMS thread usage
>Date: Sat, 23 Jun 2001 00:03:42 -0700
>
>By sending a SIGQUIT go the IBM VM. The Sun VM is crashing
>after 1 or 2 dumps so I am using the IBM 1.3 version.
>
>----- Original Message -----
>From: "Hiram Chirino" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Friday, June 22, 2001 10:22 PM
>Subject: Re: [JBoss-dev] JMS thread usage
>
>
> > Scott,
> >
> > Thanks for verifying the changes.  I have feeling those connections are 
>not
> > closing themselfs out properly.  How is it the you get the thread 
>dumps??
> > Are you running it in a debugger???
> >
> > Regards,
> > Hiram
>
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to