Skip to content
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

Anything which starts logging too early will disable Quarkus logging #2152

Closed
dmlloyd opened this issue Apr 18, 2019 · 3 comments · Fixed by #33318
Closed

Anything which starts logging too early will disable Quarkus logging #2152

dmlloyd opened this issue Apr 18, 2019 · 3 comments · Fixed by #33318
Assignees
Milestone

Comments

@dmlloyd
Copy link
Member

dmlloyd commented Apr 18, 2019

The upstream LogManager has some stuff in it to prevent this from happening. We should use that stuff.

@gsmet
Copy link
Member

gsmet commented Nov 13, 2019

@dmlloyd do we still consider this an issue?

@dmlloyd
Copy link
Member Author

dmlloyd commented Nov 14, 2019

Yes it's still not solved for Java agents. I think we need a more resilient solution.

@stuartwdouglas
Copy link
Member

Is there anything more we can realistically do here? We document/set the relevant system property every where we can, if a user uses a Java agent and does not set the property then IMHO this is user error, as AFAIK there is nothing we can do in that situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants