2:23 p.m.
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
12:12 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1564) CourierException should be visible on higher than DEBUG level
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]
Work on JBESB-1564 started by Mark Little.
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
8:58 p.m.
New subject: [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_12401660 ]
Mark Little commented on JBESB-1564:
------------------------------------
No, those are debug statements. INFO is for something completely different. Read
http://wiki.jboss.org/wiki/Wiki.jsp?page=UsageOfLoggingLevels for the rules.
Now if the debug statements aren't accompanied by exceptions or ways of informing the
application code that something has gone wrong, there may be something to look at.
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
8:58 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1564) CourierException should be visible on higher than DEBUG level
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]
Mark Little closed JBESB-1564.
------------------------------
Resolution: Rejected
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
4:53 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1564) CourierException should be visible on higher than DEBUG level
[ 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
11:05 a.m.
New subject: [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
11:07 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1564) Couriers should differentiate transport exceptions from other sources of exception
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]
Kevin Conner updated JBESB-1564:
--------------------------------
Summary: Couriers should differentiate transport exceptions from other sources of
exception (was: CourierException should be visible on higher than DEBUG level)
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
12:07 p.m.
New subject: [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_12401735 ]
Tom Fennelly commented on JBESB-1564:
-------------------------------------
Obviously these exceptions can all extend CourierException.
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
12:26 p.m.
New subject: [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_12401740 ]
Kevin Conner commented on JBESB-1564:
-------------------------------------
obviously ;).
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
12:37 p.m.
New subject: [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
12:55 p.m.
New subject: [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
12:07 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1564) Couriers should differentiate transport exceptions from other sources of exception
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]
Work on JBESB-1564 started by Mark Little.
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
12:14 a.m.
New subject: [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_12401839 ]
Mark Little commented on JBESB-1564:
------------------------------------
Hi Jiri. As you can see, there was some confusion as to what you meant by the original
issue. I think it's sorted now though :)
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
3:02 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1564) Couriers should differentiate transport exceptions from other sources of exception
[ http://jira.jboss.com/jira/browse/JBESB-1564?page=all ]
Mark Little closed JBESB-1564.
------------------------------
Resolution: Done
Added new exceptions for errors during binding/lookup, configuration, transport
(delivery/receipt) and parameter/result marshal/unmarshal.
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
5958
days inactive
5971
days old
13 comments
4 participants
participants (4)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)
-
Mark Little (JIRA)
-
Tom Fennelly (JIRA)