Well, sometimes we see in production that the total number of objects cached is far more than what we defined for max node number in treecache.xml. We deploy hibernate session factory as mbean and turns on the session factory statistics so we can watch all the caching behavior. In one particular case, the max node in the treecache.xml is 30,000 but we saw the total objects cached is 97,000. The jvm eventually got outofmemory error and we had to restarted jboss. Althought this is rare case, we constantly observe that the total number objects cached outnumbers the max node number by a small amount.
Is this expected behavior? Why tree cache does not follow the max node that we defined?
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224092#4224092
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224092
anonymous wrote : have added the resource information to the web.xml and the jboss-web.xml files in the jbossws-sar
Try adding it to the WEB-INF directory in your WAR file. (I assume you have a POJO-based web service and not an EJB-based web service.)
If that doesn't work, post the full stack trace and the contents of the web.xml and jboss-web.xml file. And let us know what kind of web service you have.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224091#4224091
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224091