Are you using load balance in your app?  If not, you probably don't need this 
line:

worker.worker1.lbfactor=50

Try to use this configuration in the server.xml

<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
            port="6969" minProcessors="5" maxProcessors="75"
            enableLookups="false" acceptCount="10" debug="0"/>

Hope this helps...


-----Original Message-----
From: Delphine Lê [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 13, 2005 6:41 PM
To: tomcat-user@jakarta.apache.org
Subject: RE: apache + tomcat + JK connector configuration


thank you, but it's got them:

# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=6969
worker.worker1.lbfactor=50
worker.worker1.cachesize=10
worker.worker1.cache_timeout=600
worker.worker1.socket_keepalive=1
worker.worker1.reclycle_timeout=300


> Post the workers.properties file.  You probably need to include these
> lines in that file:
>
> worker.list=worker1
> worker.worker1.port=6969
>
>
>
> -----Original Message-----
> From: Delphine Lê [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 13, 2005 2:01 PM
> To: tomcat-user@jakarta.apache.org
> Subject: apache + tomcat + JK connector configuration
>
>
> Hello,
>
>
>
> Has anyone had any success in configuring Apache (2.0.53) with Tomcat
> (4.1.29) in Windows XP, using a recent JK connector ?
>
> We have a server running with the JK2 connector and I'm trying to
> replace it with the latest JK connector (JK-1.2.10), the reason being
> that JK2 is officially unsupported as of 15 Nov 2004 and we're
> experiencing a problem with truncated requests due to this connector.
>
>
>
> In Apache, I configured a worker called worker1 and I send everything
> from context /examples to this worker following
> http://jakarta.apache.org/tomcat/connectors-doc/howto/quick.html.
>
> The configuration looks fine, since I can see in the following lines in
> mod_jk.log:
>
>
>
> [Wed Apr 13 18:49:13 2005] [debug]
> uri_worker_map_add::jk_uri_worker_map.c (269): exact rule
> /examples=worker1 was added
>
> [Wed Apr 13 18:49:13 2005] [debug] build_worker_map::jk_worker.c (219):
> creating worker worker1
>
> [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (125):
> about to create instance worker1 of ajp13
>
> [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (138):
> about to validate and init worker1
>
> [Wed Apr 13 18:49:13 2005] [debug] ajp_validate::jk_ajp_common.c (1781):
> worker worker1 contact is 'localhost:6969'
>
>
>
> However, if I send a request, it doesn't get through and I get an error
> message in the browser.
>
> The log shows:
>
> [Wed Apr 13 18:50:16 2005] [info]
> ajp_connect_to_endpoint::jk_ajp_common.c (877): Failed connecting to
> tomcat. Tomcat is probably not started or is listening on the wrong
> host/port (127.0.0.1:6969). Failed errno = 61
>
> [Wed Apr 13 18:50:16 2005] [info]  ajp_send_request::jk_ajp_common.c
> (1227): Error connecting to the Tomcat process.
>
>
>
> What should I change in Tomcat configuration to have it work with JK
> instead of JK2 ?
>
> It is of course started and listening on port 6969. The configuration in
> server.xml looks like this:
>
>
>
> <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
>
> port="6969" minProcessors="5" maxProcessors="75" enableLookups="true"
> redirectPort="8443" acceptCount="100" debug="0"
> connectionTimeout="20000" useURIValidationHack="false"
> disableUploadTimeout="true"/>
>
>
>
> Thanks.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to