[ http://issues.apache.org/jira/browse/DERBY-676?page=comments#action_12356674 ]
Bryan Pendleton commented on DERBY-676:
---------------------------------------
Perhaps I'm not understanding your program very well, but it seems like you are creating a
statement in JdbcTask.executeQuery, but I don't see where you close that statement. So it
seems like each time you call executeQuery, you are leaking a Statement object.
> OutOfMemoryError in Network Server while performing operations using one of the two Statement
objects created from a Connection object
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-676
> URL: http://issues.apache.org/jira/browse/DERBY-676
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.0.2.1, 10.1.1.0, 10.2.0.0, 10.1.1.1
> Environment: Windows 2000
> Reporter: Rajesh Kartha
> Attachments: JdbcTask.java, ReproTest.java
>
> The NetworkServer throws an OutOfMemoryError if there exists two Statement objects from
a Connection object, but only one of them is being actively used
> for insert/select operations. I noticed 100% CPU usage and the memory usage of Network
Server JVM steadily growing, so suspect a memory leak.
> The attached test reproduces it. With the default setting of maz heap size the Exception
ocurs in about 12-15 mins during the 'select' operation. By setting the max heap size -Xmx
for the Network Server JVM to a smaller value the error happnes much earlier.
> The test is very simple and uses plain Statement objects, which get closed after every
insert/select. I tried the same test in the Embedded mode and did not see any errors.
--
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
|