[DERBY-1693] Out of Memory Error with derby.language.logStatementText=true

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.1.3.2, 10.2.2.0, 10.3.1.4
• Component/s: SQL
• 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
• Urgency: Normal
• Assignee: Kristian Waagan
• Reporter: Manjula Kutty
• Created: 14/Aug/06 23:27
• Updated: 19/Oct/07 16:11
• Resolved: 16/Nov/06 17:08

Description

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)

Issue Links

• duplicates: DERBY-598 Ensure that with derby.language.logStatementText.true, values set by streams are not materialized