By the way, I did some more testing and though I would have sworn that
destroy() prevented any further requests in Tomcat 6.0.x it also appears
to allow at least 1 additional request.
On 3/9/2011 1:44 PM, Jess Holle wrote:
On 3/9/2011 1:40 PM, Mark Thomas wrote:
On 09/03/2011 18:50, Mark Thom
On 3/9/2011 1:40 PM, Mark Thomas wrote:
On 09/03/2011 18:50, Mark Thomas wrote:
On 09/03/2011 15:47, Jess Holle wrote:
What's more troublesome to me is that with every approach I've tried at
least 1 request still gets through. In some cases this request works
normally. In other cases the requ
On 3/9/2011 12:50 PM, Mark Thomas wrote:
On 09/03/2011 15:47, Jess Holle wrote:
When invoking stop() and then destroy() the destroy() succeeds
[something I missed in my original post], but an exception is still logged:
2011-03-09 09:29:21,939 ERROR [RMI TCP Connection(21)-10.196.0.84]
org.apach
On 09/03/2011 18:50, Mark Thomas wrote:
> On 09/03/2011 15:47, Jess Holle wrote:
>> What's more troublesome to me is that with every approach I've tried at
>> least 1 request still gets through. In some cases this request works
>> normally. In other cases the request gets a 200 and no content or
On 09/03/2011 15:47, Jess Holle wrote:
> Well the exception when invoking destroy() directly is:
>
> 2011-03-09 09:28:16,238 ERROR [RMI TCP Connection(13)-10.196.0.84]
> org.apache.tomcat.util.modeler.BaseModelMBean - Exception invoking
> method destroy
> org.apache.catalina.LifecycleException: A
Well the exception when invoking destroy() directly is:
2011-03-09 09:28:16,238 ERROR [RMI TCP Connection(13)-10.196.0.84]
org.apache.tomcat.util.modeler.BaseModelMBean - Exception invoking method
destroy
org.apache.catalina.LifecycleException: An invalid Lifecycle transition was
attempted ([
On 09/03/2011 15:06, Jess Holle wrote:
> So there's no way to do this from the Tomcat side?
>
> The process embedding Tomcat knows it's stopping. It does not
> necessarily even have an ability to connect to the web server(s) that
> are connecting to it [Apache, IIS, or SJWS, but all via the JK
>
So there's no way to do this from the Tomcat side?
The process embedding Tomcat knows it's stopping. It does not
necessarily even have an ability to connect to the web server(s) that
are connecting to it [Apache, IIS, or SJWS, but all via the JK
connector]. I therefore want to say "this Tomc
On 03/09/2011 03:26 PM, Jess Holle wrote:
P.S. I certainly want to finish processing requests that are already being
processed -- I want a graceful shutdown.
It's a two way process.
First in mod_jk mark the node as stopped (best by using status worker).
Then after all sessions times out in To
P.S. I certainly want to finish processing requests that are already
being processed -- I want a graceful shutdown.
On 3/9/2011 8:16 AM, Jess Holle wrote:
I want to stop all incoming requests at a given point. I am running
Tomcat within a larger process and I want to stop accepting new
reques
I want to stop all incoming requests at a given point. I am running
Tomcat within a larger process and I want to stop accepting new requests
-- ideally in such a way that those requests are immediately routed to
another Tomcat by mod_jk.
In Tomcat 6.0.x, I tried to do this by invoking the sto
11 matches
Mail list logo
