[JBoss JIRA] (ISPN-3743) Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3743?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-3743:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1039090, https://bugzilla.redhat.com/show_bug.cgi?id=900946 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1039090)
> 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: Core
> 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: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-3942:
------------------------------------
Ok, then I guess it's worth integrating in master. Looks like it would break compatibility if we were to integrate it in 5.2.x, because the transport factory is configurable (property {{infinispan.client.hotrod.transport_factory}}).
> HotRod client keep trying recover a connection to a cluster member after shutdown
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3942
> URL: https://issues.jboss.org/browse/ISPN-3942
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Environment: Infinispan server with HotRod client in server-client mode and replicated caches.
> Reporter: Wolf-Dieter Fink
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: clustered, hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
> Attachments: hotrod-client.log
>
>
> If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
> There is only a replicated cache configured.
> From the server-logfile the new cluster view is established
> 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered]
> There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
> This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.
--
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: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-3996) LocalCachePerformantConfTest fails randomly
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-3996:
---------------------------------
Summary: LocalCachePerformantConfTest fails randomly
Key: ISPN-3996
URL: https://issues.jboss.org/browse/ISPN-3996
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Query
Affects Versions: 6.0.1.Final
Reporter: Pedro Ruivo
Assignee: Sanne Grinovero
Fix For: 7.0.0.Alpha1, 7.0.0.Final
org.infinispan.query.blackbox.LocalCachePerformantConfTest
LocalCachePerformantConfTest.testLazyIterator
LocalCachePerformantConfTest.testLazyIteratorWithInvalidFetchSize
LocalCachePerformantConfTest.testLazyIteratorWithNoElementsFound
LocalCachePerformantConfTest.testLazyIteratorWithOffset
LocalCachePerformantConfTest.testMaxResults
LocalCachePerformantConfTest.testModified
LocalCachePerformantConfTest.testMultipleResults
LocalCachePerformantConfTest.testRemoved
LocalCachePerformantConfTest.testSearchKeyTransformer
LocalCachePerformantConfTest.testSearchManagerWithInstantiation
LocalCachePerformantConfTest.testSearchManagerWithNullCache
LocalCachePerformantConfTest.testSetFilter
LocalCachePerformantConfTest.testSetSort
LocalCachePerformantConfTest.testSimple
LocalCachePerformantConfTest.testSimpleForNonField
LocalCachePerformantConfTest.testTypeFiltering
LocalCachePerformantConfTest.testUnknownFetchModeIterator
LocalCachePerformantConfTest.testUpdated
http://ci.infinispan.org/viewLog.html?buildId=5947&tab=buildResultsDiv&bu...
--
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: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-3997:
--------------------------------------
Summary: Expired cache entries are not pruned from memory and store on access
Key: ISPN-3997
URL: https://issues.jboss.org/browse/ISPN-3997
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
Environment: Remote HotRod access to infinispan-server
Reporter: Wolf-Dieter Fink
Assignee: Dan Berindei
Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration.
This will not be done if the key is access.
In case of having no scheduler to prune the entries this might cause OutOfMemory issues.
--
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: http://www.atlassian.com/software/jira
12 years, 1 month