The servlet that would not die.

[Nathan Roy]

Hi all, my configuration is based on Apache 1.3 using mod_jk connecting to
an ajp13 thread on Tomcat 5.5. 

This is the connector port definition I am using in my server.xml:

Connector port=8009 maxThreads=75 minSpareThreads=10
maxSpareThreads=15 enableLookups=false redirectPort=8443
protocol=AJP/1.3 disableUploadTimeout=false connectionTimeout=6/

My servlet (I do not own the source code) is randomly getting hung while
servicing requests, but Tomcat will not timeout these threads. I am trying
to get these threads to timeout so that the servlet can continue processing
other requests. When one request fails, I can see all subsequent requests
build up on the Tomcat servlet status page until the queue is full. They are
all stuck in service status (Status S) and just sit there until I restart
Tomcat. 

Any ideas? 

-
NOTICE OF CONFIDENTIALITY
-

The information in this email, including attachments, may be
confidential and/or privileged and may contain confidential health
information. This email is intended to be reviewed only by the
individual or organization named as addressee. If you have received
this email in error please notify Spheris immediately--by return
message to the sender or to [EMAIL PROTECTED] -- and destroy all copies
of this message and any attachments. Confidential health information is
protected by state and federal law, including, but not limited to, the
Health Insurance Portability and Accountability Act of 1996 and related
regulations.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: The servlet that would not die.

[Caldarale, Charles R]

 From: Nathan Roy [mailto:[EMAIL PROTECTED] 
 Subject: The servlet that would not die. 
 
 My servlet (I do not own the source code) is randomly getting 
 hung while servicing requests, but Tomcat will not timeout these 
 threads.

You have a bug in the servlet, and you need to fix it, live with it, or
stop using it.  The timeout value is for a connection, not an active
request.  Once a request has been handed off to a thread to process,
it's up to the application code to insure that the request finishes.
There's nothing Tomcat can do for this.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]