[infinispan-issues] [JBoss JIRA] (ISPN-1588) IndexOutOfBoundsException while using clustered query

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-1588:
--------------------------------

    Fix Version/s: 5.2.0.FINAL

    
> IndexOutOfBoundsException while using clustered query
> -----------------------------------------------------
>
>                 Key: ISPN-1588
>                 URL: https://issues.jboss.org/browse/ISPN-1588
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Querying, RPC
>    Affects Versions: 5.1.0.BETA5
>            Reporter: Mathieu Lachance
>            Assignee: Sanne Grinovero
>             Fix For: 5.2.0.FINAL
>
>
> when using clustered query with dist sync mode i'm running into index out of bound exception.
> java.lang.IndexOutOfBoundsException: Index: 100, Size: 100
> 	at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> 	at java.util.ArrayList.get(ArrayList.java:322)
> 	at org.infinispan.query.clustered.DistributedIterator.current(DistributedIterator.java:138)
> 	at org.infinispan.query.clustered.DistributedIterator.next(DistributedIterator.java:114)
> 	at org.infinispan.query.clustered.ClusteredCacheQueryImpl.list(ClusteredCacheQueryImpl.java:136)
> 	at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:239)
> 	at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:200)
> 	at com.XXX.ClientCache.getClientsByServerId(ClientCache.java:168)
> 	at com.XXX.getClientsByServerId(ClientManager.java:157)
> 	at com.XXX$PingClient.run(PlayerBll.java:890)
> 	at java.util.TimerThread.mainLoop(Timer.java:512)
> 	at java.util.TimerThread.run(Timer.java:462)
> i do not have any reproductible step, but here's what i know :
> it only seems to happen under high contention ; when i'm running stress test.
> when running a stress test i might get query that return over than 100 results.
> tough i've also seen it happen on query that can only return few (4-6) results.
> i never saw the stack trace with different index and size different than 100 (it's always the exact same exception).
> i've also tried the lazy iterator to see if it would have a different behavior, but i get the same stack trace.
> is there anything i could look up in the source code to debug and maybe find the repro steps ?
> thanks,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira