Hi all,
Don't know if anyone remembers my original mail about this from
20/1/06, but it's just happened again. I've pasted the section where the
connector went nuts below (at end of mail). This is the first thing to
appear in mod_jk's log. Then, about 30 seconds later, The JBoss server
on the
Well I'm glad someone else is getting this, even if you have no idea
either. We wondered if we were missing some configuration from
workers.properties, since the quick start section
(http://tomcat.apache.org/connectors-doc/howto/quick.html) on
Tomcat's site gives an example minimum
Jonathon Reeve wrote:
Well I'm glad someone else is getting this, even if you have no idea
either. We wondered if we were missing some configuration from
workers.properties, since the quick start section
(http://tomcat.apache.org/connectors-doc/howto/quick.html) on
Tomcat's site gives an example
Thanks Mladen for your suggestions.
But I have to make clear that we just started with a minimum configuration
for the workers.
So we had 3 workers defined using the following config:
worker.worker_1.host=localhost
worker.worker_1.port=8009
worker.worker_1.type=ajp13
operation.
Byron
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Friday, January 20, 2006 5:19 AM
To: Tomcat Users List
Subject: Re: mod_jk connection problem after couple of days or a week
Jonathon Reeve wrote:
Well I'm glad someone else is getting this, even if you
Hello!
We have exactly the same problem with the following configuration:
OS: Windows Server 2003 Standard Edition
Apache 2.0.54
mod_jk 1.2.14
Tomcat 5.5.9/5.5.12
JBoss 2.4.4
Our website basically serves JSP-Files and custom webapps, using the Tomcat
instance as Servlet/JSP
