[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1580) Clustered SFSB caching fails due to inability to send to cluster

Clustered SFSB caching fails due to inability to send to cluster ---------------------------------------------------------------- Key: EJBTHREE-1580 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1580 Project: EJB 3.0 Issue Type: Bug Components: Clustering, core Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0-CR2 Andrew found an intermittent failure on an testsuite run; see the ScopedExtendedPersistenceUnitTestCase failures at http://jboss.hudson.alrubinger.com/job/EJB3_Plugin_AS_TRUNK/203/testReport/ . Relevant part of the failure trace in each of the failed tests is: Caused by: org.jboss.cache.lock.TimeoutException: State retrieval timed out waiting for flush unblock. at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:455) at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:432) at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:437) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:161) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:135) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:107) at org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudMethod(ReplicationInterceptor.java:160) at org.jboss.cache.interceptors.ReplicationInterceptor.visitPutKeyValueCommand(ReplicationInterceptor.java:107) at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100) at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:131) at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65) at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100) at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.jboss.cache.interceptors.TxInterceptor.attachGtxAndPassUpChain(TxInterceptor.java:284) at org.jboss.cache.interceptors.TxInterceptor.handleDefault(TxInterceptor.java:271) at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65) at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100) at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.jboss.cache.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:119) at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100) at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:178) at org.jboss.cache.interceptors.InvocationContextInterceptor.visitPutKeyValueCommand(InvocationContextInterceptor.java:82) at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100) at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:265) at org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:560) at org.jboss.ha.cachemanager.CacheManagerManagedCache.put(CacheManagerManagedCache.java:285) at org.jboss.ejb3.cache.tree.StatefulTreeCache.putInCache(StatefulTreeCache.java:511) at org.jboss.ejb3.cache.tree.StatefulTreeCache.create(StatefulTreeCache.java:123) ... 70 more This is really more of a JBC or JGroups issue, but I'm raising it here as what appears to have been a failure during the cache startup phase did not result in a deployment failure of the target bean. Need to understand why not. I'm opening a thread on jbosscache-dev(a)lists.jboss.org to discuss the underlying JBC issue.