tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 45222] New: concurrent startup of ReplicatedMap leads to inconsistent state.
Date Tue, 17 Jun 2008 20:16:47 GMT

           Summary: concurrent startup of ReplicatedMap leads to
                    inconsistent state.
           Product: Tomcat 6
           Version: 6.0.16
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Cluster

Starting four machines with a ReplicatedMap where each machine immediately puts
entries into the map frequently leads to inconsistent state. Specifically, some
nodes are missing some entries. Most are present and correct. Given the
internal work done around state transfer and the general intent of the class,
I'm assuming this is a serious bug.

I've seen this with straight;

c = new GroupChannel();
m = new ReplicatedMap(null, c, 5000, null);
m.put(key, value);

My actual rig uses TcpFailureDetector and NonBlockingCoordinator as I need
jgroups-like views (without the buggy jgroups stack!).

I can cook my own Map implementation that deals with this by periodically
resending locally owned key-value pairs, but I figured I should post the bug.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message