Claudiu, I don't know if that helps but I read in the changes of jboss 3.2.6RC1 changes the following (from http://sourceforge.net/docman/display_doc.php?docid=23847&group_id=22866): anonymous wrote : * A fix for the following clustering scenario has been added. There are a number of nodes in a partition. One node is selected as master, and runs the singleton service. The master replica is shunned. The other nodes remove its keys from the DRM. Another master replica is selected. It runs the singleton service. The shunned node returns. Two bad things happen: | 1. It doesn't check if it should still run the singleton, and assumes it is still the master (not true, he is now the last node in the DRM, not the first). From now on, two nodes are running the singleton. | 2. The other nodes don't update the shunned node's keys. From this point on, as far as the other nodes are concerned, that node can never be a master replica for that singleton service. |
Could this be also the cause of the abnormal behavior you are facing? BTW, I'm not a jboss developer neither an expert user. Just a dummy user, trying to help. regards, Pedro Salazar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845837#3845837 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845837 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
