]
Dan Berindei updated ISPN-3743:
-------------------------------
Labels: testsuite_stability (was: )
Silence "IllegalStateException: Default cache is in
'STOPPING' state" exceptions
--------------------------------------------------------------------------------
Key: ISPN-3743
URL:
https://issues.jboss.org/browse/ISPN-3743
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 6.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Labels: testsuite_stability
Fix For: 7.0.0.Final
When a cache in STOPPING state receives a command, the exception is propagated all the
way to the caller:
{noformat}
09:33:02,005 ERROR (testng-NonTxPutIfAbsentDuringLeaveStressTest:)
[UnitTestTestNGListener] Test
testNodeLeavingDuringPutIfAbsent(org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringLeaveStressTest)
failed.
java.util.concurrent.ExecutionException: org.infinispan.remoting.RemoteException:
ISPN000217: Received exception from NodeC-25987, see cause for remote stack trace
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from
NodeC-25987, see cause for remote stack trace
at
org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41)
Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from
NodeD-57301, see cause for remote stack trace
at
org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41)
Caused by: java.lang.IllegalStateException: Default cache is in 'STOPPING' state
and this is an invocation not belonging to an on-going transaction, so it does not accept
new invocations. Either restart it or recreate the cache container.
at
org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:93)
{noformat}
This causes random failures in
NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent.
The originator should either ignore the IllegalStateException or wait for a new cache
topology and retry the operation, just like it should for SuspectExceptions (ISPN-2577).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: