Multiplexer: additional_data is dropped in MuxChannel ----------------------------------------------------- Key: JGRP-265 URL: http://jira.jboss.com/jira/browse/JGRP-265 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1, 2.3 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 HAPartition makes use of the "additional_data" feature to ensure the unique identity of each member of the partition. This breaks with the MUX if the Channel is connected before HAPartition gets a chance to set the additional_data. This could be a general problem with additional_data -- one service using a shared channel wants to make use of additional_data, but the channel is already connected, so all the IpAddress objects in the views around the cluster won't have the additional_data. This *may* not be a big deal, as logical addresses (JGRP-129) remove some of the need for additional data. If people use additional_data for some other reason than logical addresses, then it may be an issue. For the HAPartition use case, I created a temporary workaround by creating an org.jboss.ha subclass of JChannelFactory, and having the subclass ensure the additional_data is set before handing out a channel. This ensures that no matter what service starts the underlying channel, the additional_data HAPartition wants will be there. This will suffice until JGRP-129 is done, after which HAPartition won't need additional_data. -- 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