[infinispan-issues] [JBoss JIRA] (HRJS-5) Iterator.next might read another next calls entry

[Galder Zamarreño (JIRA)]

Galder Zamarreño created HRJS-5:
-----------------------------------

             Summary: Iterator.next might read another next calls entry
                 Key: HRJS-5
                 URL: https://issues.jboss.org/browse/HRJS-5
             Project: Infinispan Javascript client
          Issue Type: Bug
    Affects Versions: 0.2.0
            Reporter: Galder Zamarreño


Sometimes iterator fails with:

{code}
  2) Infinispan local client can iterate over entries
   Message:
     timeout: timed out after 5000 msec waiting for spec to complete
   Stacktrace:
     undefined
{code}

When you look at the trace logs, you see:

{code}
[2016-04-25 12:20:12.127] [TRACE] client - Invoke iterator.next(msgId=326,iteratorId=6bfd9ab1-d42f-4209-9393-90c13a648381) on 127.0.0.1:11222
[2016-04-25 12:20:12.127] [TRACE] encoder - Encode operation with topology id 0
[2016-04-25 12:20:12.127] [TRACE] transport - Write buffer(msgId=326) to 127.0.0.1:11222
[2016-04-25 12:20:12.127] [TRACE] client - Invoke iterator.next(msgId=327,iteratorId=6bfd9ab1-d42f-4209-9393-90c13a648381) on 127.0.0.1:11222
[2016-04-25 12:20:12.127] [TRACE] encoder - Encode operation with topology id 0
[2016-04-25 12:20:12.128] [TRACE] transport - Write buffer(msgId=327) to 127.0.0.1:11222
[2016-04-25 12:20:12.128] [TRACE] client - Invoke iterator.next(msgId=328,iteratorId=6bfd9ab1-d42f-4209-9393-90c13a648381) on 127.0.0.1:11222
[2016-04-25 12:20:12.128] [TRACE] encoder - Encode operation with topology id 0
[2016-04-25 12:20:12.128] [TRACE] transport - Write buffer(msgId=328) to 127.0.0.1:11222
[2016-04-25 12:20:12.137] [TRACE] decoder - Read header(msgId=326): opCode=52, status=0, hasNewTopology=0
[2016-04-25 12:20:12.137] [TRACE] decoder - Call decode for request(msgId=326)
[2016-04-25 12:20:12.137] [TRACE] iterator - Iterator next contains 1 entries
[2016-04-25 12:20:12.137] [TRACE] connection - After decoding request(msgId=326), buffer size is 23, and offset 23
[2016-04-25 12:20:12.137] [TRACE] connection - Complete success for request(msgId=326) with [{"key":"local-it2","value":"v2"}]
[2016-04-25 12:20:12.138] [TRACE] decoder - Read header(msgId=328): opCode=52, status=0, hasNewTopology=0
[2016-04-25 12:20:12.138] [TRACE] decoder - Call decode for request(msgId=328)
[2016-04-25 12:20:12.138] [TRACE] iterator - Iterator next contains 1 entries
[2016-04-25 12:20:12.138] [TRACE] connection - After decoding request(msgId=328), buffer size is 46, and offset 23
[2016-04-25 12:20:12.138] [TRACE] decoder - Read header(msgId=328): opCode=52, status=0, hasNewTopology=0
[2016-04-25 12:20:12.138] [TRACE] decoder - Call decode for request(msgId=328)
[2016-04-25 12:20:12.138] [TRACE] iterator - Iterator next contains 1 entries
[2016-04-25 12:20:12.138] [TRACE] connection - After decoding request(msgId=328), buffer size is 23, and offset 23
[2016-04-25 12:20:12.139] [TRACE] connection - Complete success for request(msgId=328) with [{"key":"local-it1","value":"v1"}]
[2016-04-25 12:20:12.139] [TRACE] connection - Complete success for request(msgId=328) with [{"key":"local-it3","value":"v3"}]
[2016-04-25 12:20:17.963] [DEBUG] client - Invoke clear(msgId=329)
{code}

Two client side decode requests happened for msgId=328 whereas msgId=327 was left without answer.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)