[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1099) Old message ID sent back when failure reading magic byte

[ https://issues.jboss.org/browse/ISPN-1099?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1099: ---------------------------------------- Actually, this is really odd cos the server does encode the right error: [JBoss] 00:32:02,734 TRACE [HotRodEncoder$] Encode msg ErrorResponse{messageId=0, operation=ErrorResponse, status=InvalidMagicOrMsgId, msg=org.infinispan.server.hotrod.InvalidMagicIdException: Error reading magic byte or message id: 255} But the client ends up reading a message code 2421 ??? Coincidentaly, this message code belongs to a message that had an error due to SuspectException being thrown a few seconds later: [JBoss] 00:29:57,547 TRACE [HotRodEncoder$] Encode msg ErrorResponse{messageId=2421, operation=ErrorResponse, status=ServerError, msg=org.infinispan.CacheException: java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: Suspected member: perf20-31186} So I think something is not being left in the right state after this exception that then results on the client reading something completely different because then you see the server responding again for 2421! [JBoss] 00:32:02,733 TRACE [HotRodEncoder$] Encode msg Response{messageId=2421, operation=PutResponse, status=Success, cacheName=} I might ask Trustin to give me a hand with this but before if the root cause is the exception on put() operation, I might be able to replicate it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira