db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3497) OOME at slave during replication
Date Fri, 07 Mar 2008 13:35:47 GMT

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

Øystein Grøvlen updated DERBY-3497:

    Derby Info:   (was: [Patch Available])

Thanks, for fixing this Jørgen.
Patch committed as revision 634658.

> 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:
>         Environment: trunk at revision 633807
>            Reporter: Øystein Grøvlen
>            Assignee: Jørgen Løland
>         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.

View raw message