Excessive logging to rhq-agent-wrapper.log
Environment
- JBoss Operations Network (JON) 2.4.1
- ESB plugins for JON 2.4.1
- JON Agent started with:
./rhq-agent-wrapper.sh start
Issue
- Excessive logging to rhq-agent-wrapper.log
- Our rhq-agent-wrapper.log file is filled up with the following exceptions:
org.mc4j.ems.connection.EmsException: Could not load attribute value Connection failure Failed to authenticate principal=null, securityDomain=jmx-console
and it's current size is more then 5GB. Why is this happening?
Resolution
When starting JON Agent using rhq-agent-wrapper.sh script, rhq-agent-wrapper.log file will be the standard output of the JON Agent and if there is any system exception within the JON Agent, it will be logged in the rhq-agent-wrapper.log file.
However, there is an error in the JON ESB plugin where exception stack traces are dumped to the standard output. This has been already reported in JIRA - JBESB-3566 and should be resolved in future releases of ESB plugins.
Diagnostic Steps
Check the rhq-agent-wrapper.log file and confirm that the exceptions logged in the log file are from ESB plugin.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments