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

["Martin Ritchie (JIRA)" <qp...@incubator.apache.org>]

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

Martin Ritchie closed QPID-584.
-------------------------------

    Resolution: Fixed

The particular problem with NoSuchMethodErrors being thrown as a result of an old log4j jar being used with slf4j has been removed.

All trace() method calls are gone from the client and manually throwing such an error in the FieldTable writeToBuffer (Where this first occured) is now correctly reported as an error creating the connection.

> 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.