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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on ISPN-1948:
-----------------------------------------------

Misha H. Ali <mhusnain at redhat.com> made a comment on [bug 807741|https://bugzilla.redhat.com/show_bug.cgi?id=807741]


    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1,4 @@
-The issue is a race condition on the Hot Rod server, which can lead to sending topologies erroneously as a result of addition of a new node to the cluster. When the issue appears, clients will start seeing "Invalid magic number" error messages as a result of the stream containing unexpected data.
+The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears, clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream.
 </para>
-When the issue appears, the safest thing to do is to restart the client, but the client might recover itself once all the unexpected data has been consumed. If the client recovers, the view topology it has will be lacking one of the added nodes, so although it would work relatively Ok, it would lead to some uneven request distribution.+<para>
+When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions, the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution.
                
> 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.1.x, 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