Yes, kill -QUIT is the correct way.
----- Original Message -----
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 14, 2001 5:41 PM
Subject: Re: [JBoss-dev] EntityInstanceInterceptor change
> Isn't it SIGQUIT... SIGHUP does not seem to produce a thread dump on Linux.
>
> --jason
>
>
> On Wed, 11 Jul 2001, Scott M Stark wrote:
>
> > Generate a thread dump using SIGHUP or Ctrl-\ on unix/linux or Ctrl-Break on
> > win32.
> > This should be the first step to any deadlock/starvation investigation. The
> > sun vm
> > tends to produce garbage dumps with HotSpot so turn it off using
> > the -classic
> > switch.
> >
> > MDBs are involed in the lock unit test so what are you running?
> >
> > ----- Original Message -----
> > From: "Jason Dillon" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, July 11, 2001 8:57 PM
> > Subject: [JBoss-dev] EntityInstanceInterceptor change
> >
> >
> > > What was the problem... the diff is more or less the entire file. I am
> > > curious, because I am still running into a hang, though it seems like it
> > > might be MDB or SB related (not sure at the moment).
> > >
> > > --jason
> > >
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
