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-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
