[jboss-jira] [JBoss JIRA] Commented: (JGRP-248) Channel.down() hangs under some circumstances using multiplexer

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-248?page=comments#action_12340822 ] 
            
Bela Ban commented on JGRP-248:
-------------------------------

I assume this is jboss-head (JBoss 5) ? I didn't see any Multiplexer code in 4.0.x. I'll checkout head then...

> Channel.down() hangs under some circumstances using multiplexer
> ---------------------------------------------------------------
>
>                 Key: JGRP-248
>                 URL: http://jira.jboss.com/jira/browse/JGRP-248
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Jerry Gauthier
>         Assigned To: Bela Ban
>             Fix For: 2.4
>
>
> If I enable the ClusterPartition and TomcatClusterService mbeans for use with JGroups 2.3 multiplexer, the server startup process will hang when ClusterPartition invokes channel.down().  This is true even if the two services instantiate the multiplexer channel using createMultiplexerChannel(String, String) instead of the state transfer constructor.
> To replicate this problem, the following steps are required.
> 1)  Modify cluster-service.xml to enable ClusterPartition for multiplexer use (e.g., remove the comments from the Multiplexer attribute).
> 2)  Modify tc5-cluster.sar\META-INF\jboss-service.xml to enable TomcatClusteringCache for multiplexer use (e.g., remove the comments from the Multiplexer attributes).
> 3) JBossCache is currently inhibited from using the multiplexer in TreeCache.setMultiplexer().  The method's setter is commented out and a warning is issued if you attempt to use the multiplexer with JBossCache.  If this is still true when you attempt to replicate this issue, you'll need to modify TreeCache.setMultiplexer() to allow the multiplexer to be used.
> Note: I've only been able to replicate this issue when ClusterPartition and TomcatClusteringCache both have the multiplexer enabled.  Using other cache services with ClusterPartition doesn't seem to trigger the 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