Tuesday, September 08, 2009
jBoss Issue Related to Excessive Debugging in Logs
New jBoss installs might store excessive logging due to a malformed comment in log4j.properties that threw JBoss into a debug state on startup.
There was a comment tag in the jboss-log4j.xml file something like
!-- -------------Add new line here à
All of the additional hyphens were causing the SASServer1 to go into debug at boot and fill the log with debug entries
Additional References:
Thanks to Nick Welke for submitting this discovery!
Subscribe to:
Post Comments (Atom)
Posts
1 comments:
Yes, that can be a bit pain.
Deployment wizard should:
a) ask to explode ears (they are needed in packed form only when clustering)
b) put such limits in this jboss-log4j.xml
Thanks for pointing this note, I used to limit per category (com,org,javax to name obvious ones)
Regards
Post a Comment