Unqiue node id not properly set on multiplexed channel ------------------------------------------------------ Key: JBAS-3968 URL: http://jira.jboss.com/jira/browse/JBAS-3968 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta2 The JBoss-specific subclass of JChannelFactory was not overriding all the overloaded variants of createMultiplexerChannel, including the one called by JBoss Cache. As a result the unique node id was not being set as additional_data on the underlying channel until after the channel was connected, which means other nodes in the cluster were unaware of the unique id. A major side effect of this is that DistributedReplicantManager.lookupReplicants would only return replicants for the coordinator node. Thus smart proxies for clustered services will only be able to communicate with the coordinator node. DRMTestCase has been updated to detect this sort of problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira