[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-666) MultipleRpcCommand being serialized ignoring the @Marshaller

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Thu Oct 21 11:37:54 EDT 2010


     [ https://jira.jboss.org/browse/ISPN-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño resolved ISPN-666.
-----------------------------------

    Fix Version/s:     (was: 4.2.0.BETA1)
       Resolution: Cannot Reproduce Bug


Sanne, I'm closing this jira since we haven't been able to replicate this issue yet.

However, the changes I made as part of ISPN-699 should clarify this issue further if it appears again cos I have added more precise logging and exceptions around this area. Also, to help with this issue, I've switched the logging of the NSE to debug level.

Feel free to reopen it once you've tested with the new 4.2.x release to be out in the next few days if you encounter a similar issue.

> MultipleRpcCommand being serialized ignoring the @Marshaller
> ------------------------------------------------------------
>
>                 Key: ISPN-666
>                 URL: https://jira.jboss.org/browse/ISPN-666
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Marshalling, RPC
>    Affects Versions: 4.2.0.ALPHA2
>            Reporter: Sanne Grinovero
>            Assignee: Galder Zamarreño
>            Priority: Critical
>
> I'm getting the following stacktrace:
> 2010-09-23 00:10:28,232 ERROR [ReplicationQueue] (Scheduled-ReplicationQueueThread-1) failed replicating 1 elements in replication queue
> org.infinispan.CacheException: java.lang.RuntimeException: Failure to marshal argument(s)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:122)
> 	at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:403)
> 	at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:100)
> 	at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:128)
> 	at org.infinispan.remoting.ReplicationQueueImpl.flush(ReplicationQueueImpl.java:126)
> 	at org.infinispan.remoting.ReplicationQueueImpl$1.run(ReplicationQueueImpl.java:83)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.RuntimeException: Failure to marshal argument(s)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$ReplicationTask.marshallCall(CommandAwareRpcDispatcher.java:242)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$ReplicationTask.call(CommandAwareRpcDispatcher.java:266)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:120)
> 	... 14 more
> Caused by: org.infinispan.marshall.NotSerializableException: org.infinispan.commands.remote.MultipleRpcCommand
> Caused by: an exception which occurred:
> 	in object org.infinispan.commands.remote.MultipleRpcCommand at dcf4f7b7
> On the default cache, being configured as :
> <default>
>       <clustering mode="replication">
>          <async useReplQueue="true" replQueueInterval="300" asyncMarshalling="false" />
>       </clustering>
>       <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000" lockAcquisitionTimeout="6000" writeSkewCheck="false" useLockStriping="false" />
>       <jmxStatistics enabled="false" />
>       <eviction maxEntries="-1" strategy="NONE" />
>       <expiration maxIdle="-1" />
>    </default>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list