On 27/07/2010 11:52, VERES ZOLTAN wrote:
> Hi All,
> 
> I have a serious problem with tomcat on linux.
> Tomcat often stops with the error "Connection refused".

Does the process actually terminate? Or when you write "stops" do you
mean "stops accepting connections".

> Clients can not connect to the server and even the tomcat default page can 
> not be displayed.
> When this error occurs, one of the following two JAVA processes has 200% CPU 
> load.
> But I'm not sure this causes the problem.
> 
> /usr/java/jre1.6.0_10/bin/java 
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager.
> 
> /usr/java/jre1.6.0_10/bin/java 
> -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties.

Are those really two separate processes? That would suggest multiple
Tomcat instances.

> If I terminate the JAVA process listed above with kill -9, and restart Tomcat 
> with catalina.sh start, it works again for a while. After 10 minutes, it 
> stops again, but this working period can be hours.

Don't do that.

When the problem occurs, take 3 thread dumps, each 10 seconds apart and
compare them. That will tell you what the Tomcat instance is doing.

> I have found the following log items in catalina.log:
> But there is no other program listening on TC port 8181...
> 
> 2010.07.23. 12:35:26 org.apache.coyote.http11.Http11Protocol init
> SEVERE: Error initializing endpoint
> java.net.BindException: Address already in use<null>:8181

That suggests a Tomcat process that has not been fully shutdown is still
running.

> Is it possible, that I have to increase the "maxThreads" or "acceptCount" 
> tomcat parameters, which control the concurrent access to the tomcat server?

Anything is possible, but neither of those is likely.

> Or can an update to 6.0.20-26-28 solve this problem?

Unlikely. Although you should upgrade to 6.0.29 for the recent security fix.

> Software versions:
> OS: Suse Linux Enterprise 10
> Tomcat: 6.0.18
> JAVA JRE: 1.6.0_10-b33

And I'd upgrade the JVm too.

> I would be grateful for any idea.

Looks like an application issue to me. Take the thread dumps and check
the logs.

Mark



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to