[jboss-jira] [JBoss JIRA] (JBRULES-3256) PropertyChangeListener of dynamic facts is not cleaned up on session.dispose()

RH Bugzilla Integration (Commented) (JIRA) jira-events at lists.jboss.org
Fri Nov 25 16:42:40 EST 2011


    [ https://issues.jboss.org/browse/JBRULES-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645690#comment-12645690 ] 

RH Bugzilla Integration commented on JBRULES-3256:
--------------------------------------------------

Edson Tirelli <etirelli at redhat.com> changed the Status of [bug 746887|https://bugzilla.redhat.com/show_bug.cgi?id=746887] from ASSIGNED to ON_QA
                
> PropertyChangeListener of dynamic facts is not cleaned up on session.dispose()
> ------------------------------------------------------------------------------
>
>                 Key: JBRULES-3256
>                 URL: https://issues.jboss.org/browse/JBRULES-3256
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.3.0.CR1
>            Reporter: Toshiya Kobayashi
>            Assignee: Edson Tirelli
>             Fix For: 5.3.1.Final, 5.4.0.Beta1
>
>         Attachments: PropertyListenerTest.drl, PropertyListenerTest.java
>
>
> PropertyChangeListener of dynamic facts is not cleaned up on session.dispose() and the remaining listener may cause some issues later on (unexpected firePropertyChange() and memory leak etc.).
> You can reproduce this with attached drl and java client.
> The output would be like:
> {noformat}
> == Listeners attached before rules ==
> == Listeners attached before rules ==
> Print name of person: Test 2
> Print name of person: Test 1
> Session disposed
> == Listeners attached after rules ==
> Listener attached of type: org.drools.common.NamedEntryPoint at 7d15d06c
> Listener attached of type: org.drools.common.NamedEntryPoint at 7d15d06c
> == Listeners attached after rules ==
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list