On 12/3/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
Okay, I figured out how to get the thread dump. It was in the tomcat
logfile. I'm attaching it here.
Nothing sticks out to me as problematic, except for the 150 concurrent
requests in progress!
Perhaps the real problem already passed, and
On 12/2/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
I've done a temporary fix for this by running a proxy in front of
tomcat. Then I updated my system startup to start solr, wait 20
seconds, run a few queries, wait 20 seconds, then start the proxy.
This is working fine now. But I'd still lik
Hmmm, on most Linux/UNIX systems, sending the QUIT signal does nothing
else but generate a stack trace to the console or a log file. If you
don't start tomcat by hand, the stack trace may go somewhere else I
suppose. This would be useful to learn how to do on your particular
system (and we shoul
On 12/2/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
> accept connections for 3 or 4 hours ... did you try taking some thread
> dumps like yonik suggested to see what all the threads were doing?
A kill -3 will not kill the process. It does nothing and there's no
thread dump on the console. k
