[JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2903:
-----------------------------------------------
Paul Ferraro <paul.ferraro(a)redhat.com> changed the Status of [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549] from ASSIGNED to POST
> Manual eviction should not delete entry from cache store
> --------------------------------------------------------
>
> Key: ISPN-2903
> URL: https://issues.jboss.org/browse/ISPN-2903
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 5.2.x, jdg6
> Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log
>
>
> Here's the scenario:
> Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).
> 1. Create cache entry containing atomic map with 2 map entries on node1.
> 2. Passivate that cache entry on node2 via manual evict.
> 3. Modify 1 of the atomic map entries within the cache entry on node1.
> 4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost.
> It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.
--
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
11 years, 10 months
[JBoss JIRA] (ISPN-2547) org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2547?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2547:
--------------------------------
Fix Version/s: 5.3.0.Alpha1
(was: 5.2.0.CR2)
> org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
> -----------------------------------------------------------------------------
>
> Key: ISPN-2547
> URL: https://issues.jboss.org/browse/ISPN-2547
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Beta4
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
> Labels: testsuite_stability
> Fix For: 5.3.0.Alpha1
>
>
> The org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove() test fails randomly on all environments (RHEL6_x86 & RHEL6_x86_64, open jdk7, ibm jdk7, oracle jdk7).
> The following exception is thrown.
> {code}
> java.lang.AssertionError
> at org.infinispan.loaders.decorators.AsyncStoreTest.doTestRemove(AsyncStoreTest.java:423)
> at org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove(AsyncStoreTest.java:99)
> 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:80)
> at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
> at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 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
11 years, 10 months
[JBoss JIRA] (ISPN-2547) org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2547?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2547:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
> -----------------------------------------------------------------------------
>
> Key: ISPN-2547
> URL: https://issues.jboss.org/browse/ISPN-2547
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Beta4
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
> Labels: testsuite_stability
> Fix For: 5.2.0.CR2
>
>
> The org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove() test fails randomly on all environments (RHEL6_x86 & RHEL6_x86_64, open jdk7, ibm jdk7, oracle jdk7).
> The following exception is thrown.
> {code}
> java.lang.AssertionError
> at org.infinispan.loaders.decorators.AsyncStoreTest.doTestRemove(AsyncStoreTest.java:423)
> at org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove(AsyncStoreTest.java:99)
> 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:80)
> at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
> at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 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
11 years, 10 months
[JBoss JIRA] (ISPN-2914) Some tests are not picked up by Surefire - part2
by Anna Manukyan (JIRA)
Anna Manukyan created ISPN-2914:
-----------------------------------
Summary: Some tests are not picked up by Surefire - part2
Key: ISPN-2914
URL: https://issues.jboss.org/browse/ISPN-2914
Project: Infinispan
Issue Type: Task
Reporter: Anna Manukyan
Assignee: Anna Manukyan
Some tests are not picked up by Surefire. Because of this not all tests are run during release testings and it was found that there were some failing tests there.
Need to rename the tests.
--
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
11 years, 10 months
[JBoss JIRA] (ISPN-2547) org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2547?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2547:
--------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1717
> org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove fails randomly
> -----------------------------------------------------------------------------
>
> Key: ISPN-2547
> URL: https://issues.jboss.org/browse/ISPN-2547
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Beta4
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
> Labels: testsuite_stability
> Fix For: 5.2.0.CR2
>
>
> The org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove() test fails randomly on all environments (RHEL6_x86 & RHEL6_x86_64, open jdk7, ibm jdk7, oracle jdk7).
> The following exception is thrown.
> {code}
> java.lang.AssertionError
> at org.infinispan.loaders.decorators.AsyncStoreTest.doTestRemove(AsyncStoreTest.java:423)
> at org.infinispan.loaders.decorators.AsyncStoreTest.testPutRemove(AsyncStoreTest.java:99)
> 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:80)
> at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
> at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 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
11 years, 10 months
[JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2903:
--------------------------------
Labels: 5.2.x jdg6 (was: jdg6)
> Manual eviction should not delete entry from cache store
> --------------------------------------------------------
>
> Key: ISPN-2903
> URL: https://issues.jboss.org/browse/ISPN-2903
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 5.2.x, jdg6
> Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log
>
>
> Here's the scenario:
> Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).
> 1. Create cache entry containing atomic map with 2 map entries on node1.
> 2. Passivate that cache entry on node2 via manual evict.
> 3. Modify 1 of the atomic map entries within the cache entry on node1.
> 4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost.
> It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.
--
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
11 years, 10 months
[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated ISPN-1239:
---------------------------------
Bugzilla Update: (was: Perform)
> Graceful shutdown should be supported
> -------------------------------------
>
> Key: ISPN-1239
> URL: https://issues.jboss.org/browse/ISPN-1239
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Affects Versions: 5.0.0.FINAL
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: clean_shutdown, rehashing
> Fix For: 6.0.0.Final
>
>
> Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down.
> Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here.
--
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
11 years, 10 months
[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated ISPN-1239:
---------------------------------
Comment: was deleted
(was: Radoslav Husar <rhusar(a)redhat.com> made a comment on [bug 919399|https://bugzilla.redhat.com/show_bug.cgi?id=919399]
Unfortunately graceful cluster shutdown is not yet supported by Infinispan, thus not supported by the AS. See https://issues.jboss.org/browse/ISPN-1239)
> Graceful shutdown should be supported
> -------------------------------------
>
> Key: ISPN-1239
> URL: https://issues.jboss.org/browse/ISPN-1239
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Affects Versions: 5.0.0.FINAL
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: clean_shutdown, rehashing
> Fix For: 6.0.0.Final
>
>
> Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down.
> Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here.
--
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
11 years, 10 months
[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-1239:
-----------------------------------------------
Radoslav Husar <rhusar(a)redhat.com> made a comment on [bug 919399|https://bugzilla.redhat.com/show_bug.cgi?id=919399]
Unfortunately graceful cluster shutdown is not yet supported by Infinispan, thus not supported by the AS. See https://issues.jboss.org/browse/ISPN-1239
> Graceful shutdown should be supported
> -------------------------------------
>
> Key: ISPN-1239
> URL: https://issues.jboss.org/browse/ISPN-1239
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Affects Versions: 5.0.0.FINAL
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: clean_shutdown, rehashing
> Fix For: 6.0.0.Final
>
>
> Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down.
> Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here.
--
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
11 years, 10 months