I have made the same set of modifications and followed the advice on the site you reference. I get the same catalina.out error messages.
If anyone has this working, has looked at the recommendation on the site, some assistance would be appreciated. -----Original Message----- From: Branko Kannenberg [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 29, 2002 8:04 AM To: Tomcat Users List Subject: Re: mod_jk2 - error on tomcat4.0.4 side? Hi Thomas ! I'm also working on the problem to integrate Tomcat 4.0.4 into Apache 2.0.40 (under linux). I came across the same problem you seem to have, but I can't say that I have been succesful, I'm stuck at another problem. In my jk2.properties file I had the following line: apr.NativeSo=${jtc}/lib/libjkjni.so I took this from the nice howto at http://www.pubbitch.org/jboss/mod_jk2.html When I commented it out, suddenly the worker2.properties file was found. Ok, I got a message that APR was not loaded because the library is missing, but I have no idea if this is bad or not. Now I got Apache talking to Tomcat, but with one big problem: Not every HTTP-GET is correctly answered, some GETs are forgotten, this means, that always some pictures in the webpages are missing, sometimes the layout is wrong because the .css file was not transferred. In the Apache error.log I find this lines: [Thu Aug 29 16:04:56 2002] [error] workerEnv.init() create slot epStat.0 [Thu Aug 29 16:04:57 2002] [error] workerEnv.init() create slot epStat.1 [Thu Aug 29 16:05:03 2002] [error] workerEnv.init() create slot epStat.2 [Thu Aug 29 16:05:03 2002] [error] workerEnv.init() create slot epStat.3 [Thu Aug 29 16:05:03 2002] [error] workerEnv.init() create slot epStat.4 I would be very glad if someone could give me a hint here. See below for my configs. While compiling jakarta-tomcat-connectors, I hab another problem: A class CoyoteServerSocketFactory wouldn't compile because some Methods threw Exceptions which the interface didn't (a class from a tomcat .jar). So I deleted those Exceptions (just IOException was left). Then I could build the connectors succesfully. I have no idea if this messed something up (though I don't think so, the Methods just returned null). Had someone else this problems while compiling the connectors? Ok, here is my jk2.properties file: # --- jk2.properties ------------------------ jtc=/home/kannenbe/klinform/software/jakarta-tomcat-4.0.4 serverRoot=/opt/apache2 # list of needed handlers. handler.list=apr,channelSocket,channelUnix,request #handler.list=channelUnix #handler.list=channelSocket # Set the default port for the channelSocket channelSocket.port=8009 # State where the UNIX domain socket is located #channelUnix.file=${jtc}/work/jk2.socket channelUnix.file=/tmp/jk2.socket # Dynamic library #apr.NativeSo=${jtc}/lib/libjkjni.so #---- end of jk2.properties And my worker2.properties: # ---- workers2.properties # Shared memory handling. Needs to be set. [shm] file=/opt/apache2/logs/shm.file size=1048576 # Example socket channel, explicitly set port and host. [channel.socket:localhost:8009] port=8009 host=127.0.0.1 tomcatId=localhost:8009 debug=1 # Example UNIX domain socket [channel.un:/tmp/jk2.socket] tomcatId=localhost:8009 debug=1 # define the worker [ajp13:localhost:8009] channel=channel.un:/tmp/jk2.socket # To use the TCP/IP socket instead, just comment out the above # line, and uncomment the one below #channel=channel.socket:localhost:8009 # Announce a "status" worker [status:status] # Uri mapping [uri:] worker=ajp13:localhost:8009 #worker=ajp13:/home/kannenbe/klinform/software/jakarta-tomcat-4.0.4/work/jk2 .socket [uri:/status/*] worker=status:status #---- end of workers2.properties Ciao, Branko. === Original Message =========================== hi all, I've managed to compile from the CVS source the jakarta-tomcat-connectors project, and configured tomcat4.0.4 and apache2.0.40 with jk2.properties and workers2.properties, accordingly. If I start apache and check the localhost/jkstatus it responds, I guess there's no problem, but on the tomcat-side if I start it up, it starts, but nothing comes back on port 8080, tomcat doesn't listen. In the catalina.out log file the following error message appears: Starting service Tomcat-Standalone Apache Tomcat/4.0.4 [Wed Aug 28 16:01:24 2002] (error ) [jk_config_file.c (261)] config.update(): Can't find config file ${serverRoot}/conf/workers2.properties [Wed Aug 28 16:01:24 2002] ( info ) [jk_config.c (246)] config.setAttribute() Error setting config: file ${serverRoot}/conf/workers2.properties [Wed Aug 28 16:01:24 2002] (error ) [jk_logger_file.c (171)] Initializing log file stderr [Wed Aug 28 16:01:24 2002] (error ) [jk_shm.c (333)] shm.init(): No file [Wed Aug 28 16:01:24 2002] ( info ) [jk_workerEnv.c (403)] workerEnv.init() ok ${serverRoot}/conf/workers2.properties [INFO] ChannelSocket - -JK2: ajp13 listening on tcp port 8009 [INFO] ChannelUn - -JK: listening on unix socket: /usr/local/jakarta-tomcat-4.0.4/work/jk2.socket [INFO] JkMain - -Jk running ID=0 time=3/568 config=/usr/local/jakarta-tomcat-4.0.4/conf/jk2.properties Starting service Tomcat-Apache Apache Tomcat/4.0.4 [Wed Aug 28 16:01:25 2002] ( info ) [jk_jni_aprImpl.c (470)] jkInvoke() invoke 4b9fa760 I have the workers2.properties in /usr/local/apache2/conf, the jk2.properties in /usr/local/jakarta-tomcat-4.0.4/conf. No matters if I put workers2 into tomcat conf lib, error always appears. Does anybody came accross with this situation??? If I install tomcat from the tar, and start it, it works fine, tomcat index appears on port 8080, but when I make the changes according to compilation doc found at http://www.pubbitch.org/jboss/mod_jk2.html it fails with errors witten above. Any idea, or help is greatly appreciated, how to get around with this error. Regards, Thomas ==== End of Original Message ============================== - -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
