[JBoss JIRA] (ISPN-9982) Possible deadlock for clustered caches with Expiration enabled
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9982?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9982:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6679
> Possible deadlock for clustered caches with Expiration enabled
> --------------------------------------------------------------
>
> Key: ISPN-9982
> URL: https://issues.jboss.org/browse/ISPN-9982
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: William Burns
> Priority: Minor
>
> Add a test case for the following scenario:
> If a cache is configured for expiration an the intervall is != -1 there is a possiblity for a deadlock with JGroups and Infinispan threads because the reaper and any access to the same entry can cause a deadlock.
> The possibility is higher if the configured interval for the reaper is shorter.
> A thread dump might show something like followed:
> "HotRod-hotrod-internalServerWorker-4-12" #279 prio=5 os_prio=0 tid=0x00007f35980b8800 nid=0xbbb waiting for monitor entry [0x00007f356cfb4000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1910)
> - waiting to lock <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.handleInMemoryExpiration(ClusterExpirationManager.java:152)
> - locked <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.container.DefaultDataContainer.get(DefaultDataContainer.java:201)
> "pool-7-thread-1" #158 prio=5 os_prio=0 tid=0x00007f35c816c000 nid=0xb35 waiting for monitor entry [0x00007f3575238000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.lambda$handleInMemoryExpiration$0(ExpirationManagerImpl.java:137)
> - waiting to lock <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$$Lambda$374/1904915245.compute(Unknown Source)
> at org.infinispan.container.DefaultDataContainer.lambda$compute$3(DefaultDataContainer.java:336)
> at org.infinispan.container.DefaultDataContainer$$Lambda$375/1917382785.apply(Unknown Source)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1919)
> - locked <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:82)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9982) Possible deadlock for clustered caches with Expiration enabled
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9982?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9982:
--------------------------------
Status: Open (was: New)
> Possible deadlock for clustered caches with Expiration enabled
> --------------------------------------------------------------
>
> Key: ISPN-9982
> URL: https://issues.jboss.org/browse/ISPN-9982
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: William Burns
> Priority: Minor
>
> Add a test case for the following scenario:
> If a cache is configured for expiration an the intervall is != -1 there is a possiblity for a deadlock with JGroups and Infinispan threads because the reaper and any access to the same entry can cause a deadlock.
> The possibility is higher if the configured interval for the reaper is shorter.
> A thread dump might show something like followed:
> "HotRod-hotrod-internalServerWorker-4-12" #279 prio=5 os_prio=0 tid=0x00007f35980b8800 nid=0xbbb waiting for monitor entry [0x00007f356cfb4000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1910)
> - waiting to lock <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.handleInMemoryExpiration(ClusterExpirationManager.java:152)
> - locked <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.container.DefaultDataContainer.get(DefaultDataContainer.java:201)
> "pool-7-thread-1" #158 prio=5 os_prio=0 tid=0x00007f35c816c000 nid=0xb35 waiting for monitor entry [0x00007f3575238000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.lambda$handleInMemoryExpiration$0(ExpirationManagerImpl.java:137)
> - waiting to lock <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$$Lambda$374/1904915245.compute(Unknown Source)
> at org.infinispan.container.DefaultDataContainer.lambda$compute$3(DefaultDataContainer.java:336)
> at org.infinispan.container.DefaultDataContainer$$Lambda$375/1917382785.apply(Unknown Source)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1919)
> - locked <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:82)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9982) Possible deadlock for clustered caches with Expiration enabled
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9982?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9982:
--------------------------------
Security: (was: Red Hat Internal)
> Possible deadlock for clustered caches with Expiration enabled
> --------------------------------------------------------------
>
> Key: ISPN-9982
> URL: https://issues.jboss.org/browse/ISPN-9982
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: William Burns
> Priority: Minor
>
> Add a test case for the following scenario:
> If a cache is configured for expiration an the intervall is != -1 there is a possiblity for a deadlock with JGroups and Infinispan threads because the reaper and any access to the same entry can cause a deadlock.
> The possibility is higher if the configured interval for the reaper is shorter.
> A thread dump might show something like followed:
> "HotRod-hotrod-internalServerWorker-4-12" #279 prio=5 os_prio=0 tid=0x00007f35980b8800 nid=0xbbb waiting for monitor entry [0x00007f356cfb4000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1910)
> - waiting to lock <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.handleInMemoryExpiration(ClusterExpirationManager.java:152)
> - locked <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.container.DefaultDataContainer.get(DefaultDataContainer.java:201)
> "pool-7-thread-1" #158 prio=5 os_prio=0 tid=0x00007f35c816c000 nid=0xb35 waiting for monitor entry [0x00007f3575238000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.lambda$handleInMemoryExpiration$0(ExpirationManagerImpl.java:137)
> - waiting to lock <0x0000000742cc9898> (a org.infinispan.container.entries.metadata.MetadataTransientCacheEntry)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$$Lambda$374/1904915245.compute(Unknown Source)
> at org.infinispan.container.DefaultDataContainer.lambda$compute$3(DefaultDataContainer.java:336)
> at org.infinispan.container.DefaultDataContainer$$Lambda$375/1917382785.apply(Unknown Source)
> at org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8.compute(EquivalentConcurrentHashMapV8.java:1919)
> - locked <0x0000000742cca028> (a org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$Node)
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:335)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:135)
> at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:82)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles
by Don Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-9963?page=com.atlassian.jira.plugin.... ]
Don Naro updated ISPN-9963:
---------------------------
Sprint: JDG Sprint #25
> Restructure Documentation Titles
> --------------------------------
>
> Key: ISPN-9963
> URL: https://issues.jboss.org/browse/ISPN-9963
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Affects Versions: 10.0.0.Beta1
> Reporter: Don Naro
> Assignee: Don Naro
> Priority: Major
>
> This enhancement is to restructure the layout of the documentation directory and set up the titles for the 10.0 community release.
> The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can start to be broken down into sections and smaller units of reusable information.
> Definition of done for this issue:
> - Community and productized titles build successfully.
> - Community website updated to handle new titles.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month