, Charles R wrote:
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: RE: tomcat gets stuck after a load for streams writing
i configured the maxThreads on the executor and didn't help.
It should have let you get to 400 request processors, rather than the
default of 200 that you were
Michal Singer wrote:
I use tomcat 6 with nio connectors. i run a heavy load of data and after a
while the tomcat gets stuck
and stops processing requests from client.
I posted before regarding this and was asnwered that the problem may be in
my server
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/tomcat-gets-stuck-after-a-load-for-streams-writing
Michal Singer wrote:
Tomcat version? 6.0.14
Try 6.0.18
Mark
JDK version? 1.5.0_12
OS? Microsoft Windows Server 2003
Connector configuration settings?
Connector port=8080 executor=AgentExecutor
protocol=org.apache.coyote.http11.Http11NioProtocol
maxKeepAliveRequests=1 maxThreads=400
-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/tomcat-gets-stuck-after-a-load
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: Re: tomcat gets stuck after a load for streams writing
why? was there a bug regarding this issue which was fixed there?
Possibly, notably this one:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44620
However, if you're not burning
:
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: Re: tomcat gets stuck after a load for streams writing
why? was there a bug regarding this issue which was fixed there?
Possibly, notably this one:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44620
However, if you're
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: RE: tomcat gets stuck after a load for streams writing
i configured the maxThreads on the executor and didn't help.
It should have let you get to 400 request processors, rather than the default
of 200 that you were seeing.
i also
: RE: tomcat gets stuck after a load for streams writing
i configured the maxThreads on the executor and didn't help.
It should have let you get to 400 request processors, rather than the
default of 200 that you were seeing.
i also checked the thread dumps.
And where do they show
any help will be highly appreciated.
Thanks, Michal
--
View this message in context:
http://www.nabble.com/tomcat-gets-stuck-after-a-load-for-streams-writing-tp20878338p20878338.html
Sent from the Tomcat - User mailing list archive at Nabble.com
10 matches
Mail list logo
