[
https://issues.apache.org/jira/browse/DERBY-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839285#action_12839285
]
Knut Anders Hatlen commented on DERBY-4571:
-------------------------------------------
Thanks, I'm able to reproduce the OOME now.
I'm wondering, could this be because we have made activations dependent on the
current role and the dependency table keeps references to activations even
after they're no longer in use?
> 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
> Attachments: D4571.java, DbRoleMemoryLeak.java, memRole.sql,
> memRole.sql
>
>
> 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.
