]
Manik Surtani updated JBCACHE-711:
----------------------------------
Fix Version/s: 2.0.0.GA
(was: 2.0.0.BETA1)
Replication eats out exception on the remote node
-------------------------------------------------
Key: JBCACHE-711
URL:
http://jira.jboss.com/jira/browse/JBCACHE-711
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Replication
Affects Versions: 1.4.0.GA
Reporter: Ben Wang
Assigned To: Manik Surtani
Fix For: 2.0.0.GA
I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication.
When the remote node throws an exception like NPE, the originating node will display with
NonSerializableException. I don't a unit test for this but I think it should be easy
to reproduce.
21:51:32,490 INFO [TxInterceptor] There was a problem handling this request
java.io.NotSerializableException: RpcDispatcher returned a null. This is most often
caused by args for _replicate(_put(null,
/testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean,
org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable.
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214)
at
org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
at
org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
at
org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114)
at
org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: