DO NOT REPLY [Bug 33589] New: - stop a context without interrupting its running threads

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33589>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33589

           Summary: stop a context without interrupting its running threads
           Product: Tomcat 4
           Version: 4.1.31
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Webapps:Manager
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: lionel.farbos@free.fr


I don't think it is a bug but I'd want to suggest you a new feature.

Actually, when I stop a context, its running threads are interrupted, 
so, 
- If my servlet had already send datas on the response outputstream, I can have
a 200 HTTP response with a truncated response,
- If my servlet had not send datas before, I can have a 500 HTTP response with
NullPointerException, XML11Configuration not found, ...

So I can't stop my Context without a service interruption (from a client point
of view), even if I have load balancing/failover with mod_jk.

So, is it possible to add a configuration parameter in Tomcat Context to not
interrupt running threads ?

This request for new feature is also available for Tomcat 5.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org