[esb-issues] [JBoss JIRA] Commented: (JBESB-1564) CourierException should be visible on higher than DEBUG level
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=comments#action_12401723 ]
Kevin Conner commented on JBESB-1564:
-------------------------------------
The issue here is not the logging of the exception, debug is the appropriate level for
that.
The real issue is that this CourierException is being overused in the JMSCourier (and
probably other places) and that there is no way to differentiate from a communications
exception (missing endpoint etc) and a problem with the message.
The ServiceInvoker is correctly handling the problem of communications exceptions but
cannot address the message problems unless we define a different exception on that API.
CourierException should be visible on higher than DEBUG level
-------------------------------------------------------------
Key: JBESB-1564
URL: http://jira.jboss.com/jira/browse/JBESB-1564
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Mark Little
Fix For: 4.2.1 CP2
When the Courier exception is thrown in courier (like Failed to serialize ESB message in
JMS courier) the excpetion is logged by ServiceInvoker only at DEBUG level
logger.debug("Badly formed EPR [" + targetEPR + "] for Service [" +
service + "] and Message ["+message.getHeader()+"]. " +
e.getMessage());
This makes identification of error extremly difficult and as it is erroneous state it
should be logged at at least INFO level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira