[
https://issues.apache.org/jira/browse/DELTASPIKE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701970#comment-13701970
]
Daniel Zwicker commented on DELTASPIKE-391:
-------------------------------------------
{quote}
>From a quick look at the code - I guess that's a consequence of moving the
>QueryHandler to application scope. Will think about how to properly clean this
>stuff up....
{quote}
This could be! We have many CDI beans just processing some kind of business
logic without any state. First they were in the dependent pseudo-scope and
everything was perfect. Then we make them application scope as a single
instance would be perfectly and we want them to be proxied by CDI so they are
managed even after injection. But we get MemoryLeaks and switched back to
dependent. I don't know if there is a bug in the weld implementation? As an
application scope bean should exist only once i believe, except for the proxies
which should be released and gc-ed!
The next days the plan is to try the javax.inject.Singleton scope as the
services could be singletons... we will see.
> Memory Leak in Data Module
> --------------------------
>
> Key: DELTASPIKE-391
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-391
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
> Affects Versions: 0.5
> Reporter: Thomas Hug
> Assignee: Thomas Hug
> Priority: Critical
>
> Might be a side effect from moving QueryHandler to application scope. Several
> beans injected over Instance<> are not cleaned up properly (probably handled
> as dependent). Will do some further analysis.
--
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
