Bugs item #499117, was opened at 2002-01-03 12:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=499117&group_id=22866
Category: JBossServer Group: v2.4 BETA (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Michael Ryan (ricoryans) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss Memory Leak Initial Comment: Operating System: Solaris 8 JDK Version: java version "1.3.1_01" When employing the Minerva JDBC Local Transaction resource adaptor for connecting to the Polyhedra database, a memory leak will occur in JBoss when running the following test. Test description: We wrote a simple java client that sets a data field to a value, then to another value, and alternates forever. For this test, four copies of this client were executed simultaneously and the system resources were observed and monitored using top. We set JBoss' maximum heap size to 256m. After starting the test clients, JBoss memory usage will continue to grow until it reaches its maximum heap size and then runs out of memory after about 1.5 hours. It's important to NOTE that if you configure JBoss to instead employ the XA DataSourceLoader for Polyhedra, NO MEMORY LEAK WILL OCCUR when running the same test. ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2002-04-27 15:42 Message: Logged In: YES user_id=175228 The leaking connection listeners have been fixed for 2.4.5. ---------------------------------------------------------------------- Comment By: Lucas McGregor (lmcgregor) Date: 2002-04-17 17:24 Message: Logged In: YES user_id=516221 Sorry. I don't have access to anything like JProbe. Anything I have is speculative from adding and removing code, then watching it run with gc set to verbose. If it is a one line fix, I would be more than happy to apply the patch and then test it on my set-up to see if memory still leaks. ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2002-04-17 17:15 Message: Logged In: YES user_id=60525 Do either of you have a reasonably easy way of determining which object is leaking? We recently found a leak in the the local wrapper that took a 1-line fix, see http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbosscx/src/main/org/jboss/resource/adapter/jdbc/local/JDBCManagedConnection.java We could backport the fix if it helps. Also... a 3.0 rc1 config file for the polyhedra db would be appreciated. (What is polyhedra?) ---------------------------------------------------------------------- Comment By: Lucas McGregor (lmcgregor) Date: 2002-04-17 15:48 Message: Logged In: YES user_id=516221 I have had the same experience. I am on JBoss 2.4.4, Solaris 8 on x86, and JVM 1.3.1_01. I have tested this against MS SQL 2000 with several different JDBC drivers and HSQL. So it isn't driver specific. And I too found that the only way around this was to use the XADataSourceImpl object instead of a Minerva pool, which doesn't seem to exhibit any memory leaks. I played around with different heap and gc settings, nothing could keep Minerva running more that 4hrs for me. Memory usage would always crawl to the Heap max and JBoss would stop. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=499117&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
