-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Hibernate 3.3.0.CR1 / JBC2.1.1.CR2 evenQueueSize Bug?
PostPosted: Wed Jul 23, 2008 10:12 am 
Newbie

Joined: Tue Jul 22, 2008 10:16 am
Posts: 2
Hibernate version:3.3.0.CR1

JBossCache version:2.1.1.CR2

Under heavy load, several of the objects in my application reach the capacity threshold for JBossCache which generates the following warning and locks up the calls to select them.

eviction node event queue size is at 98% threshold value of capacity: 200000 Region: /org/somepath/MyClass/ENTITY You will need to reduce the wakeUpIntervalSeconds parameter.

I already have the wakeUpIntervalSeconds set to the minimum value of 1. I've tried increasing the eventQueueSize attribute but it is not being passed through to JBossCache. This seems to be a disconnect between the Hibernate initialization that passes the configurations on the JBossCache. Here is my EvictionPolicyConfig.

Code:
        <attribute name="EvictionPolicyConfig">
           <config>
             <attribute name="wakeUpIntervalSeconds">1</attribute>
             <attribute name="policyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
             <region name="/_default_" eventQueueSize="500000">
               <attribute name="maxNodes">50000</attribute>
               <attribute name="timeToLiveSeconds">3600</attribute>
               <attribute name="maxAgeSeconds">3600</attribute>
               <attribute name="minTimeToLiveSeconds">120</attribute>
             </region>
             <region name="/TS" policyClass="org.jboss.cache.eviction.NullEvictionPolicy"/>
           </config>
        </attribute>


All attributes appear to be flowing through other than the eventQueueSize although I have not found a way to confirm that wakeUpIntervalSeconds is being passed through correctly. Note that I've tried the attribute both inline as a sub attribute of the region and as an attribute at the config level. Here is how I'm checking the value on the eventQueueSize.

jbcRegion.getEvictionRegionConfig().getEventQueueSize();

Even though I configure it for 500000, it still is set to 200000. I can programatically adjust it but this feels like a hack since the XML configuration should take care of this. Is this a bug in Hibernate 3.3.0.CR1?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jul 23, 2008 5:28 pm 
Newbie

Joined: Tue Jul 22, 2008 10:16 am
Posts: 2
I'm finding that even with programatically increasing the eventQueueSize to 500000, it still locks up the cache under load after less than one hour and the following message is displayed.

eviction node event queue size is at 98% threshold value of capacity: 500000 Region: /org/somepath/MyClass/ENTITY You will need to reduce the wakeUpIntervalSeconds parameter.

If I roll back to JBossCache 1.4.1.x, the problem goes away. Do you think this would be a problem with JBossCache or is it the integration between Hibernate and JBossCache. It's almost like the eviction thread does not ever run or it blocks and gets hung. Anyone else having this issue or know of a resolution?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.