[infinispan-issues] [JBoss JIRA] Commented: (ISPN-960) Non serializable object errors not obvious when repl queue on
[
https://issues.jboss.org/browse/ISPN-960?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-960:
---------------------------------------
My plan is to fix this by adding a new interceptor called IsMarshallableInterceptor. This
interceptor will be inserted when either:
- Async repl is enabled, or
- Async marshalling is enabled, or
- Lazy deserialization is enabled
Since this interceptor will go before MarshalledValueInterceptor, we can get rid of the
code to check for isMarshallable in MarshalledValue constructor and hence we come up with
a cleaner solution for handling cases where we need to check whether the stuff is actually
marshallable.
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