Hi Chris- what happens when you log these events?
start of UDP loop Accepting UDP packets on the loopback address. log the buffer from UDP accept goto start of UDP loop start of loop to write to temp file Reading standard out from a child process log the buffer which is read from standard out writing it to a temp file. go start of loop to write to temp file Im guessing the UDP packet accept logic *may possibly* be blocking as it waits for the socket to read (and hanging the thread) Martin -- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: "Chris Eldredge" <[EMAIL PROTECTED]> To: <users@tomcat.apache.org> Sent: Wednesday, March 21, 2007 6:30 PM Subject: request hangs > I'm working on a web application which sometimes has several daemon > threads doing I/O processing in the background. The application seems > to be fine except when several tasks are running, sometimes Tomcat gets > a request and doesn't seem to process it. The request seems to time out > without ever being passed into my application for processing. > > My index page has an auto-refresh meta tag so I see this problem > frequently. The really strange thing is if I click reload once, the > next request also hangs, but if I click reload a 2nd time, this request > is processed very quickly. This behavior is very consistent, and > doesn't seem to have anything to do with the state of the background > tasks (they are still running). > > I mention the background tasks because I only see this hanging behavior > when the background tasks are active. When my application is idle, I > never see the behavior. Beyond that, I can't figure out what the > background tasks might be doing which would prevent Tomcat from > processing incoming requests: > > * Accepting UDP packets on the loopback address. > * Reading standard out from a child process and writing it to a temp file. > > Neither of these activities seem like they should interfere with Tomcat > request processing. > > I have placed some logging calls on a filter I configured in my > application and for the hung requests, the filter never logs a request. > This seems to indicate that the request is getting stuck before my > application gets a chance to process it. > > Has anybody seen anything like this before? > > Any advice for troubleshooting? > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
