-
Notifications
You must be signed in to change notification settings - Fork 488
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
Too much logging messages #5749
Comments
|
Another fairly common warning I am seeing in every one of my local server logs:
That warning was included in a snippet in #3801, as well as a dozen server logs included in RT and community group emails. Looking up the error in Stack Overflow, I found this answer that suggests "a resource method with Also, I do not have harvesting set up on my localhost, but still I see that warning, as well as other harvesting related msg's in the log.
|
I'm getting the "response has already been committed" jsf error only when I publish both the dataset and its parent dataverse at the same time ("do you want to publish both? popup), possibly because both success messages aren't displayed. I would venture that is a fairly rare occurrence. Does anyone know of a state that would cause the error to display every second as described by Paul above? |
Logging issues addressed so far:
|
A few things to be aware of when viewing Splunk counts:
|
Just installed our fork of 4.10.1 and was hoping to get a bit cleaner logging,
however I still got a lot of warnings swamping my log file.
The most annoying one I get more then once every second:
This has been mentioned in:
#4427 (comment)
The other one is even 'SEVERE':
Not sure which action causes this, but I see it quite often.
Possible it is related to:
"as a system administrator, I'd like glassfish to not throw exceptions from (from dataverseuser.xhtml) during normal operations" #5446
I would love to get rid of those, so the logs are better to use.
Maybe there is a fast way to suppress them while the real problem is being fixed?
The text was updated successfully, but these errors were encountered: