[ https://issues.jboss.org/browse/JGRP-1613?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1613: -------------------------------- A combination of fork-stack id and fork-channel id might do the job. E.g. with fork-stack id=2, a fork-channel picks id=17. All messages sent by that channel carry fork-stack-id=2, fork-channel-id=17. The receiver picks fork-stack 2 first, the message passes up that stack, then we pick fork-channel with id=17 and dispatch the message to it. For messages that originate from below a fork-channel, e.g. from COUNTER, the fork-channel-id is null. This also works for dynamically created fork-channels: the create() call of the fork-channel carries both ids as well. If the fork-stack doesn't exist, it is created. The rest (creation and registration of the fork-channel) is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira