On 12.02.2012 01:44, modjkl...@comcast.net wrote:
For example, if a socket connection is established and AJP transmission occurs, even though it's only one way, would GlassFish have to be listening for this to happen? Would GlassFish have to reply via AJP to establish a socket? That sort of thing. What does the log file tell us about the communication between Apache and GlassFish, and what does it not tell that we would need to know to pinpoint the problem, etc.?
Yes, without Glassfish at least listening to 8009 you would have seen something different in the mod_jk logs, namely an error during connect and not a message that says it is sending a request there.
Since you built mod_jk from source: the source distribution contains a nice httpd-jk.conf and workers.properties file which is a good starting point for configuration. I'm not saying it will fix your problem, because it really looks it is on the Glassfish side, but e.g. that configuration contains a cping/cpong test for every new configuration. If cping/cpong already fails, it would be likely that Glassfish is listening on the port but doesn't expect AJP13 as the protocol etc.
The log message from Glassfish you posted indicates, that Glassfish thinks it never received a valid request and thus closed the "idle" connection after 30 seconds. So either something eats the packet in between Apache and Glassfish (not very likely on localhost, since you could establish the connection), or the request is buggy, e.g. contains invalid headers like a wrong content-length making Glassfish to wait for more data.
Unfortunately you dropped that part of mod_jk debug output as "hex data" :( When increasing JkLogLevel to "trace" mod_jk will do a full dump of the request. Using "debug" will only dome the first one or two KB of each packet.
Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
