Hi,

I also could not mod_jk2 working after trying for 2 or 3 days.
I compiled my own but could never get it working.
I tried the combination 
RedHatLinux-7.3 w/2.4.20kernel/JDK-1.4.1_01/tomcat-4.1.18/apache-2.0.44/mod_jk2

I ended my frustration, by using a binary of mod_jk.
If I ever hear of a concrete success story with some info, I may try 
again.

I'm interested in seeing what others say about this.
Mod Parent Up... Woops wrong site.

Oscar

On Wed, 5 Feb 2003, John VANSPRONSSEN wrote:

> Good day,
> 
> Just wondering if anyone at all has successfully gotten mod_jk2 to work
> between Apache and Tomcat on W2K.
> 
> I have installed Apache 2.0.44 right out of the box and Tomcat 4.1.18 here
> at the office. jk2.properties is as it comes in the installation.
> 
> worker2.properties is as follows
> 
> # Define the communication channel 
> [channel.socket:localhost:8009]
> info=Ajp13 forwarding over socket
> tomcatId=localhost:8009
> 
> # Map the Tomcat examples webapp to the Web server uri space
> [uri:/examples/*]
> info=Map the whole webapp
> 
> I get the following in the apache error logs
> 
> [Wed Feb 05 10:31:23 2003] [error] workerEnv.init() create slot epStat.0
> failed
> [Wed Feb 05 10:31:23 2003] [error] lb.service() worker failed 120000 for
> ajp13:localhost:8009
> [Wed Feb 05 10:31:23 2003] [error] lb.service() unrecoverable error...
> [Wed Feb 05 10:31:23 2003] [error] mod_jk.handler() Error connecting to
> tomcat 120000
> [Wed Feb 05 10:38:19 2003] [error] lb.getWorker() reenable
> ajp13:localhost:8009
> [Wed Feb 05 10:38:19 2003] [error] workerEnv.init() create slot epStat.0
> failed
> [Wed Feb 05 10:38:19 2003] [error] lb.service() worker failed 120000 for
> ajp13:localhost:8009
> [Wed Feb 05 10:38:19 2003] [error] lb.service() unrecoverable error...
> [Wed Feb 05 10:38:19 2003] [error] mod_jk.handler() Error connecting to
> tomcat 120000
> 
> This is from a completely new installation of both products and follows the
> directions on the Tomcat site. 
> 
> I have been trying this at home as well but under Apache 1.37, with
> precisely the same results.
> 
> I have looked thru the newsgroups, google, archives etc, and it seems that
> no-one has succesfully used mod_jk2. 
> 
> So rather than point me at documents on a the site, I would like someone who
> knows how this works to simply tell me what is missing from the
> configuration. I have seen a lot of other people asking the same question
> with no resolution that I have been able to locate. The only answers have
> been check the docs on the jakarta site. 
> 
> I currently am running 4 commercial sites using Apache/Resin without any
> difficulty. I thought I would have another look at Tomcat after having
> thrown it out over a year ago. It would appear that not much has changed.
> Given that both Apache and Tomcat are being developed under the same
> roof(more or less) how is it that configuration of mod_jk2 is so difficult
> or error-prone? The next logical question would be, if it is so hard to get
> the Apache/Tomcat connection working, how much more difficult is it to get a
> IIS/Netscape connection working?
> 
> 
> John Vanspronssen
> 
> 
> ---------------------------------------------------------------------
> 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