[jira] [Commented] (QPID-464) Fix Broker Exception Handling

["Keith Wall (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179436#comment-13179436 ] 

Keith Wall commented on QPID-464:
---------------------------------

I think the new uncaught exception handler should also try to log the exception to the Broker log file (using log4j) in addition to stderr.   I say this as a) our users are already accustomed to checking this log file b) stderr many be swallowed by job control system or lost through careless redirection.
  
                
> Fix Broker Exception Handling
> -----------------------------
>
>                 Key: QPID-464
>                 URL: https://issues.apache.org/jira/browse/QPID-464
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: M2.1
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>
> Firstly need to define Exception handling policies and apply consistently, then need to look at specific resolution for the two linked JIRAs too.
> The Java broker does not define or implement any form of consistent exception handling.  In particular unrecoverable erros are at best handled by logging and then attempting to carry on regardless.  
> I would argue that such errors should be followed by an immediate System.exit ... however others may wish this to be configurable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org