You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by sandeepkumarnimma <sa...@gmail.com> on 2009/09/08 17:48:21 UTC

apache modjk issue

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 workers.properties 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.host=el0023.bc
worker.el0023_jboss1.port=8009

<Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
         emptySessionPath="true" enableLookups="false" redirectPort="8443"
/>

-- 
View this message in context: http://www.nabble.com/apache-modjk-issue-tp25348847p25348847.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Re: apache modjk issue

Posted by sandeepkumarnimma <sa...@gmail.com>.

sandeepkumarnimma wrote:
> 
> On 08.09.2009 17:48, sandeepkumarnimma wrote:
>>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
> 
>>http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
> 
>>and also configure the number of threads you need for your JBoss
connector.
> 
>>Regards,
> 
>>Rainer
> 
> Thanks for your reply.
> when we made below mentioned changes at apache and jboss end respectively.
> the application was up and running for about an hour and then down and it
> automatically up again.
> 
> worker.el0023_jboss1.type=ajp13
> worker.el0023_jboss1.host=el0023.bc
> worker.el0023_jboss1.port=8009
> worker.el0023_jbossx.connection_pool_timeout=600
> worker.el0023_jbossx.ping_mode=A
> 
> <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
>          emptySessionPath="true" enableLookups="false" redirectPort="8443"
> maxThreads="200" connectionTimeout="600000"/>
> 
> Can you please help us in finding the optimal values of timeout or any
> formula.
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/apache-modjk-issue-tp25348847p25365579.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Re: apache modjk issue

Posted by Rainer Jung <ra...@kippdata.de>.
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 workers.properties 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.host=el0023.bc
> 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

http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html

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

Regards,

Rainer

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