| Summary: | Cannot undeploy clustered queue and deploy it again as non-clustered | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Martin Vecera <mvecera> |
| Component: | JBoss Messaging | Assignee: | Dana Mison <dmison> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP02 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-570 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-28 08:01:08 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Vecera
2008-06-11 11:21:59 UTC
Link: Added: This issue depends JBMESSAGING-1368 I'd suggest adding a note about this to documentation because the solution is not so obvious. The definite problem solution is to delete the row from JBM_POSTOFFICE. Please could you have a look on this? Martin - is this a new problem in CP02? (In other words, is this a regression relative to CP01/GA?) Affects: Added: [Release Notes] Release note content under known issues "BMESSAGING-1368 - If you have deployed a clustered queue and then undeploy it, you cannot deploy a non-clustered queue with the same name. You must delete the destination from JBM_POSTOFFICE table first before redeploying" added to 4.3 release notes Cannot verify this fix with IR5 since the docs package is not correct and doesn't contain release notes (SOA-889). I suggest the following update to the rel. notes (marked with >>> <<<): You cannot deploy a non-clustered queue with the same name as a clustered queue that has been deployed >>>and<<< then undeployed >>>and vice versa<<<. You must delete the destination from JBM_POSTOFFICE table first before deploying. to clarify: if I deploy a clustered queue called X, undeploy it,and then deploy a new clustered queue called X there are no problems ? And like wise if the queue each time is not clustered? its only a problem if the clustering "mode" of the queue differs? Unfortately I can't use phrases like "vice versa" because they don't translate well. New content: Once a queue is undeployed you cannot deploy a new queue with the same name if one of the queues was a clustered queue and the other queue was not. You must delete the destination from the JBM_POSTOFFICE table before the new queue can be deployed successfully. content update applied This seems really great. Verified in GA |