Would you mind posting the actual configuration files, instead of file snippets (zipped)?
-----Original Message----- From: Douglas, Rory [mailto:[EMAIL PROTECTED]] Sent: June 24, 2002 11:20 AM To: 'Tomcat Users List' Subject: RE: example mod_jk2 configuration for Apache 2.0.39 It looks like the ApacheConfig <Listener> is still in the Java sources for the connectors, but I don't think it has been updated to the new config format for mod_jk2 so it probably won't work. in Server.xml, the important things are the className and protocolHandlerClassName attributes of the AJP <Connector>. these should be: protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" and className="org.apache.coyote.tomcat4.CoyoteConnector" Remember to match up the port number in all 3 place (in <connector> in Server.xml, in jk2.properties, and in worker2.properties) If you use 8009 for your AJP <connector> then you don't need to specify it in jk2.properties. That should be all, no need to mess with web.xml ;-) By the way, I was wrong about how to specify multiple channelSocket ports in jk2.properties. The following method "kind of" works: channelSocket.port=8009 (for the first one) channelSocket.otherone.port=8015 channelSocket.thirdconn.port=8020 etc However, doing this, JK seems to try to open these ports for EACH <Connector> specified in Server.xml, and you get a lot of "Address already bound" exceptions (and a lot of listening ports, because JK just increments the port number each time and trys again). have fun Rory -----Original Message----- From: Liam Morley [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Monday, June 24, 2002 1:43 PM To: Tomcat Users List Subject: Re: example mod_jk2 configuration for Apache 2.0.39 Rory, thank you very much; that'll get me started. I'm guessing you're running with Tomcat4.1; I'm trying this with Tomcat 4.0.4. With JK1, there was a <Listener> you could plug in to your $CATALINA_HOME/conf/server.xml (<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig".../>). Does that still exist? Are there any changes to the server.xml and web.xml that you can point out (for example, the mod_jk2 version of <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" .../>?) Thanks once again, this is a big help. Liam Morley Douglas, Rory wrote: > Hi there > > I haven't set-up anything really complex but the following setup > should work. I haven't got around to trying load-balancing, if anyone > does that and gets it working, please share! > > ------------------------------- > in HTTPD.CONF (in Apache2\conf) > ------------------------------- > LoadModule jk2_module modules/mod_jk2.dll > > ------------------------------------- > in JK2.PROPERTIES (in Tomcat4.1\conf) > ------------------------------------- > I just commented out everything. Note that if you are using an AJP > connector with port other than the default of 8009 you should specify > here (where it says channelSocket.port). If you comment everything out > JK seems to default to 8009 (and then 8010, 8011 and so on if you have > more than one connector). If you want need specific ports for > multiple connectors then specify channelSocket.port multiple times e.g > > channelSocket.port=8014 > channelSocket.port=8018 > > if you have two AJP connectors specified in server.xml with port > numbers 8014 and 8018. > > ---------------------- > in WORKERS2.PROPERTIES > ---------------------- > > I just copied this file from tomcat4.1\jtc-src\jk\conf into > Apache2\conf and edited it a bit. The really important bits seem to be: > > [channel.socket:localhost:8009] > info=Ajp13 forwarding over socket > debug=20 > tomcatId=Tomcat-Standalone > > that actually sets up a worker. I understand that you can specify > > group=someGroupName > > and create groups of workers for load-balancing. I also believe that > every worker created without specfiying a group is in the default > group (I think it is "lb"). > > To map contexts use [uri:] blocks like so: > > [uri:/test] > info=Test context mapping > debug=20 > context=/test > > Again, here you can specify which workers serve that context by > specifying group=groupName > > It's a good idea to keep these parts around too: > > [status:] > info=Status worker, displays runtime informations > > [uri:/jkstatus/*] > info=Display status information and checks the config file for changes. > group=status: > > you can then hit http://yourapacheserver/jkstatus <http://yourapacheserver/jkstatus> and get a loads of > jk info that might help you catch config errors > > There are some docs in tomcat4.1\jtc-src\jk\doc\jk2 that might help > (but they're not great). > > Hope this is useful to someone > cheers > Rory > > -----Original Message---- > From: Jacob Kjome [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] > Sent: Monday, June 24, 2002 11:08 AM > To: Tomcat Users List > Subject: Re: mod_jk2 binary available here > > > Hello Rory, > > Actually, a working version of mod_jk2.dll has already been provided > by Apache here: > > http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/nightly/win32 / <http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/nightly/win3 2/> > > > However, the real issue now is how does one configure all this? Rory, > you would be providing a super service to a lot of people if you would > provide a minimal configuration of mod_jk2 with *all* files involved. > > thanks, > > Jake > > Monday, June 24, 2002, 10:01:13 AM, you wrote: > > DR> Hello all > > DR> I have a working binary of mod_jk2.dll (working with Apache 2.0.39 > on Win2k > DR> Server) if anyone would like to try it out. No guarantees though! > > DR> You can get it here --> http://www.mycgiserver.com/~worrel <http://www.mycgiserver.com/~worrel> > < http://www.mycgiserver.com/%7Eworrel <http://www.mycgiserver.com/%7Eworrel> > > > DR> cheers > > DR> Rory Douglas > DR> Sun Chemical Corporation > DR> (201) 224-4600 x133 > DR> [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > > -- > Best regards, > Jacob mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > >------------------------------------------------------------------------ > >-- >To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
