db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3245) 'java.lang.OutOfMemoryError: Java heap space' on 'SELECT count(*) FROM BID' at end of Large Datavolume test ATCJ4
Date Mon, 03 Dec 2007 13:46:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547843
] 

Knut Anders Hatlen commented on DERBY-3245:
-------------------------------------------

Sounds like you've been bitten by DERBY-3130.

> 'java.lang.OutOfMemoryError: Java heap space' on 'SELECT count(*) FROM BID' at end of
Large Datavolume test ATCJ4
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3245
>                 URL: https://issues.apache.org/jira/browse/DERBY-3245
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.2.1
>         Environment: HW: 2 X i86pc i386 (AMD Opteron(tm) Processor 250): 2393 MHz, unknown
cache.  2048 Megabytes Total Memory.
> OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. - Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode)
>            Reporter: Ole Solberg
>
> 'SELECT count(*) FROM <ATCJ4 DOTS table>' is successfully done as the first queries
done during the ATCJ4 test with the following results:
> BID: 8381213, ITEM: 301200035, REGISTRY: 232480000.
> After running the test for 48 hrs 'SELECT count(*) FROM BID' fails with java.lang.OutOfMemoryError:
Java heap space.
> This test has been succesfully run on earlier releases including 10.3.1.4, and weekly
on trunk(with even larger tables).
> The server was started as 'java -client org.apache.derby.drda.NetworkServerControl start
-h 0.0.0.0 -p 1570 -noSecurityManager'.
> On 10.3.1.4, and on trunk before 2007-08-28, the server was started *without* the '-client'
option, i.e. using "ServerVM" defaults on a 2CPU/2GB machine.
> Apache Derby Network Server - 10.3.2.1 - (599110) started and ready to accept connections
on port 1570 at 2007-11-30 17:42:09.471 GMT 
> ----------------------------------------------------------------
> 2007-11-30 17:43:40.055 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby - 10.3.2.1 - (599110):
instance c013800d-0116-91a6-b2d9-0000003ace00
> on database directory /export/raid/tmp/os136789/DOTS/10.1.2.4/TESTDB  
> Database Class Loader started - derby.database.classpath=''
> 2007-12-02 18:23:57.881 GMT Thread[DRDAConnThread_42,5,main] (XID = 251526879), (SESSIONID
= 44), (DATABASE = /export/raid/tmp/os136789/DOTS/10.1.2.4/TESTDB), (DRDAID = O19F76D5.CF38-866941731649016324{45}),
Cleanup action starting
> 2007-12-02 18:23:58.159 GMT Thread[DRDAConnThread_42,5,main] (XID = 251526879), (SESSIONID
= 44), (DATABASE = /export/raid/tmp/os136789/DOTS/10.1.2.4/TESTDB), (DRDAID = O19F76D5.CF38-866941731649016324{45}),
Failed Statement is: SELECT count(*) FROM BID
> java.lang.OutOfMemoryError: Java heap space
> 	at org.apache.derby.impl.store.raw.data.BaseContainerHandle.makeRecordHandle(Unknown
Source)
> 	at org.apache.derby.impl.store.access.heap.HeapRowLocation.getRecordHandle(Unknown Source)
> 	at org.apache.derby.impl.store.access.heap.HeapController.lockRow(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.index.B2IRowLocking3.lockRowOnPage(Unknown
Source)
> 	at org.apache.derby.impl.store.access.btree.index.B2IRowLocking3._lockScanRow(Unknown
Source)
> 	at org.apache.derby.impl.store.access.btree.index.B2IRowLockingRR.lockScanRow(Unknown
Source)
> 	at org.apache.derby.impl.store.access.btree.BTreeForwardScan.fetchRows(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.BTreeScan.fetchNextGroup(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.reloadArray(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.getNextRowCore(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown
Source)
> 	at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getRowFromResultSet(Unknown
Source)
> 	at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getNextRowCore(Unknown
Source)
> 	at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown
Source)
> 	at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.getNextRow(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> 2007-12-02 18:24:04.180 GMT Thread[DRDAConnThread_42,5,main] (XID = 251526879), (SESSIONID
= 44), (DATABASE = /export/raid/tmp/os136789/DOTS/10.1.2.4/TESTDB), (DRDAID = O19F76D5.CF38-866941731649016324{45}),
Cleanup action starting
> 2007-12-02 18:24:04.458 GMT Thread[DRDAConnThread_42,5,main] (XID = 251526879), (SESSIONID
= 44), (DATABASE = /export/raid/tmp/os136789/DOTS/10.1.2.4/TESTDB), (DRDAID = O19F76D5.CF38-866941731649016324{45}),
Failed Statement is: SELECT count(*) FROM BID
> java.lang.OutOfMemoryError: Java heap space
> I will rerun the test *without* the '-client' option, i.e. with the same settings as
used on earlier release tests.
> This test run should be finished in 48 hrs. i.e. 2007-12-05.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message