[jboss-jira] [JBoss JIRA] Commented: (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:comment-tabpanel&focusedCommentId=12490519#action_12490519 ] 

Howard Gao commented on JBMESSAGING-1742:
-----------------------------------------

I'm assuming the following usage:

1. non-cluster destination --> clustered destination:

User changes the clustered attribute to 'true' and then may add as many as possible new destinations to other nodes. Existing messages can be safely removed from DB or remain without any change.

2. clustered destination ---> non clustered destination:

User keeps only one of the destination's config file and manually delete all other configuration files of the clustered destination. Then he modified the destination's clustered attribute to be 'false'. Then redeploy it.

Note: 

In both cases, it is required that the user shut down all nodes before making any of the changes.







 

> 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.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