db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed
Date Wed, 16 Jan 2008 14:34:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559516#action_12559516
] 

Jørgen Løland commented on DERBY-3316:
--------------------------------------

r612262 | kmarsden | 2008-01-15 23:36:38 +0100 (Tue, 15 Jan 2008) | 5 lines

Could this commit have made org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest
fail:

>From suites all:

There was 1 failure:
1) derbyStress(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJa vaTest)junit.framework.ComparisonFailure:
Output at line 6 expected:<Test derbyS tress finished.> but was:<FAIL -- unexpected
exception ****************>
        at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon (CanonTestCase.java:100)
        at org.apache.derbyTesting.functionTests.util.HarnessJavaTest.runTest(Ha rnessJavaTest.java:91)
        at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 96)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
        at junit.extensions.TestSetup.run(TestSetup.java:23)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
        at junit.extensions.TestSetup.run(TestSetup.java:23)
        at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57 )
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
        at junit.extensions.TestSetup.run(TestSetup.java:23)
        at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57 )


> Leak in client if ResultSet not closed
> --------------------------------------
>
>                 Key: DERBY-3316
>                 URL: https://issues.apache.org/jira/browse/DERBY-3316
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.2.1.6, 10.3.2.1, 10.4.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>             Fix For: 10.3.2.2, 10.4.0.0
>
>         Attachments: derby-3316_diff.txt, derby-3316_diff2.txt, RepeatStatement.java
>
>
> If I run the attached program RepeatStatement.java with 32M of heap,
> I will get an OutOfMemory error in the client.
> java -Xmx32M RepeatStatement
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>        at org.apache.derby.client.am.Cursor.allocateCharBuffer(Cursor.java:1260)
>        at org.apache.derby.client.net.NetStatementReply.parseSQLDTARDarray(NetStatementReply.java:1356)
>        at org.apache.derby.client.net.NetStatementReply.parseQRYDSC(NetStatementReply.java:1207)
>        at org.apache.derby.client.net.NetStatementReply.parseOpenQuery(NetStatementReply.java:479)
>        at org.apache.derby.client.net.NetStatementReply.parseOPNQRYreply(NetStatementReply.java:223)
>        at org.apache.derby.client.net.NetStatementReply.readOpenQuery(NetStatementReply.java:64)
>        at org.apache.derby.client.net.StatementReply.readOpenQuery(StatementReply.java:50)
>        at org.apache.derby.client.net.NetStatement.readOpenQuery_(NetStatement.java:153)
>        at org.apache.derby.client.am.Statement.readOpenQuery(Statement.java:1396)
>        at org.apache.derby.client.am.Statement.flowExecute(Statement.java:2001)
>        at org.apache.derby.client.am.Statement.executeQueryX(Statement.java:421)
>        at org.apache.derby.client.am.Statement.executeQuery(Statement.java:406)
>        at RepeatStatement.testInsertAndSelect(RepeatStatement.java:31)
>        at RepeatStatement.main(RepeatStatement.java:10)
> If I close the ResultSet or Statement it does not leak. 
> This occurs on trunk and 10.2.1.6. It does however not run out of memory on 10.1.3.1,
so appears to be a regression.

-- 
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