[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_12401744 ]
Kevin Conner commented on JBESB-1564:
-------------------------------------
I was trying deliberately to not be prescriptive ;), the exception hierarchy should be
driven by the circumstances of it's use (and explicitly mentioned in the API).
Of course, just because you *can* use the same root doesn't always mean you should.
;)
We need to go through the code and identify what is being thrown and why. We already have
one known issue, the serialisation of the message, and there may be more.
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