[jboss-jira] [JBoss JIRA] Closed: (JBRULES-1919) JBRMS has memory leak for RuleAgent url access
Toni Rikkola (JIRA)
jira-events at lists.jboss.org
Tue Mar 17 08:54:50 EDT 2009
[ https://jira.jboss.org/jira/browse/JBRULES-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Rikkola closed JBRULES-1919.
---------------------------------
Fix Version/s: 4.0.8
Resolution: Done
This is also fixed in releases after 5.0.0.CR1
> JBRMS has memory leak for RuleAgent url access
> ----------------------------------------------
>
> Key: JBRULES-1919
> URL: https://jira.jboss.org/jira/browse/JBRULES-1919
> Project: JBoss Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-guvnor
> Affects Versions: 4.0.7
> Environment: Solaris, JBOSS server and Glassfish 9
> Reporter: Richard Ambridge
> Assignee: Toni Rikkola
> Fix For: 4.0.8
>
>
> Drools JBRMS has a memory leak when the RulesAgent accesses the BRMS to check the status of a snapshot.
> If a RuleAgent is configured with
> url=http://localhost:8080/.../package/NAME/SNAPSHOT
> poll=60
> then the memory usage in the VM will increase until eventually it runs out of memory.
> This can be observed using jconsole.
> The problem lies in
> drools-jbrms
> org.drools.brms.server.files.FileManagerUtils.java
> This creates a Seam EVENT each time the RuleAgent accesses the GUI,
> the EVENT is only in context for the event, so it creates a RulesRepository during creation,
> but it never releases the RulesRepository so a session is left open, and the Event cannot be GC.
> Fix is
> 46d45
> < import org.jboss.seam.annotations.Destroy;
> 64,67d62
> < @Destroy
> < public void close(){
> < repository.logout();
> < }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list