You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2010/06/25 13:29:49 UTC
[jira] Created: (QPID-2695) VirtualHostConfigRecoveryHandler can
NPE or bind to the wrong exchange on binding recovery
VirtualHostConfigRecoveryHandler can NPE or bind to the wrong exchange on binding recovery
------------------------------------------------------------------------------------------
Key: QPID-2695
URL: https://issues.apache.org/jira/browse/QPID-2695
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.6, 0.7
Reporter: Robbie Gemmell
Fix For: 0.7
VirtualHostConfigRecoveryHandler.binding() can NPE if an exchange isnt found when recovering a binding to a queue which also doesnt exist. Additionally, if the NPE (which will occur in an error log statement) does not occur because the queue does exist, then the binding can be created to the default exchange in error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2695) VirtualHostConfigRecoveryHandler can
NPE or bind to the wrong exchange on binding recovery
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2695:
---------------------------------
Status: Ready To Review (was: In Progress)
> VirtualHostConfigRecoveryHandler can NPE or bind to the wrong exchange on binding recovery
> ------------------------------------------------------------------------------------------
>
> Key: QPID-2695
> URL: https://issues.apache.org/jira/browse/QPID-2695
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.7
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.7
>
>
> VirtualHostConfigRecoveryHandler.binding() can NPE if an exchange isnt found when recovering a binding to a queue which also doesnt exist. Additionally, if the NPE (which will occur in an error log statement) does not occur because the queue does exist, then the binding can be created to the default exchange in error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2695) VirtualHostConfigRecoveryHandler can
NPE or bind to the wrong exchange on binding recovery
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911093#action_12911093 ]
Robbie Gemmell commented on QPID-2695:
--------------------------------------
Behaviour updated to prevent NPE while logging, and abort binding recoery if the exchange doesnt exist rather than continue and have the binding factory use the default exchange instead.
> VirtualHostConfigRecoveryHandler can NPE or bind to the wrong exchange on binding recovery
> ------------------------------------------------------------------------------------------
>
> Key: QPID-2695
> URL: https://issues.apache.org/jira/browse/QPID-2695
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.7
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.7
>
>
> VirtualHostConfigRecoveryHandler.binding() can NPE if an exchange isnt found when recovering a binding to a queue which also doesnt exist. Additionally, if the NPE (which will occur in an error log statement) does not occur because the queue does exist, then the binding can be created to the default exchange in error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-2695) VirtualHostConfigRecoveryHandler can
NPE or bind to the wrong exchange on binding recovery
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-2695:
------------------------------------
Assignee: Robbie Gemmell
> VirtualHostConfigRecoveryHandler can NPE or bind to the wrong exchange on binding recovery
> ------------------------------------------------------------------------------------------
>
> Key: QPID-2695
> URL: https://issues.apache.org/jira/browse/QPID-2695
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.7
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.7
>
>
> VirtualHostConfigRecoveryHandler.binding() can NPE if an exchange isnt found when recovering a binding to a queue which also doesnt exist. Additionally, if the NPE (which will occur in an error log statement) does not occur because the queue does exist, then the binding can be created to the default exchange in error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org