[jboss-jira] [JBoss JIRA] Updated: (JGRP-788) concurrent startup of multiple channels with shared transport is very slow, occasionally wedges.

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-788?page=all ]

Bela Ban updated JGRP-788:
--------------------------

    Fix Version/s: 2.6.3
      Description: 
Further to the testing in ChannelConcurrencyTest, we are now verifying 2.6.3-CR2 with the new shared transport enabled.

It appears to be a lot slower than the equivalent number of channels without shared transport, the CCT timeout of 2 minutes often being insufficient.

Will attach config and test cases.

I've not been able to catch it actually wedged yet, but will post as soon as I get a confirmed sighting.

  was:

Further to the testing in ChannelConcurrencyTest, we are now verifying 2.6.3-CR2 with the new shared transport enabled.

It appears to be a lot slower than the equivalent number of channels without shared transport, the CCT timeout of 2 minutes often being insufficient.

Will attach config and test cases.

I've not been able to catch it actually wedged yet, but will post as soon as I get a confirmed sighting.

         Assignee: Vladimir Blagojevic  (was: Bela Ban)

> concurrent startup of multiple channels with shared transport is very slow, occasionally wedges.
> ------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-788
>                 URL: http://jira.jboss.com/jira/browse/JGRP-788
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6.3
>         Environment: Debian Etch / Java 6.
>            Reporter: Robert Newson
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6.3
>
>         Attachments: shared-transport.xml, SharedTransportConcurrencyTest.java
>
>
> Further to the testing in ChannelConcurrencyTest, we are now verifying 2.6.3-CR2 with the new shared transport enabled.
> It appears to be a lot slower than the equivalent number of channels without shared transport, the CCT timeout of 2 minutes often being insufficient.
> Will attach config and test cases.
> I've not been able to catch it actually wedged yet, but will post as soon as I get a confirmed sighting.

-- 
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