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 "Øystein Grøvlen (JIRA)" <ji...@apache.org> on 2008/04/11 14:33:06 UTC

[jira] Closed: (DERBY-3497) OOME at slave during replication

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

Øystein Grøvlen closed DERBY-3497.
----------------------------------


> OOME at slave during replication
> --------------------------------
>
>                 Key: DERBY-3497
>                 URL: https://issues.apache.org/jira/browse/DERBY-3497
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>         Environment: trunk at revision 633807
>            Reporter: Øystein Grøvlen
>            Assignee: Jørgen Løland
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3497-1a.diff, derby-3497-1a.stat
>
>
> After deleting and inserting more than 1 million records during replication, I got 
> java.lang.OutOfMemoryError: Java heap space.
> The heap dump shows that almost the entire heap is byte arrays, and it seems most of them are referred to by ReplicationMessage objects.  An inspection of the heap dump in VisualVM it seems that it is references rooted in SocketConnection#objInputStream that keeps them from being garbage collected.

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