[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-551) ReplicationQueue might attempt to use a closed JGroupsTransport
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Tue Jul 27 02:33:49 EDT 2010
[ https://jira.jboss.org/browse/ISPN-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreno resolved ISPN-551.
-----------------------------------
Resolution: Done
> ReplicationQueue might attempt to use a closed JGroupsTransport
> ---------------------------------------------------------------
>
> Key: ISPN-551
> URL: https://jira.jboss.org/browse/ISPN-551
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 4.0.0.Final, 4.1.0.CR2
> Reporter: Sanne Grinovero
> Assignee: Galder Zamarreno
> Fix For: 4.1.0.Final
>
>
> As mentioned on mailing list:
> java.lang.NullPointerException
> at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:92)
> at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:128)
> at org.infinispan.remoting.ReplicationQueue.flush(ReplicationQueue.java:147)
> at org.infinispan.remoting.ReplicationQueue$1.run(ReplicationQueue.java:99)
> 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)
> It looks like the transport is closed before the ReplicationQueue finished, as Galder suggested on ML setting the @Stop order on ReplicationQueue @Stop(priority=9) appears to fix it.
--
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