[infinispan-issues] [JBoss JIRA] Commented: (ISPN-835) State transfer should not force all invocations to be synchronous

[Galder Zamarreño (JIRA)]

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

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

Having talked to Steve Ebersole, they're planning a Hibernate 3.6.1 release next week which should fix the issue. This release will be included in AS 6.0.1.

Re: File loader? Hmmm, not sure but I really think you'd be better off waiting for a fix than trying out diff configurations.

> State transfer should not force all invocations to be synchronous
> -----------------------------------------------------------------
>
>                 Key: ISPN-835
>                 URL: https://issues.jboss.org/browse/ISPN-835
>             Project: Infinispan
>          Issue Type: Bug
>          Components: RPC, State transfer
>    Affects Versions: 4.1.0.Final, 4.2.0.CR4
>            Reporter: Galder Zamarreño
>            Assignee: Manik Surtani
>             Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>         Attachments: stdout-hsqldb-node1.txt.zip, stdout-hsqldb-node2.txt.zip
>
>
> Enabling state transfer is forcing even asynchronous caches to become synchronous.
> A better way is needed to make sure state transfer works correctly (sync calls needed here) while normal replication calls remain asynchronous.
> See https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/remoting/transport/jgroups/CommandAwareRpcDispatcher.java#L254 where the response mode is overridden based on whether replay is supported.  And replay support is always on when state transfer is enabled:
> https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/remoting/rpc/RpcManagerImpl.java#L101
> Need to explore whether a joiner flag can be maintained based on a view change, and replay only supported when a joiner is still "joining", and not otherwise.

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