and
happily shuts down the web application. This should be easy to
reproduce, unless it's me who's messed something up.
On to my question: What can I do about this?
I'd greatly appreciate any suggestions, as I'd like to upgrade to Tomcat
4.0. All those nifty features...
Thanks!
/D
--
Daniel Aborg
it after the servlet has relinquished all of its connections. If the
servlet got the destroy before its connections had been closed, it could
close the connections at that point and everything would be fine. Is it
possible to get this behaviour?
Thanks!
/D
--
Daniel Aborg - Developer
true. Hmmm. I think I'll dig a bit deeper into that.
Thanks for your help!
/D
--
Daniel Aborg - Developer
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]
Daniel Aborg wrote:
I'm trying to upgrade to JBoss 2.4 with Tomcat 4. Unfortunately, I've
encountered a rather fatal problem: When Tomcat is asked to remove our
web application, i.e. for redeploying it or when shutting down, it hangs
with the following message:
StandardWrapper
for your help!
/D
--
Daniel Aborg - Developer
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]