From: Rod M. <rma...@ve...> - 2004-01-26 14:10:17
|
It is my understanding there is little point in an arbitrary GC call. Periodic GC calls have some benefit in terms of distributing effort over time however that is already available through JVM options. That memory shoots up is not relevant unless and until there is insufficient memory to satisfy an allocation request. At that point the GC will run and all threads are suspended within the JVM so no allocation request will occur. The GC will run as often as needed to satisfy the need for additional memory. Out of memory will occur if and only if there are indeed to many reachable references that cannot be released. I would add that the heap is divided in two so that you can run out of the so-called eden space and that can be adjusted using the JVM memory switches. Seems to be a common misconception that forcing a GC will cure out of memory problems. If anybody has knowledget that contradicts this by all means post it since this seems to be an area of frequent concern. Kind of off-topic AFA JBoss is concerned however. =20 -----Original Message----- From: Muraly R [mailto:mur...@ci...]=20 Sent: Thursday, January 22, 2004 9:42 PM To: jbo...@li... Subject: [JBoss-user] Garbage Collector: Service? Hi Gurus, Is there any particular service available in JBoss to schedule the garbage=20 collector? The reason for this question is our application is using heavy weight=20 objects like Vector, HashTable, etc. heavily. As a result of this after a=20 simple get query the JBoss memory shoots up and it is not returning to is=20 normal state. Hence this query. Also, for SessionBeans(Stateful/Stateless), if the <cache-policy-conf> is=20 configured as follows: <cache-policy-conf> <min-capacity>50</min-capacity> <max-capacity>1000000</max-capacity> <remover-period>600</remover-period> <max-bean-life>600</max-bean-life> <overager-period>300</overager-period> <max-bean-age>300</max-bean-age> <resizer-period>400</resizer-period> <max-cache-miss-period>60</max-cache-miss-period> <min-cache-miss-period>1</min-cache-miss-period> <cache-load-factor>0.75</cache-load-factor> </cache-policy-conf> and if the ejbRemove() of the corresponding beans are populated with code=20 to 'null' the object will this help. Please suggest. Cheers Muraly =09 ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list JBo...@li... https://lists.sourceforge.net/lists/listinfo/jboss-user |