[jboss-jira] [JBoss JIRA] (DROOLS-461) Memory Leak in Drools6.0.1-JavaLexer- Whenever application is restarted in websphere

[Davide Sottara (JIRA)]

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

Davide Sottara commented on DROOLS-461:
---------------------------------------

This is VERY weird.
Looking at the link from the IBM inforcenter posted by Mario, I can actually see two possible alternatives:

- Java local
    A local variable. For example, input parameters, or locally created objects of methods that are still in the stack of a thread.
@Mario: if I'm not mistaken, that method could be invoked during the jitting of a constraint, which is indeed done in a separate
thread: are we sure that that thread is properly terminated in this case?
We'd need to see the rules to understand when the lexer is actually needed.

- Unknown
    An object of unknown root type. Some dumps, such as IBM Portable Heap Dump (.phd) files, do not have root information
Otherwise, we'd need more information to track the source of that problem.

Maybe others, unfortunately I don't have much time to investigate these days
Davide
                
> Memory Leak in Drools6.0.1-JavaLexer- Whenever application is restarted in websphere
> ------------------------------------------------------------------------------------
>
>                 Key: DROOLS-461
>                 URL: https://issues.jboss.org/browse/DROOLS-461
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.1.Final
>         Environment: Websphere7.0, Java
>            Reporter: jacob sukumar
>            Assignee: Mario Fusco
>         Attachments: dump.7z, screenshot-1.jpg, screenshot-2.jpg
>
>
> Everytime we restarted the application on websphere and taking the heap dumps, we could able to see around 8MB of JavaLexer(org/drools/compiler/rule/builder/dialect/java/parser/JavaLexer) is leaking. Let us say if we restarted the application for 3 times, (8*3)24MB heap memory is leaking.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira