Apache 3.2.3, mod_jk and JBoss 3.2.3

[erik777]

On a machine where Apache HTTPD and JBoss 3.0.6 with Tomcat is already configured to work together, I installed and started JBoss 3.2.3 in its place.

The good news is it works without having to configure JBoss/Tomcat. I was able to immediately access JBoss applications via port 80 through Apache HTTPD.

However, it outputs a ton of continuous hex dumps to STDOUT, slowing down the server and rapidly filling the logs with dump data. It is continuous so long as Apache HTTPD is running, and stops when I stop the Apache HTTPD service.

Moreover, the access log shows that it is calling the web-console/Invoker continuously.

HOW DO I STOP THIS OUTPUT?!? Below is an extract of the log where it begins to dump hex data, including the output preceding it where it starts the Invoker.

2004-01-30 21:55:45,076 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Programs/JBoss/jboss-3.2.3/server/default/deploy/http-invoker.sar/invoker.war/
2004-01-30 21:55:45,256 DEBUG [org.apache.tomcat.util.threads.ThreadPool] Getting new thread data
2004-01-30 21:55:45,256 DEBUG [org.apache.jk.common.ChannelSocket] Accepting ajp connections on 8009
2004-01-30 21:55:45,326 DEBUG [org.apache.jk.common.ChannelSocket] Accepted socket Socket[addr=/127.0.0.1,port=1515,localport=8009]
2004-01-30 21:55:45,357 DEBUG [org.apache.tomcat.util.threads.ThreadPool] Getting new thread data
2004-01-30 21:55:45,367 DEBUG [org.apache.jk.common.ChannelSocket] receive()
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@4e0e90 8192 0 4 = 4
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.MsgAjp] Received 397 18
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@4e0e90 8192 4 397 = 397
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] Call next 0 org.apache.jk.common.HandlerRequest@987197
2004-01-30 21:55:45,427 DEBUG [org.apache.jk.common.HandlerRequest] Handling 2
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] RECEIVE_PACKET ??
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] receive()
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@62610b 8192 0 4 = 4
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.MsgAjp] Received 516 18
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@62610b 8192 4 516 = 516
2004-01-30 21:55:45,457 INFO [org.apache.jk.common.JkInputStream] Receiving: getting request body chunk 516 516
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.MsgAjp] Body buffer: [B@62610b 4/520
2004-01-30 21:55:45,467 INFO [STDOUT] 12 34 02 04 02 02 ac ed 00 05 73 72 00 2e 6f 72 | .4....??..sr..or
2004-01-30 21:55:45,467 INFO [STDOUT] 67 2e 6a 62 6f 73 73 2e 63 6f 6e 73 6f 6c 65 2e | g.jboss.console.
2004-01-30 21:55:45,467 INFO [STDOUT] 72 65 6d 6f 74 65 2e 52 65 6d 6f 74 65 4d 42 65 | remote.RemoteMBe
2004-01-30 21:55:45,467 INFO [STDOUT] 61 6e 49 6e 76 6f 63 61 74 69 6f 6e e0 4f a3 7a | anInvocation?O?z
2004-01-30 21:55:45,477 INFO [STDOUT] 74 ae 8d fa 02 00 04 4c 00 0a 61 63 74 69 6f 6e | t???...L..action

2004-01-30 21:55:45,076 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Programs/JBoss/jboss-3.2.3/server/default/deploy/http-invoker.sar/invoker.war/
2004-01-30 21:55:45,256 DEBUG [org.apache.tomcat.util.threads.ThreadPool] Getting new thread data
2004-01-30 21:55:45,256 DEBUG [org.apache.jk.common.ChannelSocket] Accepting ajp connections on 8009
2004-01-30 21:55:45,326 DEBUG [org.apache.jk.common.ChannelSocket] Accepted socket Socket[addr=/127.0.0.1,port=1515,localport=8009]
2004-01-30 21:55:45,357 DEBUG [org.apache.tomcat.util.threads.ThreadPool] Getting new thread data
2004-01-30 21:55:45,367 DEBUG [org.apache.jk.common.ChannelSocket] receive()
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@4e0e90 8192 0 4 = 4
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.MsgAjp] Received 397 18
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@4e0e90 8192 4 397 = 397
2004-01-30 21:55:45,417 DEBUG [org.apache.jk.common.ChannelSocket] Call next 0 org.apache.jk.common.HandlerRequest@987197
2004-01-30 21:55:45,427 DEBUG [org.apache.jk.common.HandlerRequest] Handling 2
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] RECEIVE_PACKET ??
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] receive()
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@62610b 8192 0 4 = 4
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.MsgAjp] Received 516 18
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@62610b 8192 4 516 = 516
2004-01-30 21:55:45,457 INFO [org.apache.jk.common.JkInputStream] Receiving: getting request body chunk 516 516
2004-01-30 21:55:45,457 DEBUG [org.apache.jk.common.MsgAjp] Body buffer: [B@62610b 4/520
2004-01-30 21:55:45,467 INFO [STDOUT] 12 34 02 04 02 02 ac ed 00 05 73 72 00 2e 6f 72 | .4....??..sr..or
2004-01-30 21:55:45,467 INFO [STDOUT] 67 2e 6a 62 6f 73 73 2e 63 6f 6e 73 6f 6c 65 2e | g.jboss.console.
2004-01-30 21:55:45,467 INFO [STDOUT] 72 65 6d 6f 74 65 2e 52 65 6d 6f 74 65 4d 42 65 | remote.RemoteMBe
2004-01-30 21:55:45,467 INFO [STDOUT] 61 6e 49 6e 76 6f 63 61 74 69 6f 6e e0 4f a3 7a | anInvocation?O?z
2004-01-30 21:55:45,477 INFO [STDOUT] 74 ae 8d fa 02 00 04 4c 00 0a 61 63 74 69 6f 6e | t???...L..action

[cmoesel]

I am having the same problem... Any solutions?

[darranl]

Have either of you looked at the Log4J configuration?

[erik777]

Add this to your JBOSS_HOME/server/default/conf/log4j.xml:

 <!-- Stop the excessive flooding that jk does by default when apache httpd is talking to it -->
 <category name="org.apache.jk">
 <priority value="WARN"/>
 </category>

Someone responded with fix back in January, but it must have been on another thread.

[cmoesel]

Thanks for the help. I thought about doing this but didn't think it would work, as the hex appears to be coming from STDOUT. But for one reason or another, limiting the jk logging seems to work great. Thanks!