[infinispan-issues] [JBoss JIRA] (ISPN-2550) NoSuchElementException in Hot Rod Encoder

[Michal Linhard (JIRA)]

Michal Linhard created ISPN-2550:
------------------------------------

             Summary: NoSuchElementException in Hot Rod Encoder
                 Key: ISPN-2550
                 URL: https://issues.jboss.org/browse/ISPN-2550
             Project: Infinispan
          Issue Type: Bug
          Components: Cache Server
    Affects Versions: 5.2.0.Beta4
            Reporter: Michal Linhard
            Assignee: Galder Zamarreño


Tomas noticed this a while ago in a specific functional test:
https://bugzilla.redhat.com/show_bug.cgi?id=875151

I'm creating a more general JIRA, cause I'm having this in resilience test.

What I found by quick debug, is that here:

https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/main/scala/org/infinispan/server/hotrod/Encoders.scala#L106

{code}
               for (segmentIdx <- 0 until numSegments) {
                  val denormalizedSegmentHashIds = allDenormalizedHashIds(segmentIdx)
                  val segmentOwners = ch.locateOwnersForSegment(segmentIdx)
                  for (ownerIdx <- 0 until segmentOwners.length) {
                     val address = segmentOwners(ownerIdx % segmentOwners.size)
                     val serverAddress = members(address)
                     val hashId = denormalizedSegmentHashIds(ownerIdx)
                     log.tracef("Writing hash id %d for %s:%s", hashId, serverAddress.host, serverAddress.port)
                     writeString(serverAddress.host, buf)
                     writeUnsignedShort(serverAddress.port, buf)
                     buf.writeInt(hashId)
                  }
               }
{code}

we're trying to obtain serverAddress for nonexistent address and NoSuchElementException is not handled properly.
It hapens after I kill a node in a resilience test and the exception appears when querying for the node in the members cache.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira