> Remy Maucherat wrote: > > > > It does work fine for me. The change is a bad idea anyway, since the > > shutdown is asynchronous (it would be almost equivalent to not attemping to > > shutdown and kill the process). > > > > The way I am using Tomcat isn't typical, the instance that fails to > terminate on shutdown is being used as a stand alone soap server which > uses https. The only web application is the soap server. It doesn't work > in this case. This configuration had worked fine with Tomcat 4.0.1. This > is the first time I tried running the soap server with 4.1-dev, I wanted > to test the DbcpDataSourceFactory. > > I didn't realize that the container stop was asynchronous, so you are > right, using System.exit() like this is not a good solution. If you > look at the code you will notice that the comment says FIX ME ???. :-) > I put the System.exit() in as a temp fix.
I don't think it's a good idea to put something in that you know is broken. We might forget about it (esp since there's some vacation to help). > The only cause I can come up with which would prevent the java process > from terminating is if there are still threads running which weren't > terminated by the stop. Hence the speculation that the problem has something > to do with the STM changes. If there's no STM servlets, it shouldn't do that. Also, if you look at the code, I don't see why it would cause some problems. Is it Apache SOAP ? I'll try to look at it if it is. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
