[infinispan-issues] [JBoss JIRA] Created: (ISPN-1099) Old message ID sent back when failure reading magic byte
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Thu May 12 08:21:31 EDT 2011
Old message ID sent back when failure reading magic byte
--------------------------------------------------------
Key: ISPN-1099
URL: https://issues.jboss.org/browse/ISPN-1099
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.0.0.CR1, 4.2.1.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.2.BETA1, 4.2.2.FINAL, 5.0.0.CR2, 5.0.0.FINAL
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
More information about the infinispan-issues
mailing list