[esb-issues] [JBoss JIRA] Reopened: (JBESB-1564) CourierException should be visible on higher than DEBUG level

[Jiri Pechanec (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]

Jiri Pechanec reopened JBESB-1564:
----------------------------------

             
Hi, I wrote at least INFO level not exactly INFO level so according to table
WARN	Likely to be a problem, or it could be JBoss detected a problem it can recover from

Or you would prefer to have another JIRA issue requesting to provide application feedback?

> 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