You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2012/07/06 11:24:34 UTC
[jira] [Created] (QPID-4112) Queue's alternate exchange
(non-mandatory) does not survive broker restart
Keith Wall created QPID-4112:
--------------------------------
Summary: Queue's alternate exchange (non-mandatory) does not survive broker restart
Key: QPID-4112
URL: https://issues.apache.org/jira/browse/QPID-4112
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.17
Reporter: Keith Wall
Assignee: Keith Wall
If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4112) Queue's alternate (non-mandatory)
exchange does not survive broker restart
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4112:
-----------------------------
Description:
If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
This problem is reported to the logs in the following manner:
{code}
2012-07-06 10:12:28,861 ERROR [main] (VirtualHostConfigRecoveryHandler.java:376) - Unknown exchange id a403aba4-416d-3d12-b33c-8c7e2792ee78, cannot bind queue with id e7b05050-fc46-3e5b-9c06-6c58ace881ce
{code}
was:If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
> Queue's alternate (non-mandatory) exchange does not survive broker restart
> ----------------------------------------------------------------------------
>
> Key: QPID-4112
> URL: https://issues.apache.org/jira/browse/QPID-4112
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Keith Wall
>
> If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
> This problem is reported to the logs in the following manner:
> {code}
> 2012-07-06 10:12:28,861 ERROR [main] (VirtualHostConfigRecoveryHandler.java:376) - Unknown exchange id a403aba4-416d-3d12-b33c-8c7e2792ee78, cannot bind queue with id e7b05050-fc46-3e5b-9c06-6c58ace881ce
> {code}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4112) Queue's alternate (non-mandatory)
exchange does not survive broker restart
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4112:
-----------------------------
Summary: Queue's alternate (non-mandatory) exchange does not survive broker restart (was: Queue's alternate exchange (non-mandatory) does not survive broker restart )
> Queue's alternate (non-mandatory) exchange does not survive broker restart
> ----------------------------------------------------------------------------
>
> Key: QPID-4112
> URL: https://issues.apache.org/jira/browse/QPID-4112
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Keith Wall
>
> If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Assigned] (QPID-4112) Queue's alternate (non-mandatory)
exchange does not survive broker restart
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall reassigned QPID-4112:
--------------------------------
Assignee: Robbie Gemmell (was: Keith Wall)
Patch applied. Robbie, could you please review?
> Queue's alternate (non-mandatory) exchange does not survive broker restart
> ----------------------------------------------------------------------------
>
> Key: QPID-4112
> URL: https://issues.apache.org/jira/browse/QPID-4112
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
>
> If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
> This problem is reported to the logs in the following manner:
> {code}
> 2012-07-06 10:12:28,861 ERROR [main] (VirtualHostConfigRecoveryHandler.java:376) - Unknown exchange id a403aba4-416d-3d12-b33c-8c7e2792ee78, cannot bind queue with id e7b05050-fc46-3e5b-9c06-6c58ace881ce
> {code}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4112) Queue's alternate (non-mandatory)
exchange does not survive broker restart
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4112:
-----------------------------
Status: Ready To Review (was: In Progress)
> Queue's alternate (non-mandatory) exchange does not survive broker restart
> ----------------------------------------------------------------------------
>
> Key: QPID-4112
> URL: https://issues.apache.org/jira/browse/QPID-4112
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Keith Wall
>
> If I assign a durable queue an alternate exchange then that setting should survive a broker restart. This currently only happens for mandatory exchanges (amq.direct etc), if I choose a custom exchange, then the setting is lost.
> This problem is reported to the logs in the following manner:
> {code}
> 2012-07-06 10:12:28,861 ERROR [main] (VirtualHostConfigRecoveryHandler.java:376) - Unknown exchange id a403aba4-416d-3d12-b33c-8c7e2792ee78, cannot bind queue with id e7b05050-fc46-3e5b-9c06-6c58ace881ce
> {code}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org