-
Notifications
You must be signed in to change notification settings - Fork 305
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
Logging service hungs on first change of logging levels #1680
Comments
can you give a bit more detail please? What changes do you make? When you say "console logging" do you mean starting Payara Server in verbose mode? |
No changes. Just press "Save" button on Log Levels page on fresh payara installation (downloaded today a hour ago), no config changes, just defaults. This adds line com.sun.enterprise.server.logging.GFFileHandler=OFF to ${DOMAIN_DIR}/config/logging.properties in my case: /opt/payara41/glassfish/domains/domain1/config/logging.properties Switching com.sun.enterprise.server.logging.GFFileHandler to INFO resumes logging as expected. |
Saying Admin console I meant "Admin console" ;) |
Looking in to it, I can see that the default logging.properties has changed between 171 and 172. I'm not sure what brought the change in, yet, but it seems like GFFileHandler is set to OFF by default, but ignored until the save button is pressed. |
Anyway a simple workaround exists, but such a behaviiour is a bit confusing to customers. |
Created internal issue |
Thank you! |
Description
When saving changes on Configurations -> server-config -> Logger Settings -> Log Levels page of Admin console logging hungs because this operation adds property
com.sun.enterprise.server.logging.GFFileHandler=OFF
to ${DOMAIN_DIR}/config/logging.properties
When Switching to INFO logging resumes.
Steps to reproduce (Only for bug reports)
Environment
The text was updated successfully, but these errors were encountered: