one question: were you able to get rid of the mod_jk2 error at startup in apache ([error] mod_jk child init 1 0) that you wrote about earlier?
also:
---jk2.properties --- #list of needed handlers handler.list=apr,channelSocket,request
#Set the derault port for the channelSocket channelSocket.port=8089
#Information about a UNIX domain socket - we don't have this. Supposedly, the #UNIX domain socket is used for speed only #if this is used, add "channelUnix" to the handler.list above #channel.Unix.file=/home/gmh2441/uPortal/Tomcat_4-0-4/work/jk2.socket
#Dynamic library serverRoot=/opt/apache
# This will enable the starting of the Tomcat from mod_jk2 apr.jniModeSo=/opt/apache/modules/mod_jk2.so
---jk2.properties ---
And here begin my questions.
- I cannot find a "jk2.socket" file anywhere - is this somewhere in the Tomcat configs?
i believe that the file jk2.socket should be created on the tomcat side when tomcat starts up and reads the jk2.properties file (i think that the file is read if you have defined a jk2 connector in the server.xml file). however, i see that you have the line for creating this socket commented out and you also don't list the unix domain socket (channelUnix) in the handler list handler.list.
- notice the directory "/apache" - this is acutally a symbolic link (I'm
on a UNIX system) - the directory is actually called "httpd-2.0.45" -
I've tried using the different names for it, and it doesn't seem to
matter - or does it?
it shouldn't matter.
- as far as the UNIX domain socket and dynamic library go, the document said that without the dynamic library section the UNIX domain socket would fail, but a regular TCP/IP socket would still work. but UNIX domain sockets were much, much faster. So does that mean I should removed the part about the dynamic library if I'm using TCP/IP sockets?
Here is workers2.properties, found in {Apache}/conf
---workers2.properties --- [shm] file=/var/adm/httpd-shm.mod_jk2 size=1048576
# Example socket channel [channel.socket:poivre.ucs.louisiana.edu:8089] info=Ajp13 forwarding over socket tomcatId=poivre.ucs.louisiana.edu:8089
#Needed for UNIX domain socket - but we don't have that #[channel.un:/home/gmh2441/uPortal/Tomcat_4-0-4/work/jk2.socket] #tomcatId=poivre.ucs.louisiana.edu:8089 #debug=0
# define the worker [ajp13:poivre.ucs.louisiana.edu:8089] #This uses the TCP/IP socket instead of the UNIX domain socket channel=channel.socket:poivre.ucs.louisiana.edu:8089 #Uncomment the next line to use the UNIX domain socket #channel=channel.un:/home/gmh2441/uPortal/Tomcat_4-0-4/work/jk2.socket
#Announce a "status" worker [status:status]
# Map the Tomcat examples webapp to the Web server uri space [uri:/examples/*] info=Map the whole webapp
worker=ajp13:poivre.ucs.louisiana.edu:8089 #Uncomment the next line to use the UNIX domain socket #worker=ajp13:/home/gmh2441/uPortal/Tomcat_4-0-4/work/jk2.socket #info=Map the whole examples webapp
[uri:/jkstatus/*] worker=status:status
---workers2.properties ---
Something else I've seen, under that "#Example socket channel" entry is that the port and host need to be explicity set, thusly:
port=8089 host=130.70.132.204 (127.0.0.1 for localhost)
- Does this info have to be there as well?a
All this configuration info is based on the document on Apache 2, Tomcat
4.0.4 and mod_jk2 I found at http://www.pubbitch.org/jboss/mod_jk2.html
- and according to this document, once these config files have been
written and installed in the correct places, I need to start Tomcat,
then Apache. First, I should view a "normal" tomcat connection by
referencing a URL ending in 8080, or the port that the standard http
connector is on. Then, (assuming the URL has been mapped in
workers2.properties)(like "/examples/*", I assume) try the equivalent
URL by connecting to Apache instead - I take it that this last sentence
means that if the first URL
I viewed was, say, http://poivre.ucs.louisiana.edu:8080/examples, the
next URL I should try would be http://poivre.ucs.louisiana.edu/examples
- and I should get the same result, if the connector is working.
Well, according to that "status" worker, and my Apache log, the mod_jk2
connector is installed and working fine. However, all I get going to
that second URL is a blank page - even in the source of the page, all
that's there is <html><body></body></html>. A httpd-xfer log file I have
shows that each request returns a 400 (Bad Request), however when I go
to /jkstatus instead, I get a 200 and a page with tables, showing
various values and other information. I have tried this in several
different browsers - that is one reason I haven't been using "localhost"
but instead use my server's name - I can try it on a nearby PC as well.
None of the docs I've found as yet tell me what to do if things don't go
right - I'm not sure just where to look to solve this. I would
appreciate any ideas/comments/questions/etc.
have you looked at all of the tomcat log files (catalina.out, etc) to see if there are any errors? i've noticed that errors will not be identified w/ an 'error' tag but will be embedded in w/ the rest of the informational logging messages.
i have not tried using tcp/ip sockets to see if i get the same results that you do. but, i will try it to see if i get better results.
cheers,
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
