Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 1792 invoked from network); 8 Sep 2009 16:12:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Sep 2009 16:12:00 -0000 Received: (qmail 67535 invoked by uid 500); 8 Sep 2009 16:11:56 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 67470 invoked by uid 500); 8 Sep 2009 16:11:56 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 67459 invoked by uid 99); 8 Sep 2009 16:11:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2009 16:11:56 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rainer.jung@kippdata.de designates 195.227.30.149 as permitted sender) Received: from [195.227.30.149] (HELO mailserver.kippdata.de) (195.227.30.149) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2009 16:11:47 +0000 Received: from [195.227.30.209] (notebook-rj [195.227.30.209]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id n88GBPHm013492 for ; Tue, 8 Sep 2009 18:11:25 +0200 (CEST) Message-ID: <4AA68227.1080809@kippdata.de> Date: Tue, 08 Sep 2009 18:11:19 +0200 From: Rainer Jung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: apache modjk issue References: <25348847.post@talk.nabble.com> In-Reply-To: <25348847.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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 > > 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