You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2008/10/30 12:15:44 UTC

[jira] Updated: (QPID-584) Client allows RuntimeExceptions to be silently swallowed.

     [ https://issues.apache.org/jira/browse/QPID-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-584:
----------------------------------

    Fix Version/s:     (was: M4)

Descoping items not being worked on for M4 into Unknown Fix Version for now

> Client allows RuntimeExceptions to be silently swallowed.
> ---------------------------------------------------------
>
>                 Key: QPID-584
>                 URL: https://issues.apache.org/jira/browse/QPID-584
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>
> Currently RuntimeErrors such as; a log4j classpath problem where an older version of log4j causes the isTraceEnabled/trace methods to be unavailable; are only sent to the ExceptionListener, if there is no exception listener then the message is silently dropped. An error level logging event should occur, to provide feedback to the client.
> This is also the reason that we can't see why the Connection is not connecting and sticking in NOT_STARTED. Most probably a log4j compatibility issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.