jbosscache-issues April 2013

jbosscache-issues@lists.jboss.org

1 participants
4 discussions

[JBoss JIRA] (JBCACHE-1332) Lock in eviction.Region:putNodeEvent()

by Nick . (JIRA)

[ https://issues.jboss.org/browse/JBCACHE-1332?page=com.atlassian.jira.plug... ] Nick . edited comment on JBCACHE-1332 at 4/22/13 11:42 PM: ----------------------------------------------------------- Any update on this issue...? Can anyone please suggest some way to over come this thread blocking issue.? was (Author: nick.sree): ANy update on this issue... can anyone please suggest some way to over come this thread blocking issue. > Lock in eviction.Region:putNodeEvent() > -------------------------------------- > > Key: JBCACHE-1332 > URL: https://issues.jboss.org/browse/JBCACHE-1332 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Eviction > Affects Versions: 1.4.1.SP1 > Environment: JBoss 4.05 > Hibernate 3.2.6.ga > Reporter: Nicolas Lebreton > Assignee: Manik Surtani > Priority: Critical > Fix For: 1.4.X > > Attachments: 2008-04-10-molene.nexotelematics.com_susan_node2_Percentage db connections in use.jpg, 2008-04-25 locktree.svg, jboss-service.xml, ThreadDumps.zip > > > JBoss TreeCache is used as cache provider. Please find attached jboss-service.xml configuration file. > The second level cache is actitated, and several read-only classes are cacheable: > <cache usage="read-only"/> > The query cache is activated, and few queries are cacheable: > <query name="ActorType.listAll.named" cacheable="true"> > > We encounter an issue. It can be reproduced on an environment with only few users connected (less than 10). For those users, screen is refreshed every 30 seconds through Ajax requests. > Application is running in a cluster. On the other hand, this issue occurs with only one node started. A JBoss is started. Less than 24 hours later, application is becoming unresponsive. JBoss then needs to be recycled. And it works. > Before stoping the node, I have taken several thread dumps separated by at least 30 seconds. Please find attached 10th, 11th, 25th's output files. We noticed thread locks in these 3 snapshots. The stack trace of the culprit was always the same (please see attached outputs for more details): > # java.lang.Object:wait > # waiting on-->EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue(0x9331fd60) > # java.lang.Object:wait(Object.java:474) > # EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue:put > # locked-->EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue(0x9331fd60) > # locked-->java.lang.Object(0x9331fe78) > # org.jboss.cache.eviction.Region:putNodeEvent(Region.java:141) > # org.jboss.cache.interceptors.EvictionInterceptor:doEventUpdatesOnRegionManager(EvictionInterceptor.java:145) > # org.jboss.cache.interceptors.EvictionInterceptor:updateNode(EvictionInterceptor.java:118) > # org.jboss.cache.interceptors.EvictionInterceptor:invoke(EvictionInterceptor.java:93) > Nicolas -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBCACHE-1596) Initial state transfer with more than 200, 000 nodes deadlock on eviction queue

by Nick . (JIRA)

[ https://issues.jboss.org/browse/JBCACHE-1596?page=com.atlassian.jira.plug... ] Nick . commented on JBCACHE-1596: --------------------------------- Can some one tell me, does this fix is same for [JBCACHE-1332|https://issues.jboss.org/browse/JBCACHE-1332] ? If so apart from replacing with this jar, do we have to add or change any attribute value in replySync-Service.xml ? > Initial state transfer with more than 200,000 nodes deadlock on eviction queue > ------------------------------------------------------------------------------ > > Key: JBCACHE-1596 > URL: https://issues.jboss.org/browse/JBCACHE-1596 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Eviction > Affects Versions: 1.4.1.SP13 > Reporter: Dennis Reed > Assignee: Dennis Reed > Fix For: 1.4.1.SP15 > > > When the cache has more than 200,000 entries, state transfer deadlocks on the joining node, > due to filling up and blocking the eviction queue before the eviction thread has been started. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBCACHE-1631) Issue exist in JBCache-1.4.1-SP14

by Nick . (JIRA)

Nick . created JBCACHE-1631: ------------------------------- Summary: Issue exist in JBCache-1.4.1-SP14 Key: JBCACHE-1631 URL: https://issues.jboss.org/browse/JBCACHE-1631 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Eviction, Locking Affects Versions: 1.4.1.SP14 Reporter: Nick . Assignee: Manik Surtani Priority: Blocker -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBCACHE-1332) Lock in eviction.Region:putNodeEvent()

by Nick . (JIRA)

[ https://issues.jboss.org/browse/JBCACHE-1332?page=com.atlassian.jira.plug... ] Nick . commented on JBCACHE-1332: --------------------------------- ANy update on this issue... can anyone please suggest some way to over come this thread blocking issue. > Lock in eviction.Region:putNodeEvent() > -------------------------------------- > > Key: JBCACHE-1332 > URL: https://issues.jboss.org/browse/JBCACHE-1332 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Eviction > Affects Versions: 1.4.1.SP1 > Environment: JBoss 4.05 > Hibernate 3.2.6.ga > Reporter: Nicolas Lebreton > Assignee: Manik Surtani > Priority: Critical > Fix For: 1.4.X > > Attachments: 2008-04-10-molene.nexotelematics.com_susan_node2_Percentage db connections in use.jpg, 2008-04-25 locktree.svg, jboss-service.xml, ThreadDumps.zip > > > JBoss TreeCache is used as cache provider. Please find attached jboss-service.xml configuration file. > The second level cache is actitated, and several read-only classes are cacheable: > <cache usage="read-only"/> > The query cache is activated, and few queries are cacheable: > <query name="ActorType.listAll.named" cacheable="true"> > > We encounter an issue. It can be reproduced on an environment with only few users connected (less than 10). For those users, screen is refreshed every 30 seconds through Ajax requests. > Application is running in a cluster. On the other hand, this issue occurs with only one node started. A JBoss is started. Less than 24 hours later, application is becoming unresponsive. JBoss then needs to be recycled. And it works. > Before stoping the node, I have taken several thread dumps separated by at least 30 seconds. Please find attached 10th, 11th, 25th's output files. We noticed thread locks in these 3 snapshots. The stack trace of the culprit was always the same (please see attached outputs for more details): > # java.lang.Object:wait > # waiting on-->EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue(0x9331fd60) > # java.lang.Object:wait(Object.java:474) > # EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue:put > # locked-->EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue(0x9331fd60) > # locked-->java.lang.Object(0x9331fe78) > # org.jboss.cache.eviction.Region:putNodeEvent(Region.java:141) > # org.jboss.cache.interceptors.EvictionInterceptor:doEventUpdatesOnRegionManager(EvictionInterceptor.java:145) > # org.jboss.cache.interceptors.EvictionInterceptor:updateNode(EvictionInterceptor.java:118) > # org.jboss.cache.interceptors.EvictionInterceptor:invoke(EvictionInterceptor.java:93) > Nicolas -- 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, 8 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues April 2013