[infinispan-issues] [JBoss JIRA] (ISPN-1948) Invalid magic number
[
https://issues.jboss.org/browse/ISPN-1948?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1948:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
807741|https://bugzilla.redhat.com/show_bug.cgi?id=807741]
Galder Zamarreño <galder.zamarreno(a)redhat.com> made a comment on jira ISPN-1948
First of all, thx Michal for getting trace logs for this. I must say that this is quite an
odd one. I've posted the relevant bits of the logs to https://gist.github.com/2290090.
Basically, the client sends the request, server handles it correctly and encodes a
response without any issues, yet the client gets messed up. My gut feeling is that
there's either a mix up in sockets/buffers/channels on the server, or in the client of
some sort. I'm gonna add some extra logging information to both the client and the
server to find out more about these situations. With this info as well, we should be able
to get more targeted logging for next round of testing.
Invalid magic number
--------------------
Key: ISPN-1948
URL: https://issues.jboss.org/browse/ISPN-1948
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.1.3.CR1
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.1.4.CR1, 5.1.4.FINAL
Here we have the good old "invalid magic number" problem again (JDG 6.0.0.ER5
testing):
https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/...
{code}
2012-03-26 15:18:43,524 253444 ERROR [org.jboss.smartfrog.edg.loaddriver.DriverNode]
(Client-477:) Error doing PUT(key410977) to node node02 (lastOpTime 1 ms)
org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number.
Expected 0xa1 and received 0x0
at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:92)
at
org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:78)
at
org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:72)
at
org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:52)
at
org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:41)
at
org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:68)
at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:219)
at org.infinispan.CacheSupport.put(CacheSupport.java:52)
at
org.jboss.qa.edg.adapter.HotRodAdapter$HotRodRemoteCacheAdapter.put(HotRodAdapter.java:249)
at
org.jboss.qa.edg.adapter.HotRodAdapter$HotRodRemoteCacheAdapter.put(HotRodAdapter.java:234)
at
org.jboss.smartfrog.edg.loaddriver.DriverNodeImpl$ClientThread.makeRequest(DriverNodeImpl.java:244)
at
org.jboss.smartfrog.edg.loaddriver.DriverNodeImpl$ClientThread.run(DriverNodeImpl.java:375)
{code}
The exception repeats many times in the log and the "received" part of
"Expected 0xa1 and received 0xXX" takes on different values.
Also happens in both PUT and GET operations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira