I did some more tracing and what I am seeing is that notify is called, the thread is waiting, but it never wakes up.
Keith
Remy Maucherat wrote:
Keith Wannamaker wrote:
Hey Remy,
Some facts: - the higher level code cannot cause the accept thread to "die"
Thread dump from T0 shows the two expected accepts, from main and from the HttpConnector; thread dump at T(5mins) shows the main accept, many idle Http handler threads waiting for work, and a few long-running uploads & downloads, but no Http accept. So, indeed, the thread is either stopping itself with no message or being killed with no message.
This is the same as the "RH 9" bug. Which OS are you using ?
Interesting note on logging. I tried today to use both jdk14 logger and simple log to show the progress of the accept. The behavior of going through either logger is that init messages come through but runIt messages don't. I thought it was the logger config so I reverted to System.out and still got that behavior. I wonder if the underlying exception causing the problem is being squelched by whatever is squelching my messages. Ever seen this?
Well, no. I have to admit I didn't look in detail at what everything does, since I didn't write that algorithm, and never quite understood why it works.
If Keith is feeling like experimenting a little (without too much risk involved, though): try 5.5.3 with strategy="ms" on the Connector. This will use the old TC 4.0 thread pool strategy, which is far less fancy, and was never reported as having trouble on stuff like RH 9.
I may try this.
That algorithm is really stupid. OTOH, it does seem to have more syncing (not that I can see any performance impact from it).
R?my
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
