[jboss-user] I have the "big" problem with my Jboss in environment Cluster

[Claudemir Ferreira Franco]

Hi people,
 
I have the "big" problem with my Jboss. My situation is: 
I Have many applications running in cluster Jboss in the version 4.0.2 and sametimes my two nodes the cluster occurred the following error:
 
ERROR [org.apache.tomcat.util.threads.ThreadPool] All threads (400) are currently busy, waiting. Increase maxThreads (400) or check the servlet status.
 
I already analised the threaddump and I didn´t any things about "memory leak, deadlock and etc.." When this is ocurs my portal becomes unavailable.  My configuration is:
 
*) 02 servers running linux version kernel 2.6
*) Version JBOSS is 4.0.2
*) Apache 1.3.37 + Mod_jk.1.2.25
 
workes.properties
# 
# Servidor Jboss Producao 01
#
worker.dcpr0039.port=8009
worker.dcpr0039.host=192.168.0.5
worker.dcpr0039.type=ajp13
worker.dcpr0039.connection_pool_timeout=600
worker.dcpr0039.connection_pool_minsize=10
worker.dcpr0039.connect_timeout=60000  # (1 minute)
worker.dcpr0039.prepost_timeout=60000  # (1 minute)
worker.dcpr0039.lbfactor=1
 
# 
# Servidor Jboss Producao 02
#
worker.dcpr0040.port=8009
worker.dcpr0040.host=192.168.0.6
worker.dcpr0040.type=ajp13
worker.dcpr0040.connection_pool_timeout=600
worker.dcpr0040.connection_pool_minsize=10 
worker.dcpr0040.connect_timeout=60000  # (1 minute)
worker.dcpr0040.prepost_timeout=60000  # (1 minute)
worker.dcpr0040.lbfactor=1
 
 
server.xml (tomcat)
      <!-- A AJP 1.3 Connector on port 8009 -->
      <Connector port="8009" address="${jboss.bind.address}"
         maxThreads="400" minSpareThreads="150" maxSpareThreads="175"
         acceptCount="100"
         emptySessionPath="true" enableLookups="false" redirectPort="8443" 
         protocol="AJP/1.3"/>

httpd.conf
MinSpareServers 5
MaxSpareServers 20
#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 10
 
#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 500

 
Please, Someone could help me?
 
 
Thanks.
 
- - - - - - -
Claudemir Ferreira Franco
Analista Suporte Unix
BrasilTelecom Site III - CyberDatacenter
Tel: 41 3305-1657
HYPERLINK "mailto:claudemir.franco at b2br.com.br"claudemir.franco at b2br.com.br
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.16/1251 - Release Date: 30/1/2008 09:29
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20080130/46a1a7d9/attachment.html