Closed patbos closed 9 years ago
jmxtrans project » jmxtrans-agent #46 SUCCESS This pull request looks good (what's this?)
Thanks @patbos, shame on me, I work for CloudBees and I did not test jmxtrans-agent with Jenkins!
I propose to write the message with System.out.println()
, would this be ok?
Cyrille
jmxtrans project » jmxtrans-agent #47 SUCCESS This pull request looks good (what's this?)
No problem, I will not tell anyone at CloudBees ;) Changed to System.out.println instead.
Patrik
Hi @patbos, I checked the code, why would we need to just modify this call and not all the other calls to java.util.logging?
It is the only log call that happens before Jenkins own logging configuration has been initialized. Have not figured out how the logging configuration in Jenkins works but for some reason it will be "corrupted" when calls to java.util.Logger happen before that.
Hello @patbos. Can you try jmxtrans-agent 1.0.8. I replaced java.util.logger
by an internal logger framework to prevent these kind of issues.
This internal logger is an alternate solution for the problem that you solved with this pull request.
https://github.com/jmxtrans/jmxtrans-agent/releases/tag/jmxtrans-agent-1.0.8
Thanks! Great stuff! It did the trick for me. I close this PR now.
Tried to use jmxtrans-agent on a Jenkins master and since it started logging with JUL before Jenkins initialized is JUL configuration, the logging in Jenkins became very strange. By just removing the initial logging in the agent logging the issue was resolved.