[esb-issues] [JBoss JIRA] Commented: (JBESB-1564) Couriers should differentiate transport exceptions from other sources of exception
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=comments#action_12401741 ]
Tom Fennelly commented on JBESB-1564:
-------------------------------------
hehehe
Just thought I'd say it coz sometimes 180 degree fixes are implemented for this type
of thing e.g. go from having 0/1 exceptions to an orgy of them... all unrelated etc
Couriers should differentiate transport exceptions from other sources
of exception
----------------------------------------------------------------------------------
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