I am having the same problem... Any solutions?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837757#3837757
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837757
---
Have either of you looked at the Log4J configuration?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837766#3837766
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837766
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
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!
View the original post :
