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

Investigate and reduce the number of Errors, Exception, and SEVERE events from server.log #7805

Closed
kcondon opened this issue Apr 14, 2021 · 3 comments

Comments

@kcondon
Copy link
Contributor

kcondon commented Apr 14, 2021

SEVERE events are ones whose level is SEVERE according to Payara.
Errors and Exceptions may be WARNING or INFO level but nonetheless contains important info.

The search strings are "SEVERE" "Error" and "Exception"

@PaulBoon
Copy link
Contributor

Yes, every time when looking into the server.log I have to take a deep breath ...
see my issue: #5749

@eunices
Copy link
Contributor

eunices commented Feb 16, 2022

Hello, just to add onto this issue.

Recently we also noticed EZIDException in server.log. Also mentioned in https://groups.google.com/g/dataverse-community/c/hge7q5xsjh4/m/NMJB3K6YAgAJ. It isn't fatal according to @qqmyers. Could consider removing the severe log for DOIEZIdServiceBean.java especially since EZID is no longer used.

[SEVERE] [] [edu.harvard.iq.dvn.core.index.DOIEZIdServiceBean] [tid: _ThreadID=65 _ThreadName=RunLevelControllerThre
  Other Error on ezidService.login(USERNAME, PASSWORD) - not EZIDException ]] 

@pdurbin
Copy link
Member

pdurbin commented Nov 12, 2023

Let's open more targeted issues, please. Smaller chunks.

@pdurbin pdurbin closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants