"aslak" wrote : This issue came up during something that might have been a missconfiguration. | I was trying to setup a two node cluster where the destinations were only deployed on one node(not using farm), | figuring that they would be transferred over to the second node. | InMemoryBindings are added to the second node, but the SecurityMetaData is missing. | After adding some code to transferred the SecurityMetaData, I found that they are never bound to the DestinationManager, | so they are never found by any deployed mdbs on the second node. | Any clustered destinations need to be deployed on all nodes anonymous wrote : | I tried a different setup deploying the same destinations on both nodes, that's when I saw this problem: | http://www.jboss.org/index.html?module=bb&op=viewtopic&t=118320 | | When removing the security, it failes on the temporary destination not being bound. | The scenario is: | Using the ClusteredConnectionFactory, create a temporary destination on node1. | Kill node1, the failover to node2 failes because there is no Temporary Destination | with name X bound in node2s DestinationManager. | | The next potential issue is somehow the connection to the second node has to get the connection id of the first connection, or register itself as the owner of the temporary destination to be able to keep up the tempdestination.createdConnectionId == connection.id security constraint. | I havn't looked into this yet, it might work already. | | -aslak- I'm having a bit of a problem understanding your explanation - could you possibly rephrase it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085204#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...