[
http://jira.jboss.com/jira/browse/JGRP-624?page=all ]
Michael Newcomb closed JGRP-624.
--------------------------------
Resolution: Rejected
I had 3 different types of clients.
The first 2 actually used the state transfer and implemented the get/set state properly.
My 3rd client does not need state so it did not implement the get/set state but it still
called the connect-with-state-transfer method!
So this is a non-issue. Once I fixed that they connected just fine.
However, in another one of my applications I have only one type of member and they all use
connect-with-state-transfer. When I start them concurrently, I'm seeing the multiple
unblock issue again. I'm closing this bug and opening another to deal with that
issue.
connect-with-state-transfer not working when multiple clients
simultaneously try to connect-with-state-transfer
---------------------------------------------------------------------------------------------------------------
Key: JGRP-624
URL:
http://jira.jboss.com/jira/browse/JGRP-624
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6
Reporter: Michael Newcomb
Assigned To: Vladimir Blagojevic
Fix For: 2.6.1, 2.7
1. have 2 members of a group connected
2. simultaneously launch 3 new members that connect with a state transfer request
3. each of the 3 new members eventually time out awaiting state transfer
I was watching the log on the initially connected members (1 coordinator and 1 member)
and I watched as each of the new members slowly joined (about 10s between each new view).
However, on the coordinator log, I saw some GMS 'flush failure' messages.
I will be re-running with all the logs on and will report back.
--
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