camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Assigned] (CAMEL-7635) Memory leak in Message History feature
Date Fri, 25 Jul 2014 07:23:39 GMT


Claus Ibsen reassigned CAMEL-7635:

    Assignee: Claus Ibsen

> Memory leak in Message History feature
> --------------------------------------
>                 Key: CAMEL-7635
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.13.1
>         Environment: Apache ServiceMix 5.1.0 w/ Camel 2.13.1
> JDK 7
>            Reporter: Raúl Kripalani
>            Assignee: Claus Ibsen
>         Attachments: Screen Shot 2014-07-24 at 15.32.05.png, image1.png, image2.png,
> We just had an OOM incident in our dev environments after upgrading from Camel 2.10.3
to 2.13.1. Heap settings have remained untouched.
> A heap dump showed millions of DefaultMessageHistory instances retained (see [^image1.png]),
along with their corresponding Date and StopWatch instances. Obviously our first solution
will be to disable message history in all contexts.
> Digging deeper, I'm utterly confused because I don't seem to find the GC roots that are
keeping these objects alive.
> OQL query for VisualVM:
> {code}
> select x from org.apache.camel.impl.DefaultMessageHistory x where count(referrers(x))
> 0
> {code}
> returns many objects, which is good.
> However, they are referenced by some Object[] which in turn has no referrers (!), see
> Using the "Find nearest GC root" feature yields no results either.
> This mysterious Object[] seems to be filled from position 4072 onwards (see [^image3.png]),
it has 9k+ items... Perhaps some kind of Queue? There are many more Object[] arrays storing
DefaultMessageHistory instances too.

This message was sent by Atlassian JIRA

View raw message