i'm using drools 5.5.0, after the rules deployment, (associate DRL's with the KnowladBase and compile them) my permgen grows to 500m, and also if i undeploy, the permgen doesn't cleaned up. (only if i restart the server) It won't help me to increase the permgen size, because the client does a lot of heavy deployment, and can be in the maximum size by 3-4 deployments. I tried this tomcat flags, and it does nothing: -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC I tried set the flag : PermGenThreshold=0, like other people suggested in your forums and it doesn't help. any help? it's production issue... -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

i tried it. wasn't help. i used MAT to analyze the leak, and it points on mvel2.optimizer -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027040.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

i tried it. wasn't help. i used MAT to analyze the leak, and it points on mvel2.optimizer -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027040.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

On Dec 2, 2013, at 6:49 PM, brachi <brachi.w(a)sapiens.com&gt; wrote: i did, nothing changed. the leak still exists. -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027045.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

On Dec 2, 2013, at 7:10 PM, brachi <brachi.w(a)sapiens.com&gt; wrote: how did you changed to mvel? this property?drools.dialect.mvel.strict false or true? i think i tried it with false... -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027048.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

how did you changed to mvel? this property?drools.dialect.mvel.strict false or true? i think i tried it with false... -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027048.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

On Dec 2, 2013, at 7:41 PM, brachi <brachi.w(a)sapiens.com&gt; wrote: thanks, I used CMSClassUnloadingEnabled, but this can't help because the GC can't garbage this classes because they are in use somewhere, that is actually the leak. -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027052.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

On Dec 2, 2013, at 11:28 PM, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: At this point we are probably stuck, without a unit test that reproduces the issue. Or better still a patch fixing it. Mark > On 2 Dec 2013, at 19:41, brachi <brachi.w(a)sapiens.com&gt; wrote: > > thanks, I used CMSClassUnloadingEnabled, but this can't help because the GC > can't garbage this classes because they are in use somewhere, that is > actually the leak. > > > > -- > View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027052.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

I got a compilation error whith MVEL dialect, on string contains ";" character. "unterminated string literal" any idea? -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027111.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi, You mention that the brand new kbase evertime could be a problem and you may get this from "re-deployments". In my situation I am not in an app server and so do not have a re-deployment issue but I am creating a new kbase every time I run through the system. The system dynamically creates the drl from database definitions and this is done for each "run" of the application. Is there an alternative for this? -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027321.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

1. when will you estimate that 5.6.0.Final will published out?

2. why did you add this dispose methods on the implementation and not on the interface, I don't want to cust the builder and kbase in order to dispose, can it be?

3. It occurs also on 6.0.

-- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027530.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

I have memory leak when using java dialect that doesn't happen with mvel dialect. when change to mvel some rules that hit with java doesn't hit now.and I got compilation errors. this memory leak occurs also at 6.0. -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027534.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

see previous messages, pmander attached a unit test -- View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

I have run pmander's tests, and reported in a previous email. The leak in 5.x is due to the nature of the composite classloader, and dispose() forces the memory to be released. I don't remember if that fix was in 5.6.CR1 (probably not), so you may have to try 5.6.0-SNAPSHOT or wait for the end of the week. 6.x does not suffer from the same problem, but has a different issue - no way to unload kie modules once they are cached - which Mario has been working on. In either case, pmander's test works fine in both 5.6.x and 6.x after these fixes Davide On 01/06/2014 07:56 PM, Mark Proctor wrote: > I’ve been told 5.6 will be released this week. This is because the JCR2GIT migration tool, in 5.6 is needed for our 6.0 product. > > Davide's current kbase.dispose() method, on the concrete class, should just be considered a work around for the problem. Unless this is fixed by someone in the community, I don’t think any core developers will have time to address this. At least not for 5.x; we’ll continue to look into it for 6.x. > > Mark > > > On 6 Jan 2014, at 16:14, brachi <brachi.w(a)sapiens.com&gt; wrote: > >> see previous messages, pmander attached a unit test >> >> >> >> -- >> View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html >> Sent from the Drools: User forum mailing list archive at Nabble.com. >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-users > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

