db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-3497) OOME at slave during replication
Date Thu, 06 Mar 2008 14:58:58 GMT

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

jorgenlo edited comment on DERBY-3497 at 3/6/08 6:58 AM:
--------------------------------------------------------------

All tests except those that fail in tinderbox (predicatePushdown.sql, TransactionTable.sql)
passed on patch 1a

      was (Author: jorgenlo):
    All tests passed on patch 1a
  
> 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
>         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.


Mime
View raw message