db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Khettry (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-912) OutOfMemory error on continuous execution of SQL statement
Date Tue, 21 Feb 2006 18:19:16 GMT
    [ http://issues.apache.org/jira/browse/DERBY-912?page=comments#action_12367238 ] 

Manish Khettry commented on DERBY-912:
--------------------------------------

Yes, it is from the original test program. BTW, I added a conn.commit() to the original program--
so it basically looks like this:

while (true)
{
  ps = conn.prepareStatement(sql);
  rs = ps.executeQuery();
  // read from rs.
  conn.commit();
  // close rs, ps
}

and it still runs out of memory. Shouldn't doing a commit create a new transaction?

> OutOfMemory error on continuous execution of SQL statement
> ----------------------------------------------------------
>
>          Key: DERBY-912
>          URL: http://issues.apache.org/jira/browse/DERBY-912
>      Project: Derby
>         Type: Sub-task
>   Components: Store
>     Versions: 10.0.2.0
>  Environment: cygwin, jdk 1.4
>     Reporter: Manish Khettry

>
> After fixing the original memory leak, I still run into problems on repeated execution
of a sql statement. Take the sample program in the bug and run it with a small heap size (4m).
After around 80-90K executions an outofmemory error is thrown. I took snapshots of the heap
while the program was running but couldn't find anything obviously wrong. 

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


Mime
View raw message