The root of the perm gen leak has now be solved, thanks to some heroic work by community developer Davide Sottara. This is just in time for the 5.6 release going out this week. You will not need to use the kbase.dispose() work around. Mark On 6 Jan 2014, at 20:50, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > The 5.6 approach should be considered a work around, not a fix. Somewhere a ref is being held, that shouldn’t be - we just haven’t found it yet. > > Mark > > On 6 Jan 2014, at 19:17, Davide Sottara <dsotty(a)gmail.com&gt; wrote: > >> I have run pmander's tests, and reported in a previous email. >> The leak in 5.x is due to the nature of the composite classloader, and >> dispose() >> forces the memory to be released. I don't remember if that fix was in >> 5.6.CR1 >> (probably not), so you may have to try 5.6.0-SNAPSHOT or wait for the >> end of the week. >> 6.x does not suffer from the same problem, but has a different issue - >> no way >> to unload kie modules once they are cached - which Mario has been >> working on. >> In either case, pmander's test works fine in both 5.6.x and 6.x after >> these fixes >> Davide >> >> On 01/06/2014 07:56 PM, Mark Proctor wrote: >>> I’ve been told 5.6 will be released this week. This is because the JCR2GIT migration tool, in 5.6 is needed for our 6.0 product. >>> >>> Davide's current kbase.dispose() method, on the concrete class, should just be considered a work around for the problem. Unless this is fixed by someone in the community, I don’t think any core developers will have time to address this. At least not for 5.x; we’ll continue to look into it for 6.x. >>> >>> Mark >>> >>> >>> On 6 Jan 2014, at 16:14, brachi <brachi.w(a)sapiens.com&gt; wrote: >>> >>>> see previous messages, pmander attached a unit test >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html >>>> Sent from the Drools: User forum mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> rules-users mailing list >>>> rules-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/rules-users >>> >>> _______________________________________________ >>> rules-users mailing list >>> rules-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/rules-users >>> >> >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-users >

