"clebert.suconic(a)jboss.com" wrote : ConnectionFactoryJNDIMapper::onReplicationChange is calling updating ServerCFEndpoing::updateClusteredClients... | | onReplicateChange is also setting the new LoadBalancing when the data is being changed. | | ClusterViewUpdateTest::testUpdateConnectionFactory is testing updates on CFs... it kills the server and verifies if the connectinFactory was changed. | | Test was passing for me on Friday. | I don't see how this could be the case. Think about it, if a server crashes then the connection factories will not get undeployed. If you are only updating the view when connection factory is deployed / undeployed then how can the client update be happening? What am I missing? anonymous wrote : | | I didn't want MessageCallbackHandler to also take care of ConnectionFactories... I thought the dependency would be wrong. | | This is fine, but has nothing to do with the point I am making. I am just saying that creating a new interface is redundant since you are not calling the methods polymorphically. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004614#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...