I'll get that to you on Monday
> On 30 Mar 2014, at 12:59, "Mark Proctor [via Drools]"
> <ml-node+s46999n4029026...@n3.nabble.com> wrote:
>
> Are you able to isolate what the FH’s are referencing, that might give us an
> idea of where to look. If you look RightTuple’s they will have a ‘sink'
> reference (network node) and that sink will have an ‘associates’ map. That
> map is the rules that node is part of. You can use this to identify the
> offending rule(s), and maybe paste those rules here?
>
> Mark
>> On 30 Mar 2014, at 09:03, kellyajp <[hidden email]> wrote:
>>
>> Thanks
>>
>> I'll get someone from the team to work on this on Monday. Not sure how easy
>> it will be to isolate but will keep you informed.
>>
>> Andy
>>> On 28 Mar 2014, at 23:52, "Mark Proctor [via Drools]" <<a
>>> href="x-msg://131/user/SendEmail.jtp?type=node&node=4029025&i=0"
>>> target="_top" rel="nofollow" link="external">[hidden email]> wrote:
>>>
>>> Can you get us a unit test demonstrating this, and we’ll look into it as a
>>> priority.
>>>
>>> Mark
>>> On 28 Mar 2014, at 15:40, kellyajp <<a
>>> href="x-msg://131/user/SendEmail.jtp?type=node&node=4029018&i=0"
>>> target="_top" rel="nofollow" link="external">[hidden email]> wrote:
>>>
>>> > We have upgraded from Drools 5 -> Drools 6.01 and when repeating the
>>> > processing in each environment we have very different object counts that
>>> > is
>>> > causing memory to run out on Drools 6:
>>> >
>>> > Below is an extract from a heap dump
>>> >
>>> > In Drools 6 the main objects in the heap are
>>> > 1: 4378006 700480960 org.drools.core.reteoo.RightTuple
>>> >
>>> > Where as in Drools 5 there are way less objects
>>> > 92: 19022 1826112 org.drools.reteoo.RightTuple
>>> >
>>> > Has anyone else had any experience of this issue?
>>> >
>>> > Thanks
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context:
>>> > http://drools.46999.n3.nabble.com/Possible-memory-leak-in-Drools-6-0-1-tp4029010.html
>>> > Sent from the Drools: Developer (committer) mailing list mailing list
>>> > archive at Nabble.com.
>>> > _______________________________________________
>>> > rules-dev mailing list
>>> > <a
>>> > href="x-msg://131/user/SendEmail.jtp?type=node&node=4029018&i=1"
>>> > target="_top" rel="nofollow" link="external">[hidden email]
>>> > https://lists.jboss.org/mailman/listinfo/rules-dev
>>> _______________________________________________
>>> rules-dev mailing list
>>> <a href="x-msg://131/user/SendEmail.jtp?type=node&node=4029018&i=2"
>>> target="_top" rel="nofollow" link="external">[hidden email]
>>> https://lists.jboss.org/mailman/listinfo/rules-dev
>>>
>>>
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://drools.46999.n3.nabble.com/Possible-memory-leak-in-Drools-6-0-1-tp4029010p4029018.html
>>> To unsubscribe from Possible memory leak in Drools 6.0.1, click here.
>>> NAML
>>
>> View this message in context: Re: Possible memory leak in Drools 6.0.1
>> Sent from the Drools: Developer (committer) mailing list mailing list
>> archive at Nabble.com.
>> _______________________________________________
>> rules-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> _______________________________________________
> rules-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://drools.46999.n3.nabble.com/Possible-memory-leak-in-Drools-6-0-1-tp4029010p4029026.html
> To unsubscribe from Possible memory leak in Drools 6.0.1, click here.
> NAML
--
View this message in context:
http://drools.46999.n3.nabble.com/Possible-memory-leak-in-Drools-6-0-1-tp4029010p4029027.html
Sent from the Drools: Developer (committer) mailing list mailing list archive
at Nabble.com.
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
