Marko!
Thanks a lot! It works!
Just out of curiosity, how did you know that?
I've read the documentation about java on HP
http://www.hp.com/products1/unix/java/infolibrary/prog_guide/java1_3/classic.html#-XdoCloseWithReadPending
The java command line option -XdoCloseWithReadPending allows one thread
to close() a socket when there is an outstanding
read pending on that same socket
from another thread. The default behavior when
close() is called on a socket
which has an outstanding read call from another
thread is for the close() to block
until the read call completes. With the
-XdoCloseWithReadPending option, the
socket close() call closes the socket and, in
the context of the thread with the
pending read, a SocketException with the message
"Socket closed" is thrown.
But in jboss case (as well as for tomcat) no SocketException
is thrown, but shutdown completed without problem.
Well, HP is whole new world.
Thanks again.
Alex.
Marco Ladermann wrote:
>
> On Monday, 23. July 2001 18:13, Alexander Kogan wrote:
> > Semir,
> >
> > Semir Patel wrote:
> > > Try 'kill -3 <pid>' to get a VM dump and see if you can spot what is
> > > potentially hanging up the shutdown process.
> >
> > I did that (see the stack below), but I'm not sure
> > where the problem is. I think that something is waiting
> > for socket closure, but what?
> >
>
> Have you tried the (HP) JVM-Option:
> -XdoCloseWithReadPending
>
> May be that helps.
>
> Regards
> Marco
> --
> Marco Ladermann
> dpa, Deutsche Presse-Agentur GmbH
> [EMAIL PROTECTED] (PGP-Schlüssel auf Anfrage)
> Tel. +49 40 4113 2414 Fax +49 40 4113 2479
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
--
__________________________________________________
Alexander Kogan PTC www.ptc.com
[EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
