[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995426#comment-16995426 ] THEODOROS CHAIKALIS commented on DELTASPIKE-1398: - Thank you! Do you have any plans in the near future about deploying 1.9.2 to maven repo? > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Assignee: Thomas Andraschko >Priority: Blocker > Fix For: 1.9.2 > > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994604#comment-16994604 ] Thomas Andraschko commented on DELTASPIKE-1398: --- The bug is the following: When we add the BM, we add a cache entry for the current CL and the parent CL. But when we cleanup, we don't remove the parentCL entry. It was introduced by: https://github.com/apache/deltaspike/commit/35883fbd0d1a1c3dfc9023d67d4c5449e97fe6c2#diff-e7ec55687361a85269330f4f18cfa6d2 Nevertheless... Mark, Romain and I agreed to use CDI.current only if available and skip our caching. Then it's up to the container to provide the right BM. The whole behavior can be deactivated by: deltaspike.bean-manager.delegate_lookup = false > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Priority: Blocker > Fix For: 1.9.2 > > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994602#comment-16994602 ] ASF subversion and git services commented on DELTASPIKE-1398: - Commit 02e33e5125b995a184e7678f0938ad107e98cd2e in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=02e33e5 ] DELTASPIKE-1398 - fixed delegation and change it to more agressive use of CDI.current. This also fixes the mem leak as our caching isn't used anymore. > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Priority: Blocker > Fix For: 1.9.2 > > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992899#comment-16992899 ] Thomas Andraschko commented on DELTASPIKE-1398: --- I already consider it but don't have much time. Can you try to debug BeanManagerProvider? The logic is quite simple: BeanManagerProvider#setBeanManager should add it to bmInfos BeanManagerProvider#cleanupStoredBeanManagerOnShutdown should remove it when undeployed > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Priority: Blocker > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992877#comment-16992877 ] THEODOROS CHAIKALIS commented on DELTASPIKE-1398: - Can you please consider about resolving this problem? > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Priority: Blocker > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[ https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992727#comment-16992727 ] Thomas Andraschko commented on DELTASPIKE-1398: --- I can also replicate it in TomEE with a simple WAR. BeforeShutdown is called once (which is expected, there is only one shutdown of the application) but the cleanup doesn't work correctly. Make the ClassLoader is different > Weblogic memory leak > > > Key: DELTASPIKE-1398 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.8.0 >Reporter: THEODOROS CHAIKALIS >Priority: Blocker > Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png, > mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war, > server_small.zip > > > This extends previously reported issue 1392 > Iam returning back to a previously reported serious memory leak in Weblogic > 12.2.1-3. > To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl) > are not being garbage collected after application removal. > > Steps to reproduce: > > # deploy the attached war (server-small) > # {{open the webpage at /server-small/views/index.xhtml (mleak2)}} > # monitor the classes created with a profiler (with starting name > gr.teohaik...) (mleak1) > # delete the app > # check again the profiler. The ejbs are still there! (mleak3) > > A suggestion in 1392 was to debug BeanManagerProvider, so we did. > {{but bpmSingleton.bminfos contains 2 objects. but method }} > {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown) > }} > {{is called only once}} > Attached you can see relevant object contents in the debugger screenshots -- This message was sent by Atlassian Jira (v8.3.4#803005)