Return-Path: 
 <tomcat-user-return-104029-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 51962 invoked from network); 23 Jun 2004 14:03:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 23 Jun 2004 14:03:38 -0000
Received: (qmail 38890 invoked by uid 500); 23 Jun 2004 13:56:16 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 38767 invoked by uid 500); 23 Jun 2004 13:56:14 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 38640 invoked by uid 99); 23 Jun 2004 13:56:12 -0000
Received: from [212.202.153.225] (HELO server01.hh.uptime.de)
 (212.202.153.225)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 23 Jun 2004 06:56:12 -0700
content-class: urn:content-classes:message
Subject: RE: tomcat crash ... "unexpected exception"
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 Jun 2004 15:56:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <C19D2E05B25FA94E943431666541E5B73A6688@server01.hh.uptime.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: tomcat crash ... "unexpected exception"
Thread-Index: AcRZKG5iZwsXoq9HTt6VN0heAcEtIQAAJDdA
From: "Ralph Einfeldt" <ralph.einfeldt@uptime-isc.de>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N


Although I'm not a mod_jk* user, I think it's quite=20
unusual to define 2 CoyoteConnectors and 2 workers
for one tomcat instance.

Unless you have good reason to do so, I would remove
one of each. This introduces a complexity that is
not needed. (At least I that's my opinion)

> -----Original Message-----
> From: bastien.devos@bpo.be [mailto:bastien.devos@bpo.be]
> Sent: Wednesday, June 23, 2004 3:24 PM
> To: Tomcat Users List
> Subject: Re: tomcat crash ... "unexpected exception"
>=20
>=20

> # real workers (Tomcat instances)
> [ajp13:localhost:8009]
> info=3DWorker1
> channel=3Dchannel.socket:localhost:8009
> group=3Dlb
> ver=3D2
>=20
> [ajp13:localhost:8010]
> info=3DWorker2
> channel=3Dchannel.socket:localhost:8010
> group=3Dlb
> ver=3D1
>=20
>    <Connector=20
> className=3D"org.apache.coyote.tomcat4.CoyoteConnector" port=3D"8009"=20
> minProcessors=3D"100" maxProcessors=3D"500" enableLookups=3D"false"=20
> acceptCount=3D"100" debug=3D"4"=20
> connectionTimeout=3D"120000" useURIValidationHack=3D"false"=20
> protocolHandlerClassName=3D"org.apache.jk.server.JkCoyoteHandler">
>          <Logger className=3D"org.apache.catalina.logger.FileLogger"=20
> prefix=3D"connector1-logger-" suffix=3D".log" timestamp=3D"true" />
>    </Connector>
>=20
>    <Connector=20
> className=3D"org.apache.coyote.tomcat4.CoyoteConnector" port=3D"8010"=20
> minProcessors=3D"100" maxProcessors=3D"500" enableLookups=3D"false"=20
> acceptCount=3D"100" debug=3D"4"=20
> connectionTimeout=3D"120000" useURIValidationHack=3D"false"=20
> protocolHandlerClassName=3D"org.apache.jk.server.JkCoyoteHandler">
>          <Logger className=3D"org.apache.catalina.logger.FileLogger"=20
> prefix=3D"connector2-logger-" suffix=3D".log" timestamp=3D"true" />
>    </Connector>

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