Red Hat Bugzilla – Bug 485105
Clean up GateKeeper exceptions in logs
Last modified: 2011-01-31 12:48:18 EST
Description of problem:
There are a large number of exceptions in the logs coming from GateKeeper. Each one needs to be reviewed to see whether it is unexpected and is likely a defect or if the exception is acceptable. If it is the latter, then we should not be logging the exception, certainly not a full stack trace. I will add some of the exceptions as attachments.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 331583 [details]
ClassNotFoundException for process that cannot be found
This is a ClassNotFoundException from a process that cannot be found. My understanding is that this exception gets thrown when a process is removed. It is probably worth investigating what can be done to prevent the exception. If we cannot prevent it, we should do whatever we can to avoid having the entire stack trace logged if this exception is in fact tolerable.
Created attachment 331587 [details]
NullPointerException during SLABreachWarningAction initialization
Created attachment 331590 [details]
NullPointerException in BaseProcessAction.getProductQueueUsers()
Bugs are no longer tracked under this classification. CSP is now monitored in
Other | Customer Portal | Integrated app: JBoss CSP.
Please refile any current defect records or RFEs under the current