Skip to content

Change JBoss JDK logging policy #2612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
emeroad opened this issue Feb 14, 2017 · 0 comments
Closed
2 tasks done

Change JBoss JDK logging policy #2612

emeroad opened this issue Feb 14, 2017 · 0 comments
Milestone

Comments

@emeroad
Copy link
Member

emeroad commented Feb 14, 2017

Pinpoint team can not manage the JDK logging policy of all third party libs.

  • Google guava and guice use the JDK logger.

We decided to change the JDK logger policy.

  • 1.6.0 : PinpointAgent does not use the JDK logger.
  • 1.6.1+: PinpointAgent uses the JDK logger.

TODO

  • remove thirdparty google guava module
  • add JDK logging option of jboss plugin
@emeroad emeroad added this to the 1.6.1 milestone Feb 14, 2017
@emeroad emeroad changed the title Change JBoss JDK logger option Change JBoss JDK logging policy Feb 14, 2017
emeroad added a commit to emeroad/pinpoint that referenced this issue Feb 14, 2017
emeroad added a commit to emeroad/pinpoint that referenced this issue Feb 28, 2017
emeroad added a commit that referenced this issue Feb 28, 2017
@emeroad emeroad closed this as completed Feb 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant