[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2344: --- Assignee: (was: Ole Solberg) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Components: Network Server, Regression Test Failure, Services Affects Versions: 10.3.1.4 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Attachments: 13.zip, 14.zip, memory.png, memory.txt, memory_507152.txt, MemRunner.java, memusage.png, VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2344: -- Derby Info: (was: [Regression]) Unchecking Regession checkbox as this is not a confirmed product regression 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Components: Network Server, Regression Test Failure, Services Affects Versions: 10.3.1.4 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Assignee: Ole Solberg Attachments: 13.zip, 14.zip, memory.png, memory.txt, memory_507152.txt, MemRunner.java, memusage.png, VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2344: -- Component/s: Services Regression Test Failure 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Components: Network Server, Regression Test Failure, Services Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Assigned To: Ole Solberg Attachments: 13.zip, 14.zip, memory.png, memory.txt, memory_507152.txt, MemRunner.java, memusage.png, VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2344: -- Attachment: memory.png memory.txt MemRunner.java I'm not sure if it's of any help, but MemRunner.java (attached) is a test runner which runs System.gc() and System.runFinalization() twice after each test case and reports memory usage. memory.txt shows the log after a run on trunk with JDK 6 started with -server -Xmx1024m. memory.png shows memory usage after each test case. The memory usage is highest when running BlobClob4BlobTest (~100M after testPositionAgressive), but it drops when the test has finished so I don't that's where the leak is. 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Assigned To: Ole Solberg Attachments: 13.zip, 14.zip, memory.png, memory.txt, MemRunner.java, VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2344: -- Attachment: memusage.png memory_507152.txt I have run MemRunner against an older revision of trunk (507152). The log is attached as memory_507152.txt. memusage.png compares the memory usage for the old revision and the newer one. The profiles are almost identical, except that the memory usage for the newest revision increases more in the beginning. The increased memory usage seems to be caused by these two tests: 1) TriggerTest was added between these revisions and caused a jump from ~33 MB to ~48 MB, and the extra memory is not freed when the test has finished. 2) LangHarnessJavaTest was added between these revision and caused a jump from ~55 MB to ~69 MB, and the extra memory is not freed. 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Assigned To: Ole Solberg Attachments: 13.zip, 14.zip, memory.png, memory.txt, memory_507152.txt, MemRunner.java, memusage.png, VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . --
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2344: --- Attachment: 14.zip 13.zip I finally managed to get the OOME/heap space again. Several test runs in the same environement during this weekend did not fail! In this case I find in derby.log: 2007-02-19 13:29:29.951 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.3.0.0 alpha - (508917:509179M): instance af14467b-0110-da15-245a-aad2107f on database directory /export/home/tmp/os136789/testingInMyDerbySandbox/adHoc/system/wombat Database Class Loader started - derby.database.classpath='' 2007-02-19 13:29:50.705 GMT Thread[main,5,main] (XID = 109524), (SESSIONID = 4), (DATABASE = wombat), (DRDAID = null), Cleanup action starting 2007-02-19 13:29:50.705 GMT Thread[main,5,main] (XID = 109524), (SESSIONID = 4), (DATABASE = wombat), (DRDAID = null), Failed Statement is: insert into testClobTriggerB(a, b) select n.a, n.b from new org.apache.derby.catalog.TriggerNewTransitionRows() N java.lang.OutOfMemoryError: Java heap space at org.apache.derby.iapi.services.io.DynamicByteArrayOutputStream.init(Unknown Source) at org.apache.derby.impl.store.raw.data.BasePage.insertAllowOverflow(Unknown Source) at org.apache.derby.impl.store.raw.data.BasePage.insert(Unknown Source) at org.apache.derby.impl.store.access.heap.HeapController.doInsert(Unknown Source) at org.apache.derby.impl.store.access.heap.HeapController.insert(Unknown Source) at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.sql.execute.GenericTriggerExecutor.executeSPS(Unknown Source) at org.apache.derby.impl.sql.execute.StatementTriggerExecutor.fireTrigger(Unknown Source) at org.apache.derby.impl.sql.execute.TriggerEventActivator.notifyEvent(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.sql.execute.GenericTriggerExecutor.executeSPS(Unknown Source) at org.apache.derby.impl.sql.execute.RowTriggerExecutor.fireTrigger(Unknown Source) at org.apache.derby.impl.sql.execute.TriggerEventActivator.notifyEvent(Unknown Source) at org.apache.derby.impl.sql.execute.UpdateResultSet.fireAfterTriggers(Unknown Source) at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.testTriggersWithClobColumn(BlobClob4BlobTest.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:80) Cleanup action completed 2007-02-19 13:31:07.974 GMT Thread[main,5,main] (XID = 113695), (SESSIONID = 31), (DATABASE = wombat), (DRDAID = null), Cleanup action starting 2007-02-19 13:31:07.974 GMT Thread[main,5,main] (XID = 113695), (SESSIONID = 31), (DATABASE = wombat), (DRDAID = null), Failed Statement is: UPDATE testBlob set b = b + 0 java.lang.OutOfMemoryError: Java heap space Cleanup action completed Apache Derby Network Server - 10.3.0.0 alpha - (508917:509179M) started and ready to accept connections on port 1527 at 2007-02-19 13:31:47.960 GMT Does Cleanup action completed indicate that this is an exception handled by the server, or is this a real failure? These tests are run with svn 508917 on OS: Fedora Core release 4 (Stentz) 32bits - Linux 2.6.17-1.2142_FC4 #1 Tue Jul 11 22:41:14 EDT 2006 GNU/Linux HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2669.734 MHz, 512 KB cache.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2344: --- Attachment: VM_Summary.jpg VM_Summary-1.txt Attaching VM Summary and Overview from a JConsole session of a failing test run. 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Attachments: VM_Summary-1.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2344: --- Attachment: VM_Summary-serverJvm-PS_Old_Gen.jpg VM_Summary-serverJvm.jpg VM_Summary-serverJvm.txt Attached JConsole output for a run where serverJvm settings are chosen. This shows that mem usage is growing throughout the suites.All run. Observer that the VM_Summary. attachements use Jvm 1.6. 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Attachments: VM_Summary-1.txt, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) . . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2344) 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread
[ https://issues.apache.org/jira/browse/DERBY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2344: --- Attachment: VM_Summary-J507152DK14Jvm15-clientjvm.jpg VM_Summary-507428JDK14Jvm15-clientjvm.jpg VM_Summary-507428JDK6Jvm6-clientjvm.jpg Some observations: VM_Summary-J507152DK14Jvm15-clientjvm.jpg, where no errors problems were reported shows a significant drop in mem usage after ~25 minutes. VM_Summary-507428JDK14Jvm15-clientjvm.jpg, which reported one failure: 1) testPositionAgressive(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)java.lang.OutOfMemoryError: Java heap space shows steadily increasing mem usage where 507152 has a drop. VM_Summary-507428JDK6Jvm6-clientjvm.jpg, includes JDBC4 tests and fills memory even faster. It seems like - either the setUp/tearDown for the JUnit tests do not release memory taken per test run, - or may be test cases themselves do not release/close resources? 'java.lang.OutOfMemoryError: Java heap space' in NetworkServerThread Key: DERBY-2344 URL: https://issues.apache.org/jira/browse/DERBY-2344 Project: Derby Issue Type: Bug Affects Versions: 10.3.0.0 Environment: JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Fedora Core release 5 (Bordeaux) 32bits - Linux 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 HW: 1 X Intel(R) Pentium(R) 4 CPU 2.66GHz: 2656.261 MHz, 512 KB cache. 773284 kB Total Memory. JVM: Sun Microsystems Inc. 1.5.0_06-b04 OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27 HW: 1 X x86 AuthenticAMD family 15 model 36 step 2 (AMD Turion(tm) 64 Mobile Technology ML-37): 2000 MHz, unknown cache. 1023 Megabytes Total Memory JVM: Sun Microsystems Inc. - 1.5.0_05-b05 OS: Microsoft Windows XP Professional - 5.1.2600 Service Pack 2 Build 2600 - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin HW: 1 X Ferrari 4000 x86 Family 15 Model 36 Stepping 2 AuthenticAMD: ~2000 MHz, 2,048 MB cache. 1,022 Total Memory. Reporter: Ole Solberg Attachments: VM_Summary-1.txt, VM_Summary-507428JDK14Jvm15-clientjvm.jpg, VM_Summary-507428JDK6Jvm6-clientjvm.jpg, VM_Summary-J507152DK14Jvm15-clientjvm.jpg, VM_Summary-serverJvm-PS_Old_Gen.jpg, VM_Summary-serverJvm.jpg, VM_Summary-serverJvm.txt, VM_Summary.jpg I see this only on test machines with 1Gb of memory or less. Our lab-machines with 2Gb mem show now problems. See http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-508068.html Extract from a typical thread dump: main prio=1 tid=0x09e2a760 nid=0xef6 runnable [0xbfd89000..0xbfd8a418] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.derby.client.net.Reply.fill(Unknown Source) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source) at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source) at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source) at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source) at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source) at org.apache.derby.client.net.NetConnection.init(Unknown Source) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source) at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) - locked 0x8cda8a18 (a java.lang.Class) at java.sql.DriverManager.getConnection(DriverManager.java:171) - locked 0x8cda8a18 (a java.lang.Class) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:76) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:764) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:205) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:90) at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.setUp(BlobClob4BlobTest.java:56) at junit.framework.TestCase.runBare(TestCase.java:128) .
