[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.

[Howard Gao (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard Gao closed JBMESSAGING-1742.
-----------------------------------

    Resolution: Done


Documentation added:

6.6.2.1.18.
6.6.3.1.20.



> Allow the clustered status of a destination to be updated without the need for manually intervention.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1742
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
>            Reporter: Colin Mondesir
>            Assignee: Howard Gao
>            Priority: Minor
>             Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
>
>
> At the moment when a destination is deployed as non clustered, then redeployed as clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
> In order to change the clustered status of a destination you need to delete the original destination from storage first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira