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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2010/03/01 15:31:05 UTC

[jira] Updated: (DERBY-4571) Memory leak on server when using "SET ROLE" command

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

Knut Anders Hatlen updated DERBY-4571:
--------------------------------------

    Attachment: test.diff

Attaching patch test.diff which contains a regression test case for this bug. When it's run as part of the junit-lowmem suite, it fails with OOME without the fix and passes with the fix.

> 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: 10.5.1.1, 10.5.3.0
>         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, 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.