You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/04/20 11:21:15 UTC

[jira] Created: (QPID-464) Define Exception handling policies and apply consistantly

Define Exception handling policies and apply consistantly
---------------------------------------------------------

                 Key: QPID-464
                 URL: https://issues.apache.org/jira/browse/QPID-464
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker
            Reporter: Rob Godfrey


The Java broker does not define or implement ay form of consitant 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-464:
----------------------------------

    Fix Version/s:     (was: M4)

Moving items not being worked on afaik out of M4 Fix Version

> 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: Aidan Skinner
>
> 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-464:
----------------------------------

             Assignee: Aidan Skinner
          Description: 
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.

  was:
The Java broker does not define or implement ay form of consitant 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.

    Affects Version/s: M2.1
              Summary: Fix Broker Exception Handling  (was: Define Exception handling policies and apply consistantly)

> 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: Aidan Skinner
>             Fix For: M3
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-464) Define Exception handling policies and apply consistantly

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-464:
--------------------------------

    Fix Version/s: M3

> Define Exception handling policies and apply consistantly
> ---------------------------------------------------------
>
>                 Key: QPID-464
>                 URL: https://issues.apache.org/jira/browse/QPID-464
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
>             Fix For: M3
>
>
> The Java broker does not define or implement ay form of consitant 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.
-
You can reply to this email to add a comment to the issue online.