[JBoss JIRA] (ISPN-2903) CLONE - Eviction causes lost AtomicMap entries
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated ISPN-2903:
-------------------------------
Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/1163)
> CLONE - Eviction causes lost AtomicMap entries
> ----------------------------------------------
>
> 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: jdg6
> Fix For: 5.2.4.Final, 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2095) Eviction causes lost AtomicMap entries
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-2095:
------------------------------------------
Bugzilla Update: (was: Perform)
Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=900549)
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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) CLONE - Eviction causes lost AtomicMap entries
by Paul Ferraro (JIRA)
Paul Ferraro created ISPN-2903:
----------------------------------
Summary: CLONE - Eviction causes lost AtomicMap entries
Key: ISPN-2903
URL: https://issues.jboss.org/browse/ISPN-2903
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 5.1.5.FINAL
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
Priority: Critical
Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
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.
--
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) CLONE - Eviction causes lost AtomicMap entries
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated ISPN-2903:
-------------------------------
Fix Version/s: 5.2.4.Final
5.3.0.Alpha1
(was: 5.2.0.Final)
(was: 5.2.0.ALPHA1)
(was: 5.1.6.FINAL)
Affects Version/s: 5.2.3.Final
(was: 5.1.5.FINAL)
> CLONE - Eviction causes lost AtomicMap entries
> ----------------------------------------------
>
> 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: jdg6
> Fix For: 5.2.4.Final, 5.3.0.Alpha1
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2889) AbstractIterator shouldn't allocate a larger result array than is necessary
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-2889?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero updated ISPN-2889:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> AbstractIterator shouldn't allocate a larger result array than is necessary
> ---------------------------------------------------------------------------
>
> Key: ISPN-2889
> URL: https://issues.jboss.org/browse/ISPN-2889
> Project: Infinispan
> Issue Type: Enhancement
> Components: Querying
> Reporter: Marko Lukša
> Assignee: Marko Lukša
> Fix For: 5.3.0.Alpha1
>
>
> Currently {{AbstractIterator}} (superclass of LazyIterator and EagerIterator) always allocates an {{Object[]}} array of size {{fetchSize}}, even when the actual number of results is smaller than {{fetchSize}}.
> This is especially problematic when the user wants to fetch all the results at once (by setting fetchSize to a very large number such as Integer.MAX_VALUE). This results in an OutOfMemoryError: Requested array size exceeds VM limit.
> Since the number of results is known up-front, {{AbstractIterator}} can allocate a smaller array.
--
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-2095) Eviction causes lost AtomicMap entries
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2095:
-----------------------------------
Affects Version/s: (was: 5.2.3.Final)
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2095) Eviction causes lost AtomicMap entries
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño resolved ISPN-2095.
------------------------------------
Resolution: Done
Original issue was fixed, and the fix versions have been released.
Please open a new jira, link to this one, and assign it to me. Please indicate the AS version failing with this, and attach TRACE logs on org.infinispan if available.
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.2.0.Final, 5.2.0.ALPHA1, 5.1.6.FINAL
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2095) Eviction causes lost AtomicMap entries
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-2095:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900549
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL, 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2095) Eviction causes lost AtomicMap entries
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reopened ISPN-2095:
--------------------------------
The attached test is failing on 5.2.3.Final
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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-2095) Eviction causes lost AtomicMap entries
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/ISPN-2095?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated ISPN-2095:
-------------------------------
Affects Version/s: 5.2.3.Final
> Eviction causes lost AtomicMap entries
> --------------------------------------
>
> Key: ISPN-2095
> URL: https://issues.jboss.org/browse/ISPN-2095
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.5.FINAL, 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg6
> Fix For: 5.1.6.FINAL, 5.2.0.ALPHA1, 5.2.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java
>
>
> 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.
--
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