yaxing/ads_con_ctrl — Issue #6: Weird result when all are failed and reading a duplicate variable
Author: sarnzzle
Created: 2011-12-05 19:47:26+00:00
State: open

Check out the following results:

fail(1); fail(2); fail(3); fail(4); fail(5); fail(6); fail(7); fail(8); fail(9); fail(10)
**DEBUG** Site={1} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={2} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={3} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={4} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={5} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={6} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={7} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={8} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={9} Command="FAIL"
**DEBUG** Result="null"
**DEBUG** Site={10} Command="FAIL"
**DEBUG** Result="null"
begin(t1)
recover(1)
**DEBUG** Site={1} Command="RECOVER"
**DEBUG** Result="null"
r(t1, x2)
Could not read, there is a recover lock: r(t1, x2) // this is correct, because there is only a recover lock
All sites have recover lock for resource: X2
Buffering command: r(t1, x2)
**DEBUG** Site={1} Command="INSTR 1 1323114240573 R X2"
**DEBUG** Result="EXE_RESP 0"
recover(2) // now I recover one more site
**DEBUG** Site={2} Command="RECOVER"
**DEBUG** Result="null"
**DEBUG** Site={1} Command="INSTR 1 1323114240573 R X2"
**DEBUG** Result="EXE_RESP 0"
**DEBUG** Site={2} Command="INSTR 1 1323114240573 R X2"
**DEBUG** Result="EXE_RESP X2:20" // here is the response I don't understand. site two should have a reocver lock on X2, but instead it just let T1 read it
EXE_RESP X2:20
Could not read, there is a recover lock: r(t1, x2)