Hi Mark/Davide Is there a work around to this problem in 5.4?. Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 08/01/2014 04:46 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org For anyone interested. The commit involves addressing two needs. 1) Enforcing MVEL reflection mode throughout - MVEL ASM optimiser can NEVER be used for anything (it doesn’t add much value anyway). 2) Avoiding giving the template system the root class loader(which we use for dynamic stuff), as those templates are statically cached. https://github.com/sotty/drools/commit/1b75d4785861e72338cc5ea1280610a793... Mark On 8 Jan 2014, at 00:53, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > The root of the perm gen leak has now be solved, thanks to some heroic work by community developer Davide Sottara. > > This is just in time for the 5.6 release going out this week. You will not need to use the kbase.dispose() work around. > > Mark > On 6 Jan 2014, at 20:50, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > >> The 5.6 approach should be considered a work around, not a fix. Somewhere a ref is being held, that shouldn’t be - we just haven’t found it yet. >> >> Mark >> >> On 6 Jan 2014, at 19:17, Davide Sottara <dsotty(a)gmail.com&gt; wrote: >> >>> I have run pmander's tests, and reported in a previous email. >>> The leak in 5.x is due to the nature of the composite classloader, and >>> dispose() >>> forces the memory to be released. I don't remember if that fix was in >>> 5.6.CR1 >>> (probably not), so you may have to try 5.6.0-SNAPSHOT or wait for the >>> end of the week. >>> 6.x does not suffer from the same problem, but has a different issue - >>> no way >>> to unload kie modules once they are cached - which Mario has been >>> working on. >>> In either case, pmander's test works fine in both 5.6.x and 6.x after >>> these fixes >>> Davide >>> >>> On 01/06/2014 07:56 PM, Mark Proctor wrote: >>>> I’ve been told 5.6 will be released this week. This is because the JCR2GIT migration tool, in 5.6 is needed for our 6.0 product. >>>> >>>> Davide's current kbase.dispose() method, on the concrete class, should just be considered a work around for the problem. Unless this is fixed by someone in the community, I don’t think any core developers will have time to address this. At least not for 5.x; we’ll continue to look into it for 6.x. >>>> >>>> Mark >>>> >>>> >>>> On 6 Jan 2014, at 16:14, brachi <brachi.w(a)sapiens.com&gt; wrote: >>>> >>>>> see previous messages, pmander attached a unit test >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html >>>>> Sent from the Drools: User forum mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> rules-users mailing list >>>>> rules-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>>> _______________________________________________ >>>> rules-users mailing list >>>> rules-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>> >>> _______________________________________________ >>> rules-users mailing list >>> rules-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/rules-users >> > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Is this possible to set everything to MVEL Dialect as we are using JavaDialect in all our rules. We had this few times before and we managed to avoid it with usage of CMSClassUnlaoadingEnabled . But this has again comeback recently because the rate at which the classes are produced with load,CMS is unable to collect the permgen space at same rate so it trips Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 15/01/2014 18:27 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org You can try setting everything to the MVEL dialect, and also forcing MVEL to reflection via the system property (turning off jit) http://mvel.codehaus.org/Disabling+the+JIT+Compiler Mark On 15 Jan 2014, at 18:23, adarsh.chaini(a)hsbcib.com wrote: Hi Mark/Davide Is there a work around to this problem in 5.4?. Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 08/01/2014 04:46 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org For anyone interested. The commit involves addressing two needs. 1) Enforcing MVEL reflection mode throughout - MVEL ASM optimiser can NEVER be used for anything (it doesn’t add much value anyway). 2) Avoiding giving the template system the root class loader(which we use for dynamic stuff), as those templates are statically cached. https://github.com/sotty/drools/commit/1b75d4785861e72338cc5ea1280610a793... Mark On 8 Jan 2014, at 00:53, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > The root of the perm gen leak has now be solved, thanks to some heroic work by community developer Davide Sottara. > > This is just in time for the 5.6 release going out this week. You will not need to use the kbase.dispose() work around. > > Mark > On 6 Jan 2014, at 20:50, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > >> The 5.6 approach should be considered a work around, not a fix. Somewhere a ref is being held, that shouldn’t be - we just haven’t found it yet. >> >> Mark >> >> On 6 Jan 2014, at 19:17, Davide Sottara <dsotty(a)gmail.com&gt; wrote: >> >>> I have run pmander's tests, and reported in a previous email. >>> The leak in 5.x is due to the nature of the composite classloader, and >>> dispose() >>> forces the memory to be released. I don't remember if that fix was in >>> 5.6.CR1 >>> (probably not), so you may have to try 5.6.0-SNAPSHOT or wait for the >>> end of the week. >>> 6.x does not suffer from the same problem, but has a different issue - >>> no way >>> to unload kie modules once they are cached - which Mario has been >>> working on. >>> In either case, pmander's test works fine in both 5.6.x and 6.x after >>> these fixes >>> Davide >>> >>> On 01/06/2014 07:56 PM, Mark Proctor wrote: >>>> I’ve been told 5.6 will be released this week. This is because the JCR2GIT migration tool, in 5.6 is needed for our 6.0 product. >>>> >>>> Davide's current kbase.dispose() method, on the concrete class, should just be considered a work around for the problem. Unless this is fixed by someone in the community, I don’t think any core developers will have time to address this. At least not for 5.x; we’ll continue to look into it for 6.x. >>>> >>>> Mark >>>> >>>> >>>> On 6 Jan 2014, at 16:14, brachi <brachi.w(a)sapiens.com&gt; wrote: >>>> >>>>> see previous messages, pmander attached a unit test >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html >>>>> Sent from the Drools: User forum mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> rules-users mailing list >>>>> rules-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>>> _______________________________________________ >>>> rules-users mailing list >>>> rules-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>> >>> _______________________________________________ >>> rules-users mailing list >>> rules-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/rules-users >> > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Mark, Thanks for your reply.

We have been testing against 5.5.0.Final and we faced some problems . One of the problem was that we had a quick fix to mvel component from redhat guys (with their good will )

to one of the critical concurrency issues we faced .But it seems that fix is not part of these community releases and there has been changes to mvel after that change. Is there a way that we can make the same permgen fix to the 5.4.0.Final codebase?.

Or Is this possible to get the concurrency fix these newer versions?.

Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 15/01/2014 21:05 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org why not just update to 5.6, it’s fixed there. http://downloads.jboss.org/drools/release/5.6.0.Final/ You can specify dialect at the top of the drl file, to be applied to all rules in that file. But that’s about it. Mark On 15 Jan 2014, at 20:51, adarsh.chaini(a)hsbcib.com wrote: Is this possible to set everything to MVEL Dialect as we are using JavaDialect in all our rules. We had this few times before and we managed to avoid it with usage of CMSClassUnlaoadingEnabled . But this has again comeback recently because the rate at which the classes are produced with load,CMS is unable to collect the permgen space at same rate so it trips Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 15/01/2014 18:27 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org You can try setting everything to the MVEL dialect, and also forcing MVEL to reflection via the system property (turning off jit) http://mvel.codehaus.org/Disabling+the+JIT+Compiler Mark On 15 Jan 2014, at 18:23, adarsh.chaini(a)hsbcib.com wrote: Hi Mark/Davide Is there a work around to this problem in 5.4?. Thanks and regards, Adarsh CHAINI SENIOR LEAD DEVELOPMENT SPECIALIST | HSBC Bank Plc 8 Canada Square, London E14 5HQ, UK _______________________________________________ Phone Int: (0)79914720 Ext: +44 (0)20 79914720 Mobile +44(0)7595530105 Email adarsh.chaini(a)hsbcib.com _______________________________________________ Protect our environment - please only print this if you have to! From: Mark Proctor <mproctor(a)codehaus.org&gt; To: Rules Users List <rules-users(a)lists.jboss.org&gt; Date: 08/01/2014 04:46 Subject: Re: [rules-users] permgen leak Sent by: rules-users-bounces(a)lists.jboss.org For anyone interested. The commit involves addressing two needs. 1) Enforcing MVEL reflection mode throughout - MVEL ASM optimiser can NEVER be used for anything (it doesn’t add much value anyway). 2) Avoiding giving the template system the root class loader(which we use for dynamic stuff), as those templates are statically cached. https://github.com/sotty/drools/commit/1b75d4785861e72338cc5ea1280610a793... Mark On 8 Jan 2014, at 00:53, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > The root of the perm gen leak has now be solved, thanks to some heroic work by community developer Davide Sottara. > > This is just in time for the 5.6 release going out this week. You will not need to use the kbase.dispose() work around. > > Mark > On 6 Jan 2014, at 20:50, Mark Proctor <mproctor(a)codehaus.org&gt; wrote: > >> The 5.6 approach should be considered a work around, not a fix. Somewhere a ref is being held, that shouldn’t be - we just haven’t found it yet. >> >> Mark >> >> On 6 Jan 2014, at 19:17, Davide Sottara <dsotty(a)gmail.com&gt; wrote: >> >>> I have run pmander's tests, and reported in a previous email. >>> The leak in 5.x is due to the nature of the composite classloader, and >>> dispose() >>> forces the memory to be released. I don't remember if that fix was in >>> 5.6.CR1 >>> (probably not), so you may have to try 5.6.0-SNAPSHOT or wait for the >>> end of the week. >>> 6.x does not suffer from the same problem, but has a different issue - >>> no way >>> to unload kie modules once they are cached - which Mario has been >>> working on. >>> In either case, pmander's test works fine in both 5.6.x and 6.x after >>> these fixes >>> Davide >>> >>> On 01/06/2014 07:56 PM, Mark Proctor wrote: >>>> I’ve been told 5.6 will be released this week. This is because the JCR2GIT migration tool, in 5.6 is needed for our 6.0 product. >>>> >>>> Davide's current kbase.dispose() method, on the concrete class, should just be considered a work around for the problem. Unless this is fixed by someone in the community, I don’t think any core developers will have time to address this. At least not for 5.x; we’ll continue to look into it for 6.x. >>>> >>>> Mark >>>> >>>> >>>> On 6 Jan 2014, at 16:14, brachi <brachi.w(a)sapiens.com&gt; wrote: >>>> >>>>> see previous messages, pmander attached a unit test >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: http://drools.46999.n3.nabble.com/permgen-leak-tp4027038p4027539.html >>>>> Sent from the Drools: User forum mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> rules-users mailing list >>>>> rules-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>>> _______________________________________________ >>>> rules-users mailing list >>>> rules-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>> >>> _______________________________________________ >>> rules-users mailing list >>> rules-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/rules-users >> > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi Mark, Started a new topi though it was related to permgen leak Can you please point me to the 5.4.0.Final source code repository that can be pulled for local development ?. Is there any maven based repository for these projects ?. Adarsh ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ************************************************************ HSBC Bank plc may be solicited in the course of its placement efforts for a new issue, by investment clients of the firm for whom the Bank as a firm already provides other services. It may equally decide to allocate to its own proprietary book or with an associate of HSBC Group. This represents a potential conflict of interest. HSBC Bank plc has internal arrangements designed to ensure that the firm would give unbiased and full advice to the corporate finance client about the valuation and pricing of the offering as well as internal systems, controls and procedures to identify and manage conflicts of interest. HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England - Number 14259 Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group "HSBC" for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy._______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users