[
http://jira.jboss.com/jira/browse/JGRP-227?page=comments#action_12340953 ]
Mark Kopec commented on JGRP-227:
---------------------------------
In order to be very clear:
- What is currently attached to this issue as of August 9th 2006 has a junit test
JGroupsDistTest.java
if you run this test only one time. It will fail, each subsequent time you run it also.
- Included in the Junit test is the workaround, which is located on line 264, using this
method you can acheive the same desired functionality that caused a cluster wide lockup.
Bela, if you get the chance, please update your website that points to the distributed
hashtable api, and make it "undepricated" so that people accessing wikipedias
"distributed hashtable" section can use your product more.
http://en.wikipedia.org/wiki/Distributed_hash_tables references:
http://www.jgroups.org/javagroupsnew/docs/javadoc/org/jgroups/blocks/Dist...
I had to fight with some dudes to keep it there, he kept insisting that jgroups is more of
a framework, but so is Bamboo (the first entry there). May I say the model is suprisingly
similar to Jgroups, imitation is probably the sincerest form of flattery.
To make a long story short; it's now a well established member of the wikipedia dht
entry community :)
Distributed Hashtable call to put() blocks indefinitely
-------------------------------------------------------
Key: JGRP-227
URL:
http://jira.jboss.com/jira/browse/JGRP-227
Project: JGroups
Issue Type: Bug
Affects Versions: 2.2.9.1
Environment: Mandrake Linux 9.1, Java 1.4.2
Reporter: Mark Kopec
Assigned To: Bela Ban
Fix For: 2.4
Attachments: JGroupsDistTest.java
Distributed hashtable put(x,y) without any ERROR level locks up and creates inconsistent
DHT values across cluster.
Here is the code that exposes this error:
MyListener implements DistributedHashtable.notification{
// other methods
public void entryRemoved(Object key) {
distributedHashTableObject.put(key,"xxxsomeval"); //<-- this and
subsequent on the distributedHashTableObject put() or remove() get stuck!!!!
}
--
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