[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1099) Old message ID sent back when a server error is encountered

[ https://issues.jboss.org/browse/ISPN-1099?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1099: ----------------------------------- Summary: Old message ID sent back when a server error is encountered (was: Old message ID sent back when failure reading magic byte) Description: If the server fails with a server error (i.e. a suspicion), the decoder is not cleared correctly and so next requests end up with previous message ids: 2011/04/29 00:32:02:733 EDT [WARN ][Runner - 0] HOST perf01.mw.lab.eng.bos.redhat.com:rootProcess:E - Error sampling data: <org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid message id. Expected 2476 and received 2421> was: If the server fails to read anything before the message id, for example when reading the magic byte: [JBoss] 00:32:02,733 TRACE [HotRodEncoder$] Encode msg Response{messageId=2421, operation=PutResponse, status=Success, cacheName=} ... [JBoss] org.infinispan.server.hotrod.HotRodException: org.infinispan.server.hotrod.InvalidMagicIdException: Error reading magic byte or message id: 255 The error response sent back will contain the previous message ID and the client won't like it: 2011/04/29 00:32:02:733 EDT [WARN ][Runner - 0] HOST perf01.mw.lab.eng.bos.redhat.com:rootProcess:E - Error sampling data: <org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid message id. Expected 2476 and received 2421> I don't know however the root of the InvalidMagicIdException but in such situation where the server did not get to read the message id, it will return 0 as message id and the client needs to be able to deal w/ it accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira