From: <leg...@at...> - 2003-09-12 16:21:28
|
The following comment has been added to this issue: Author: Gavin King Created: Fri, 12 Sep 2003 11:20 AM Body: Which contain _what_? "instrumented classes"?? Are you talking about CGLIB cache of generated classes? something else? --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-327 Summary: memory leak Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Bostjan Dolenc Created: Fri, 12 Sep 2003 10:42 AM Updated: Fri, 12 Sep 2003 10:42 AM Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03) Description: Symptoms: Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy. I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released. Application: J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
From: <leg...@at...> - 2003-09-12 16:31:28
|
The following comment has been added to this issue: Author: Bostjan Dolenc Created: Fri, 12 Sep 2003 11:30 AM Body: Yep, CGLIB classes. I'll try to post some text from OptimizeIt on Monday. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-327 Summary: memory leak Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Bostjan Dolenc Created: Fri, 12 Sep 2003 10:42 AM Updated: Fri, 12 Sep 2003 10:42 AM Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03) Description: Symptoms: Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy. I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released. Application: J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
From: <leg...@at...> - 2004-02-02 13:42:59
|
The following comment has been added to this issue: Author: Juozas Baliuka Created: Mon, 2 Feb 2004 7:42 AM Body: Cglib holds weak reference on class loader, but I will review cache implementation and I will try to test it. BTW are you sure class garbage collector is enabled on your JVM ( -Xnoclassgc disables it on SUNs JVM ) ? --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-327 Summary: memory leak Type: Bug Status: Closed Priority: Critical Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Bostjan Dolenc Created: Fri, 12 Sep 2003 10:42 AM Updated: Mon, 2 Feb 2004 7:42 AM Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03) Description: Symptoms: Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy. I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released. Application: J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
From: <leg...@at...> - 2004-02-02 14:01:54
|
The following comment has been added to this issue: Author: Bostjan Dolenc Created: Mon, 2 Feb 2004 8:01 AM Body: I am sure class garbage collection is enabled. I submitted this issue to WebLogic support and we couldn't reach any definite conclusions. Part of the problem was that I couldn't make a (100% reproducible) test case using Hibernate. The test case that was "deterministic" enough was traced to RMI garbage collector. It fires up every 4 minutes, so frequest application redeploys (which are often during development) can produce quite large peak memory usages. Anyway, with 2.1 final (and some cache size changes in our app) we are not getting OutOfMemoryException anymore... --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-327 Summary: memory leak Type: Bug Status: Closed Priority: Critical Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Bostjan Dolenc Created: Fri, 12 Sep 2003 10:42 AM Updated: Mon, 2 Feb 2004 8:01 AM Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03) Description: Symptoms: Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy. I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released. Application: J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |