[infinispan-issues] [JBoss JIRA] Commented: (ISPN-826) RemoteLockCleanupStressTest throws EOFException when reading state

[Galder Zamarreño (JIRA)]

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

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

p.s. If anyone thinks this should be handled in a different way, speak up! If we can't generate the transaction log, that means that the node is already trying to server to someone else, so the failure on the sender, and hence on the receiver is correct in my view.

> RemoteLockCleanupStressTest throws EOFException when reading state
> ------------------------------------------------------------------
>
>                 Key: ISPN-826
>                 URL: https://jira.jboss.org/browse/ISPN-826
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Marshalling, State transfer
>    Affects Versions: 4.1.0.Final, 4.2.0.CR3
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>            Priority: Blocker
>             Fix For: 4.2.0.CR4, 4.2.0.Final
>
>         Attachments: eof-ispn826-infinispan.log.zip
>
>
> While doing some work to verify ISPN-244, I've spotted that RemoteLockCleanupStressTest throws. Note that this is not related to the ISPN-244 cos the issue is present in 4.2.x as well where ISPN-244 has no bearing: 
> 2010-12-08 18:16:25,945 13951 ERROR [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,Infinispan-Cluster,NodeC-2057:) Caught while requesting or applying state 
> org.infinispan.statetransfer.StateTransferException: java.io.EOFException: Read past end of file 
> at org.infinispan.statetransfer.StateTransferManagerImpl.applyState(StateTransferManagerImpl.java:331) 
> at org.infinispan.remoting.InboundInvocationHandlerImpl.applyState(InboundInvocationHandlerImpl.java:102) 
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.setState(JGroupsTransport.java:598) 
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:712) 
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:772) 
> at org.jgroups.JChannel.up(JChannel.java:1422) 
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:954) 
> at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:478) 
> at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.connectToStateProvider(STREAMING_STATE_TRANSFER.java:525) 
> at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.handleStateRsp(STREAMING_STATE_TRANSFER.java:464) 
> at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:225) 
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:190) 
> at org.jgroups.protocols.FC.up(FC.java:483) 
> at org.jgroups.protocols.pbcast.GMS.up(GMS.java:888) 
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) 
> at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:615) 
> at org.jgroups.protocols.UNICAST.up(UNICAST.java:295) 
> at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:707) 
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:132) 
> at org.jgroups.protocols.FD.up(FD.java:266) 
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:269) 
> at org.jgroups.protocols.MERGE2.up(MERGE2.java:210) 
> at org.jgroups.protocols.Discovery.up(Discovery.java:292) 
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1093) 
> at org.jgroups.protocols.TP.access$100(TP.java:56) 
> at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1633) 
> at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1615) 
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
> at java.lang.Thread.run(Thread.java:680) 
> Caused by: java.io.EOFException: Read past end of file 
> at org.jboss.marshalling.AbstractUnmarshaller.eofOnRead(AbstractUnmarshaller.java:184) 
> at org.jboss.marshalling.AbstractUnmarshaller.readUnsignedByteDirect(AbstractUnmarshaller.java:319) 
> at org.jboss.marshalling.AbstractUnmarshaller.readUnsignedByte(AbstractUnmarshaller.java:280) 
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:207) 
> at org.jboss.marshalling.AbstractUnmarshaller.readObject(AbstractUnmarshaller.java:85) 
> at org.infinispan.marshall.jboss.GenericJBossMarshaller.objectFromObjectStream(GenericJBossMarshaller.java:162) 
> at org.infinispan.marshall.VersionAwareMarshaller.objectFromObjectStream(VersionAwareMarshaller.java:184) 
> at org.infinispan.statetransfer.StateTransferManagerImpl.processCommitLog(StateTransferManagerImpl.java:228) 
> at org.infinispan.statetransfer.StateTransferManagerImpl.applyTransactionLog(StateTransferManagerImpl.java:250) 
> at org.infinispan.statetransfer.StateTransferManagerImpl.applyState(StateTransferManagerImpl.java:320) 
> ... 29 more 
> Now, in spite of this issue the test passes!!! (WTF?). 
> So, first things first, the test needs improving to send these issues back up. That probably means changing to a Callable rather than Runnable, and will see which exceptions we wanna swallow and which ones we wanna propagate. Then I'll get going to figure out the cause.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira