[infinispan-issues] [JBoss JIRA] (ISPN-1948) Invalid magic number

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696452#comment-12696452 ] 

Galder Zamarreño commented on ISPN-1948:
----------------------------------------

@Manik, I'm pretty sure that's not the case here because it uses the same Transport instance throughout sending the request and reading from it, and all socket instance variables in Transport are final, and we're logging what transport is reading each time. See my updated summary.
                
> Invalid magic number
> --------------------
>
>                 Key: ISPN-1948
>                 URL: https://issues.jboss.org/browse/ISPN-1948
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.1.3.FINAL
>            Reporter: Michal Linhard
>            Assignee: Galder Zamarreño
>             Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
>
>         Attachments: summary
>
>
> 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/job/edg-60-elasticity-dist-basic/47/console-edg-perf05/consoleText
> {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