8:23 a.m.
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.1.CR3, 4.2.0.Final
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
8:23 a.m.
New subject: [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:
---------------------------------------
This came from talking to Jim Crossley from the Torquebox team who couldn't figure out
why replication was not working. It's only when we enabled TRACE that the issue became
apparent. It should be more obvious.
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
6:39 a.m.
New subject: [JBoss JIRA] Work started: (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...
]
Work on ISPN-960 started by Galder Zamarreño.
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
11:41 a.m.
New subject: [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:
---------------------------------------
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
12:06 p.m.
New subject: [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
12:27 p.m.
New subject: [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:
---------------------------------------
It also makes sense adding the interceptor if async store is on.
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
9:09 a.m.
New subject: [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:
---------------------------------------
https://github.com/infinispan/infinispan/pull/185
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
4:04 a.m.
New subject: [JBoss JIRA] Resolved: (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 resolved ISPN-960.
-----------------------------------
Resolution: Done
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
6:22 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Manik Surtani updated ISPN-960:
-------------------------------
Fix Version/s: 4.2.1.CR4
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.CR4, 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
6:50 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
SBS JIRA Integration updated ISPN-960:
--------------------------------------
Forum Reference: http://community.jboss.org/message/578084#578084
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.CR4, 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
4968
days inactive
5068
days old
infinispan-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
SBS JIRA Integration (JIRA)