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

[Nick . (JIRA)]

    [ https://issues.jboss.org/browse/JBCACHE-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772946#comment-12772946 ] 

Nick . edited comment on JBCACHE-1332 at 5/9/13 3:52 AM:
---------------------------------------------------------

Hi Mircea,
          Thanks for your response, We are in bad situation where we can't migrate to Infinispan since we are using JBoss AS-4.2.3GA.

Issue JBCACHE-1596(does this addressing the same issue ?)
                
      was (Author: nick.sree):
    Hi Mircea,
          Thanks for your response, We are in bad situation where we can't migrate to Infinispan since we are using JBoss AS-4.2.3GA.

Issue JBCACHE-1596 & JBCACHE-1332 (does this addressing the same 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