connections until long running / keep alive
are left, and stopping Tomcat is the best thing to do outside of waiting for
the connections to close themselves.
On Oct 13, 2012, at 4:39 AM, Mark Thomas ma...@apache.org wrote:
On 13/10/2012 04:27, Andrew Feller wrote:
Is there a graceful way to drain
Is there a graceful way to drain connections and shutdown Tomcat with JSVC?
I've been unsuccessful finding anything documented about this, so I
imagine people have a variety of non-standard ways or don't care.
Regards,
Andrew
--
*Andrew Feller*, Development Team Lead
Bronto Software
patches are still released and their frequency.
Thank you for the assistance,
Andrew
--
Andrew Feller, Analyst
LSU University Information Services
200 Frey Computing Services Center
Baton Rouge, LA 70803
-
To unsubscribe, e-mail
QUESTION: What is the best practice for running Tomcat? JSVC daemon or
startup / shutdown scripts as a non-root user and forwarding HTTPS requests
to a non-privileged port?
While reading the Professional Apache Tomcat 6 (ISBN: 978-0-471-75361-2),
they recommend running Tomcat to start it up
Is there any reason why Tomcat running under the JSVC daemon using the
Apache Portable Runtime for SSL would act erratically to TCP health checks?
We are using a Juniper DX for load balancing that uses TCP health checks to
port 443 of a Tomcat instance in order to keep the machine in the