db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4571) Memory leak on server when using "SET ROLE" command
Date Tue, 02 Mar 2010 15:46:27 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen updated DERBY-4571:

    Attachment: derby-4571-1a.stat

Attaching a new patch which includes both the fix and the test case. All the regression tests
ran cleanly with this patch.

As to my comment about performance implications above, I had forgotten that prepared statements
reuse activations, so this code will not be invoked as frequently as I thought and it should
not be an issue.

> Memory leak on server when using "SET ROLE" command
> ---------------------------------------------------
>                 Key: DERBY-4571
>                 URL: https://issues.apache.org/jira/browse/DERBY-4571
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:,
>         Environment: Windows XP, Java 6 (build doesn't matter: 10-18)
>            Reporter: Roman Musil
>            Assignee: Knut Anders Hatlen
>         Attachments: clear_deps.diff, D4571.java, DbRoleMemoryLeak.java, derby-4571-1a.diff,
derby-4571-1a.stat, memRole.sql, memRole.sql, test.diff
> Scenario:
> -connect into database
> -use command SET ROLE
> -repeat simple selects many times -> memory consumtions ends with database "outOfMemory:
heap space" crash.
> Sometimes this crash ends with loosing (of course previously commited) data in different
tables - this is in the case using "UPDATE" etc. command.
> Without command SET ROLE everythings works OK. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message