[JBoss JIRA] (ISPN-2551) HotRod Client testsuite leaves many dangling threads
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-2551:
-------------------------------------
Summary: HotRod Client testsuite leaves many dangling threads
Key: ISPN-2551
URL: https://issues.jboss.org/browse/ISPN-2551
Project: Infinispan
Issue Type: Bug
Components: Cache Server, Test Suite
Affects Versions: 5.2.0.Beta4
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 5.2.0.CR1
Some of the HotRod client tests don't kill some of the RemoteCacheManagers and/or HotRodServers they create
--
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-2549) Invalidation mode caches with pessimistic transactions may result in stale remote locks
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-2549:
-----------------------------------
Summary: Invalidation mode caches with pessimistic transactions may result in stale remote locks
Key: ISPN-2549
URL: https://issues.jboss.org/browse/ISPN-2549
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Reporter: Adrian Nistor
Assignee: Adrian Nistor
An invalidation mode cluster with two nodes A and B. Node A is coordinator.
Putting a key on node B results in a remote lock being acquired on A. But the lock on A is not released when the TX commits. Subsequent attempts to lock the key on A will fail with TimeoutException.
The key aspects to reproduce this are:
1. pessimistic locking
2. the transaction starts on a node different than the coordinator
This scenario does not involve any state transfer, so it should not be related to the already known issues with stale locks caused by state-transfer.
--
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-2354) AsyncStoreFunctionalTest fails intermittently
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-2354?page=com.atlassian.jira.plugin.... ]
Dan Berindei resolved ISPN-2354.
--------------------------------
Resolution: Out of Date
Galder, I haven't seen this test in a while - the latest failure on my machine was on Oct 12th.
I'm not seeing the particular AsyncStoreTest failure I mentioned in my last comment either, but I am seeing another failure - see ISPN-2535.
> AsyncStoreFunctionalTest fails intermittently
> ---------------------------------------------
>
> Key: ISPN-2354
> URL: https://issues.jboss.org/browse/ISPN-2354
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Alpha4
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 6.0.0.Final
>
>
> AsyncStoreFunctionalTest sometimes fails with this assertion error:
> {noformat}
> 14:49:46,380 ERROR (testng-AsyncStoreFunctionalTest:) [UnitTestTestNGListener] Test testGetAfterRemove(org.infinispan.loaders.decorators.AsyncStoreFunctionalTest) failed.
> java.lang.AssertionError: Keys not empty: [1]
> at org.testng.AssertJUnit.fail(AssertJUnit.java:57)
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:22)
> at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest$3.call(AsyncStoreFunctionalTest.java:211)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1252)
> at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest.testGetAfterRemove(AsyncStoreFunctionalTest.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1147)
> at org.testng.TestRunner.privateRun(TestRunner.java:749)
> at org.testng.TestRunner.run(TestRunner.java:600)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)
> at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {noformat}
--
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-2538) Endless loop in TreeMap.remove at shutdown of query-enabled cache
by Marko Lukša (JIRA)
Marko Lukša created ISPN-2538:
---------------------------------
Summary: Endless loop in TreeMap.remove at shutdown of query-enabled cache
Key: ISPN-2538
URL: https://issues.jboss.org/browse/ISPN-2538
Project: Infinispan
Issue Type: Feature Request
Components: Querying
Affects Versions: 5.2.0.Beta4
Reporter: Marko Lukša
Assignee: Marko Lukša
{code}
"MSC service thread 1-6" prio=6 tid=0x000000000d5b9000 nid=0x10a0 runnable [0x000000000e45e000]
java.lang.Thread.State: RUNNABLE
at java.util.TreeMap.fixAfterDeletion(TreeMap.java:2215)
at java.util.TreeMap.deleteEntry(TreeMap.java:2173)
at java.util.TreeMap.remove(TreeMap.java:600)
at org.infinispan.query.impl.LifecycleManager.cacheStopped(LifecycleManager.java:181)
at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:227)
at org.infinispan.CacheImpl.stop(CacheImpl.java:540)
at org.infinispan.CacheImpl.stop(CacheImpl.java:535)
at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:348)
at org.jboss.as.capedwarf.services.CacheLifecycleService.stop(CacheLifecycleService.java:94)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
--
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-2542) AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2542:
--------------------------------------
Summary: AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly
Key: ISPN-2542
URL: https://issues.jboss.org/browse/ISPN-2542
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Galder Zamarreño
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
Attachments: testRestrictionOnAddingToAsyncQueue-2.log.zip
{code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest): Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000{code}
--
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-2354) AsyncStoreFunctionalTest fails intermittently
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2354?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-2354:
----------------------------------------
Sanne/Dan, provide some trace logs next time :)
> AsyncStoreFunctionalTest fails intermittently
> ---------------------------------------------
>
> Key: ISPN-2354
> URL: https://issues.jboss.org/browse/ISPN-2354
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Alpha4
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 6.0.0.Final
>
>
> AsyncStoreFunctionalTest sometimes fails with this assertion error:
> {noformat}
> 14:49:46,380 ERROR (testng-AsyncStoreFunctionalTest:) [UnitTestTestNGListener] Test testGetAfterRemove(org.infinispan.loaders.decorators.AsyncStoreFunctionalTest) failed.
> java.lang.AssertionError: Keys not empty: [1]
> at org.testng.AssertJUnit.fail(AssertJUnit.java:57)
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:22)
> at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest$3.call(AsyncStoreFunctionalTest.java:211)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1252)
> at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest.testGetAfterRemove(AsyncStoreFunctionalTest.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1147)
> at org.testng.TestRunner.privateRun(TestRunner.java:749)
> at org.testng.TestRunner.run(TestRunner.java:600)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)
> at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {noformat}
--
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-2475) When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners
by Dan Berindei (JIRA)
Dan Berindei created ISPN-2475:
----------------------------------
Summary: When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners
Key: ISPN-2475
URL: https://issues.jboss.org/browse/ISPN-2475
Project: Infinispan
Issue Type: Sub-task
Components: State transfer
Affects Versions: 5.1.0.FINAL
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.CR1
Copied from the parent:
{quote}
[...] we can keep track of the consistent hashes in the last 10 minutes (or whatever the L1 lifespan is) and the time of the last invalidation sent for each key. When we need to send a new invalidation, we add the owners in all the consistent hashes since the last invalidation to the invalidation command recipients.
{quote}
--
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-2425) Amend the xsite configuration and the xsd
by Mircea Markus (JIRA)
Mircea Markus created ISPN-2425:
-----------------------------------
Summary: Amend the xsite configuration and the xsd
Key: ISPN-2425
URL: https://issues.jboss.org/browse/ISPN-2425
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 5.2.0.Beta2
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
Change:
{code:xml}
<global>
...
<sites local="LON"/>
...
</global>
{code}
to
{code:xml}
<global>
...
<site name="LON"/>
...
</global>
{code}
And:
{code:xml}
<backups backupSites="NYC,SFO">
<backup site="NYC" backupFailurePolicy="WARN" strategy="SYNC" timeout="12000"/>
<backup site="SFO" backupFailurePolicy="IGNORE" strategy="ASYNC"/>
<backup site="LON" strategy="SYNC"/>
</backups>
{code}
to:
{code:xml}
<backups>
<backup site="NYC" failurePolicy="WARN" strategy="SYNC" timeout="12000" enabled="true"/>
<backup site="SFO" failurePolicy="IGNORE" strategy="ASYNC" enabled="true"/>
<backup site="LON" strategy="SYNC" enabled="false"/>
</backups>
{code}
--
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