[infinispan-issues] [JBoss JIRA] Commented: (ISPN-960) Non serializable object errors not obvious when repl queue on

[Galder Zamarreño (JIRA)]

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

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

Indeed, my suspicion is correct:
- With REPL_ASYNC (no repl queue), non serializable objects are reported to client code
- With REPL_ASYNC (repl queue or async marshalling), non serializable objects are not reported to client code

Same thing happens for the async variations of invalidation and distribution, but the important one is replication due to the AS6 use case.

> Non serializable object errors not obvious when repl queue on
> -------------------------------------------------------------
>
>                 Key: ISPN-960
>                 URL: https://issues.jboss.org/browse/ISPN-960
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Marshalling, RPC
>    Affects Versions: 4.2.0.Final, 4.2.1.CR3
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 4.2.1.FINAL
>
>
> Hmmm, it appears that when a cache is configured with REPL_ASYNC and repl queue, a non-serializable object being replicated will fail silently. It would appear as nothing replicates but the error will only become apparent when TRACE is enabled.
> This is not very nice and would have a direct impact in AS use case, cos web cache is configured this way and users often put stuff in the HTTP session that cannot be replicated.
> This would cause issues amongst users. Verify what happens with std REPL_ASYNC (I think here the serialization still happens in same thread and so the users would see it). Async marshalling would also need to be checked.

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