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 "Manjula Kutty (JIRA)" <de...@db.apache.org> on 2006/08/15 01:28:13 UTC
[jira] Created: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
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
Affects Versions: 10.2.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
Priority: Minor
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
[jira] Updated: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Kristian Waagan updated DERBY-1693:
-----------------------------------
Fix Version/s: 10.2.1.8
Merged to 10.2 branch with revision 477699 and the following merge command:
svn merge -r 475816:475817 https://svn.apache.org/repos/asf/db/derby/code/trunk
Ran derbyall with no failures.
> 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
> Fix For: 10.3.0.0, 10.2.1.8
>
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12450381 ]
Knut Anders Hatlen commented on DERBY-1693:
-------------------------------------------
The patch looks good. +1 to commit.
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12428186 ]
Manjula Kutty commented on DERBY-1693:
--------------------------------------
My question is what should log statement text do. The easiest is just not print values for the blob/clob. Is
that ok?
I have more prefrence to not to print the values for the blob /clob. This will solve 2 problems:
1. The out of memory error
2. the derby.log will become more cleaner (without those binary values for the blob)
> 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
> Affects Versions: 10.2.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
> Priority: Minor
>
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-1693:
----------------------------------
Fix Version/s: 10.1.3.2
> Out of Memory Error with derby.language.logStatementText=true
> -------------------------------------------------------------
>
> Key: DERBY-1693
> URL: https://issues.apache.org/jira/browse/DERBY-1693
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.6, 10.3.1.4
> 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
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.1.3.2, 10.2.2.0, 10.3.1.4
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Mike Matrigali updated DERBY-1693:
----------------------------------
I agree, my guess is that we are trying to print out the whole blob/clob in the log statement text. This is
very unlikely what the user wants. And in the current architecture anytime you try to do 2 different things
with streamed blob/clob then the blob/clob is going to get instantiated in memory. So for instance on
an insert we can stream the blob to the store, but if we need to print it to the log first we are going to call
toString and end up with it in memory (of course you could stream to disk and back but doesn't seem
worth it for logstatement text).
My question is what should log statement text do. The easiest is just not print values for the blob/clob. Is
that ok?
> 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
> Affects Versions: 10.2.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
> Priority: Minor
>
> 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
[jira] Closed: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-1693.
----------------------------------
No further work expected, and no problems reported.
> 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
> Fix For: 10.2.2.0, 10.3.0.0
>
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12428074 ]
Kristian Waagan commented on DERBY-1693:
----------------------------------------
I think I have seen the same issue earlier.
My mind might be playing a trick on me, but I mean to remember the problem was that the statement text logging mechanism tries to log the contents of LOBs. Based on my testing, insertion of a 10 MB clob fails without tracing (this will change when some fixes get in), which may support the observation that insertion of a 5 MB clob fails if its content is cloned when being logged.
> 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
> Affects Versions: 10.2.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
> Priority: Minor
>
> 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
[jira] Assigned: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Kristian Waagan reassigned DERBY-1693:
--------------------------------------
Assignee: Kristian Waagan
Having looked a little bit at this, I suggest adding (yet) another method to the DataValueDescriptor interface, say getTraceString().
The reason for this, is that today the method getString() is used to obtain the text logged to derby.log when derby.language.logStatementText is set to true. At the same time, this call is also used for getting the values of data types to do other operations. If getString() is changed to return a representation of the data that is only suitable for tracing, Derby will stop working. NetBeans counted 207 usages of the method.
I tried changing getString(), and when executing a simple insert with a prepared statement, Derby went down miserably with a stack overflow error.
I also tried adding the suggested getTraceString(), and things seemd to work (no LOB contents in derby.log and the test succeded).
I think we can get away with a general implementation of getTraceString() that forwards to getString() in DataType and then write specific implementations for the types that require this (Clob and Blob).
Have I overlooked something, or will this approach cause trouble?
If I don't get pushback, I will create a patch for the suggested approach.
> 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
> Affects Versions: 10.2.1.6
> 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
>
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12428183 ]
Kristian Waagan commented on DERBY-1693:
----------------------------------------
When a very similar problem was fixed in the network server code, I think the length of the LOB was included.
Maybe something like 'BLOB(2048)'. This looks useful to me, but we may not always know the length (for instance when a BLOB with an associated stream is used as input). For these, I guess marking the length as unknown is okay.
> 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
> Affects Versions: 10.2.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
> Priority: Minor
>
> 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
[jira] Resolved: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Kristian Waagan resolved DERBY-1693.
------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed 'derby-1693-1a.diff' to trunk with revision 475817.
I also plan to merge this fix into the 10.2 branch.
> 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
> Fix For: 10.3.0.0
>
> 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
[jira] Updated: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Kristian Waagan updated DERBY-1693:
-----------------------------------
Attachment: derby-1693-1a.diff
Attaching the patch ('derby-1693-1a.diff')...
Someone with Jira super-powers can delete the class file if they want to.
Patch ready for review.
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12429382 ]
Kristian Waagan commented on DERBY-1693:
----------------------------------------
I agree that the values for LOBs should not be printed.
The question is what should be printed instead?
I would go for either 'BLOB'/'CLOB' or 'BLOB(<length>)'/'CLOB(<length>)'.
I fancy the latter the most, but I do not fully understand the complications of obtaining the length wrt "length less LOBs". For instance, materializing it to determine the length is unacceptable in my opinion.
> 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
> Affects Versions: 10.2.1.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
> Priority: Minor
>
> 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
[jira] Commented: (DERBY-1693) Out of Memory Error with
derby.language.logStatementText=true
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12450460 ]
Kristian Waagan commented on DERBY-1693:
----------------------------------------
Forgot to say that I ran derbyall and suites.All without failures (except for CompatibilityTest, which I believe has been fixed by now).
> 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
> Fix For: 10.3.0.0
>
> 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