db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4571) Memory leak on server when using "SET ROLE" command
Date Thu, 25 Feb 2010 21:34:27 GMT

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

Kristian Waagan commented on DERBY-4571:

Hi Roman,

Do you happen to have a stack trace from the OOME?
I know stack traces of OOMEs may be a red herring (due to concurrency / multithreading), but
if you're consistently seeing OOMEs in the same spot of of the code it may be a good start
for debugging.

Also, are you sure you're loosing previously committed data?
If so, do you know if you're running with the disk cache enabled or not?


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