[infinispan-issues] [JBoss JIRA] (ISPN-6924) HotRod addressCache iterator shouldn't go remote

[Dan Berindei (Jira)]

    [ https://issues.jboss.org/browse/ISPN-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662501#comment-13662501 ] 

Dan Berindei commented on ISPN-6924:
------------------------------------

[~william.burns] you mentioned that this stacktrace can also appear when the iterator doesn't go remotely, and that it's fixed in the latest distributed streams code:

{noformat}
"HotRod-hotrod-externalServerWorker-5-24" #464 prio=5 os_prio=0 tid=0x00007f5e6002f000 nid=0xe9f waiting on condition [0x00007f5d28a60000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <merged>(a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2163)
	at org.infinispan.stream.impl.DistributedCacheStream$IteratorSupplier.get(DistributedCacheStream.java:918)
	at org.infinispan.util.CloseableSuppliedIterator.getNext(CloseableSuppliedIterator.java:27)
	at org.infinispan.util.CloseableSuppliedIterator.hasNext(CloseableSuppliedIterator.java:33)
	at org.infinispan.stream.impl.RemovableIterator.getNextFromIterator(RemovableIterator.java:34)
	at org.infinispan.stream.impl.RemovableIterator.hasNext(RemovableIterator.java:43)
	at org.infinispan.commons.util.Closeables$IteratorAsCloseableIterator.hasNext(Closeables.java:86)
	at org.infinispan.stream.impl.RemovableIterator.getNextFromIterator(RemovableIterator.java:34)
	at org.infinispan.stream.impl.RemovableIterator.hasNext(RemovableIterator.java:43)
	at org.infinispan.commons.util.IteratorMapper.hasNext(IteratorMapper.java:26)
	at java.util.concurrent.ConcurrentMap.forEach(ConcurrentMap.java:104)
	at org.infinispan.server.hotrod.Encoder2x.generateTopologyResponse(Encoder2x.java:207)
	at org.infinispan.server.hotrod.Encoder2x.getTopologyResponse(Encoder2x.java:184)
	at org.infinispan.server.hotrod.Encoder2x.writeHeader(Encoder2x.java:57)
	at org.infinispan.server.hotrod.HotRodEncoder.encode(HotRodEncoder.java:56)
{noformat}

If that's true, could you mark this as fixed and update the versions?

> HotRod addressCache iterator shouldn't go remote
> ------------------------------------------------
>
>                 Key: ISPN-6924
>                 URL: https://issues.jboss.org/browse/ISPN-6924
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Clustered Executor, Server
>            Reporter: William Burns
>            Priority: Major
>
> In the forum post, the stack traces show the topology update being sent back from the server to the client.  However it is using a distributed iterator.  This shouldn't happen as the addressCache is a REPL cache which should own all segments and thus the iterator shouldn't go remote at all and just operate on the user thread solely.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)