Re: [rules-users] GC Overhead Limit Exceeded and 1B JoinLeftNode Objects

The GC uses **incoming** references to determine the liveness of an object and thus its eligibility for GC. The code here makes sure that the internal ReteooStatefulSession is no longer referenced by the StatefulKnowldegeSessionImpl wrapper, making it eligible for GC unless it's referenced somewhere else. The StatefulKnowledgeSessionImpl itself now may or may not be reachable anymore, depending on who was holding references to it. In any case, it is now pointing to the "Disposed" singleton, a mock, shared empty object. This said, you will need to provide more details about your configuration and usage. Just knowing that you have "hundreds of rules" does not help much in diagnosing the problem... :) Did your system work, say, in 5.4 and then started generating these OOMEs after moving to 5.5? Could the problem be reproduced systematically? What are your policies for retracting facts OR expiring sessions? See the previous messages in this thread for a list of other questions you may want to answer... Only then we may be able to provide some advice :) Best Davide On 02/25/2013 09:35 PM, ismaximum wrote: