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] Commented: (DERBY-4571) Memory leak on server when using "SET ROLE" command
Date Mon, 01 Mar 2010 14:53:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839700#action_12839700
] 

Knut Anders Hatlen commented on DERBY-4571:
-------------------------------------------

I was a little bit worried about the performance impact of clearing the activation's dependencies
unconditionally on each execution, since clearDependencies() ends up synchronizing on a Hashtable
and on a BasicDependencyManager, both of which are shared between all threads accessing the
same database. However, running the micro-benchmark attached to DERBY-3024 in noshare mode
on a 32-way processor did not show any negative impact. I cannot think of any other test that
would be more likely to be affected by this, so unless someone has an idea for a simple way
to check whether the call to clearDependencies() is needed, I plan to go ahead with the unconditional
call to clearDependencies() from BaseActivation.close().

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


Mime
View raw message