You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2006/11/01 02:53:39 UTC
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12446145 ]
Bryan Pendleton commented on DERBY-1693:
----------------------------------------
I downloaded the patch and applied it. I was able to run the ReproDerby1693 program,
and I can see in the derby.log that the logged statement text is just as I expected: only
a token for the large object's stream is logged, not the large object itself.
> Out of Memory Error with derby.language.logStatementText=true
> -------------------------------------------------------------
>
> Key: DERBY-1693
> URL: http://issues.apache.org/jira/browse/DERBY-1693
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.6, 10.3.0.0
> Environment: JVM INFO :
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
> Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode)
> OS : Windows XP Professional
> Reporter: Manjula Kutty
> Assigned To: Kristian Waagan
> Priority: Minor
> Attachments: derby-1693-1a.diff, derby-1693-1a.stat, ReproDerby1693.class, ReproDerby1693.java
>
>
> While running a test with blobs and clobs of random size but not exceeding more than 5MB , with derby.language.logStatementText=true , The inserts are faling with out of memory error. Once that error occurs then the test loses all connections to the database. If I take off the derby.language.logStatementText=true property from derby.properties, the test runs fine. Here is the stack Trace
> java.lang.OutOfMemoryError: Java heap space
> ---SQLException Caught---
> SQLState: XJ001
> Severity: 0
> Message: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
> java.lang.OutOfMemoryError: Java heap space
> java.sql.SQLException: No current connection.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExc
> eptionFactory.java:45)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:89)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:105)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Util.java:209)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(EmbedConnect
> ion.java:1351)
> at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(EmbedCon
> nection.java:1529)
> at org.apache.derby.impl.jdbc.EmbedConnection.rollback(EmbedConnection.j
> ava:946)
> at com.ibm.db2j.tests.scenario.utils.DbTasks.insertMail(DbTasks.java:400
> )
> at com.ibm.db2j.tests.scenario.tasks.Refresh.insertMail(Refresh.java:62)
> at com.ibm.db2j.tests.scenario.tasks.Refresh.doWork(Refresh.java:43)
> at com.ibm.db2j.tests.scenario.tasks.Refresh.run(Refresh.java:21)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira