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

Logging service hungs on first change of logging levels #1680

Closed
sgerr opened this issue Jun 15, 2017 · 7 comments · Fixed by #1691
Closed

Logging service hungs on first change of logging levels #1680

sgerr opened this issue Jun 15, 2017 · 7 comments · Fixed by #1691
Assignees
Labels
Type: Bug Label issue as a bug defect
Milestone

Comments

@sgerr
Copy link

sgerr commented Jun 15, 2017

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)

  1. Navigate to Admin console -> Configurations -> server-config -> Logger Settings -> Log Levels page
  2. Press "Save" button

Environment

  • Payara Version: payara-4.1.2.172
  • Edition: Full
  • JDK Version: 8 uXX - Oracle
  • Operating System: Linux
@mikecroft
Copy link
Contributor

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?

@sgerr
Copy link
Author

sgerr commented Jun 15, 2017

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.

@sgerr
Copy link
Author

sgerr commented Jun 15, 2017

Saying Admin console I meant "Admin console" ;)
i. e. web interface on https://localhost:4848

@mikecroft
Copy link
Contributor

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.

@mikecroft mikecroft added Type: Bug Label issue as a bug defect reproducible and removed 1:Wait labels Jun 15, 2017
@sgerr
Copy link
Author

sgerr commented Jun 15, 2017

Anyway a simple workaround exists, but such a behaviiour is a bit confusing to customers.

@mikecroft
Copy link
Contributor

Created internal issue PAYARA-1759

@mikecroft mikecroft added the Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev label Jun 15, 2017
@sgerr
Copy link
Author

sgerr commented Jun 15, 2017

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Label issue as a bug defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants