[jboss-jira] [JBoss JIRA] (JGRP-1887) Remove the synchronization on JChannel.class in JChannel.init

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008731#comment-13008731 ] 

Bela Ban edited comment on JGRP-1887 at 10/6/14 6:04 AM:
---------------------------------------------------------

Cause: https://issues.jboss.org/browse/JGRP-964, related to shared transport. When multiple channels are started in parallel, the first channel creates the shared transport. However, subsequent channels might fail accessing the shared transport's fields (such as the timer), as the shared transport hasn't yet been fully created (e.g. the timer hasn't yet been instantiated).


was (Author: belaban):
Cause: https://issues.jboss.org/browse/JGRP-964. Need to investigate whether this is still needed.

> Remove the synchronization on JChannel.class in JChannel.init
> -------------------------------------------------------------
>
>                 Key: JGRP-1887
>                 URL: https://issues.jboss.org/browse/JGRP-1887
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 3.5.1
>            Reporter: Dan Berindei
>            Assignee: Bela Ban
>             Fix For: 3.5.2, 3.6
>
>
> {{JChannel.init(ProtocolCtackConfigurator)}} has a {{synchronized(Channel.class)}} block that doesn't seem necessary, as JChannel instances do not normally share resources.
> This can cause serious delays in the Infinispan test suite, because we run many tests in parallel, each creating its own cluster. In some tests we also have a timeout for the test to create the JChannel (among other things), and these delays can lead to random failures (e.g. ISPN-4802).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)