Hi Manik, First of all, thanks for the reply. anonymous wrote : | I presume that these exceptions are fairly infrequent? |
The CacheException that i am seeing is VERY FREQUENT. We even tried out a few things, to try and find out the issue. In our configurations we changed the "maxNodes" attribute value to 10000 from the initial 5000, in the EvictionPolicyConfig. We also changed the implementation of the toString( ) method of the composite id classes of our hibernate objects. After these changes the application started working. We tried out executing 3-4 times and it worked. But, let me not jump to any conclusions. I am NOT sure whether these are related. You may be a better person to tell, whether these config settings and the implementation of the toString( ) method, has anything to do with the CacheException. We are still trying out a few things, to see whether these changes affect the application. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907862#3907862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907862 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
