tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: apache modjk issue
Date Tue, 08 Sep 2009 16:11:19 GMT
On 08.09.2009 17:48, sandeepkumarnimma wrote:
> we are using webseal,apache 2.0, mod_jk 1.2.18 and jboss 4.2.3 application
> server. we are facing an issue with a single application out of 36
> applications configured in apache file. we are receiving
> 500 internal error in webseal logs for a duration of 5 to 10 mins in which
> the application is not at all accessible. But after some time the
> application is becoming stable again. But in few instances the the
> application is up and running either when we restart jboss instance or
> apache service. we are using default configuration of apache and jboss.
> Please let us know if we need to perform any new configurations. The problem
> started when we migrated the jboss instance from version 3.2.6 to 4.2.3.
> Currently, here are the configurations made in apache and jboss instance
> respectively.
> worker.el0023_jboss1.type=ajp13
> worker.el0023_jboss1.port=8009
> <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
>          emptySessionPath="true" enableLookups="false" redirectPort="8443"
> />

If status 500 is logged in your webapp log file, then you have to
discuss it with your webapp developers.

Your configuration is to basic for production use.

Read about timeouts on

and also configure the number of threads you need for your JBoss connector.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message