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

Trace Specification logging level "off" doesn't work #6123

Closed
kbaillie opened this issue Jan 7, 2019 · 2 comments · Fixed by #6244
Closed

Trace Specification logging level "off" doesn't work #6123

kbaillie opened this issue Jan 7, 2019 · 2 comments · Fixed by #6244
Assignees
Labels
release bug This bug is present in a released version of Open Liberty release:19001 team:Lumberjack

Comments

@kbaillie
Copy link
Contributor

kbaillie commented Jan 7, 2019

When setting the trace specification with the off logging level, for example: <logging traceSpecification="com.ibm.ws.*=all:com.ibm.ws.kernel.*=off"/> the relevant code does not turn off logging.

@fmhwong fmhwong added the release bug This bug is present in a released version of Open Liberty label Jan 16, 2019
@fwji
Copy link
Contributor

fwji commented Jan 16, 2019

It seems like a user cannot turn off a subset of traces if the superset of the subset is turned on

@fwji
Copy link
Contributor

fwji commented Jan 18, 2019

In TraceComponent.updateTraceSpec(), when we are looping through log levels to enable all log levels and up, we didn't include TraceLevel.off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release bug This bug is present in a released version of Open Liberty release:19001 team:Lumberjack
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants