[ https://forge.continuent.org/jira/browse/HEDERA-34?page=all ]
     
Robert Hodges resolved HEDERA-34:
---------------------------------

    Resolution: Fixed

This problem is solved by switching to the JGroups 2.4.x stack defined by the 
total.xml configuration file.  This uses a different total order algorithm 
based on a sequencer.  Speed seems to be about equal to Appia and the test 
passes. 

> Hedera performance test does not complete when sending more than a few 
> messages with JGroups 2.4.1
> --------------------------------------------------------------------------------------------------
>
>          Key: HEDERA-34
>          URL: https://forge.continuent.org/jira/browse/HEDERA-34
>      Project: Hedera
>         Type: Bug

>  Environment: MacOS 10.4, behavior also replicated on Linux / CentOS 4.5
> The JGroups library version is JGroups 2.4.1-SP4
>     Reporter: Robert Hodges
>     Assignee: Robert Hodges
>     Priority: Critical
>      Fix For: Hedera 1.6.3

>
>
> The Hedera ChannelPerformanceTest does not complete if you run it using 
> JGroups 2.4.1.   Older versions such as 2.2.9 appear to work better.   
> The problem seems to be that while messages are sent normally over the 
> channel, not all messages are received.  The test then hangs waiting for the 
> missing messages to arrive.   To set up this this test, edit run-test.sh to 
> use JGroups, replacing the CONFIG line as follows.   This specifies 2 
> senders, 2 receivers, and 1000 messages of 1024 bytes each.  
> CONFIG="1 2 2 1000 1024 /hedera_jgroups.properties"
> Run the test by starting run-test.sh in two windows, which should result in 
> output similar to the following in each window: 
> hartzpass:~/workspace_os/hedera rhodges$ ./run-test.sh 
> 2008-01-13 11:32:09,501 INFO  continuent.hedera.channel Using group 
> communication factory: 
> org.continuent.hedera.factory.JGroupsGroupCommunicationFactory
> -------------------------------------------------------
> GMS: address is 192.168.57.1:54668
> -------------------------------------------------------
> 2008-01-13 11:32:11,892 INFO  continuent.hedera.channel TestGroup_0: Channel 
> local membership: Member(address=/192.168.57.1:54668, uid=TestGroup_0)
> 2008-01-13 11:32:11,892 INFO  continuent.hedera.channel TestGroup_0: Waiting 
> for all members to join...
> 2008-01-13 11:32:11,924 INFO  continuent.hedera.channel TestGroup_0: All 
> members joined, sending messages!
> 2008-01-13 11:32:11,925 INFO  continuent.hedera.channel TestGroup_0: Starting 
> sending 1000 messages of 1024 bytes to 2 members.
> 2008-01-13 11:32:11,925 INFO  continuent.hedera.channel TestGroup_0: Members 
> are: Member(address=/192.168.57.1:54665, uid=TestGroup_0) 
> Member(address=/192.168.57.1:54668, uid=TestGroup_0) .
> 2008-01-13 11:32:12,390 INFO  continuent.hedera.channel TestGroup_0: Sent 
> all, average time per message: 0.465ms
> Edit config/log4j.properties to turn logging on the channel performance test 
> to DEBUG and you will see that while all messages are send only a few are 
> actually received.    In my test runs it seems that about 140 or so messages 
> are received.  
> If you run using Appia, which is the default for run-test.sh, the test 
> completes without any problems.    You can also make the test complete by 
> setting the number of messages to a very small value, such as 10.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
Hedera mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/hedera

Reply via email to