Bug 839715
| Summary: | Log at a higher level than 'Debug' for ActionProcessingPipeline exceptions | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> |
| Component: | JBossESB | Assignee: | Nobody <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.2.0 GA | CC: | maurizio.antillon, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Description of problem: ActionProcessingPipeline logs errors at 'DEBUG' level. This can hide important information, could we turn this up to 'INFO' at least? Here's the suggested change area: catch (final Exception ex) { final long procTime = System.nanoTime() - actionStart; if (LOGGER.isDebugEnabled()) { LOGGER.debug("Unexpected exception caught while processing the action pipeline",ex); It's understood that processing will still continue (hence the low level in the first place), but turning the error up a little will help bring attention to things that could otherwise be lost. Example: If BusinessRulesProcessor fails to parse rules for some reason, we'd get a message in the log like this: 2012-07-12 10:32:39,756 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-32-thread-1) No fault address defined for fault message!... Where turning up logging to DEBUG reveals this: 2012-07-12 10:32:39,742 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-32-thread-1) Unexpected exception caught while processing the action pipeline org.jboss.soa.esb.actions.ActionProcessingException: Generation raised the following errors: [DialectError message='Unable to wire compiled classes, probably related to compilation failures:[Error: no such identifier: FIRMA] [Near : {... FIRMA.length ....}] ^ [Line: 1, Column: 1]'] at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:134) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649)