<font size=2 face="sans-serif">We had this issue where the permgen
space was not reclaimed as CMS does not by default reclaim unless you use
</font><tt><font size=2>CMSClassUnloadingEnabled </font></tt><font size=2 face="sans-serif">.</font>
<br><font size=2 face="sans-serif">After that we have not seen this though
the permgen space keeps growing with addition of rules.The only thing we
are afraid that if the permgen space requirement becomes same/greater than
the threshold that CMS reclaims then what will happen?.We keep changing/increasing
the permgen space but there is a limit to this at some point we can't
allocate more proportion of memory for permgen space only ...</font>
<br>
<br><font size=2 face="sans-serif">Thanks<br>
&<br>
Regards,<br>
Adarsh <br>
<br>
SENIOR LEAD DEVELOPMENT SPECIALIST<br>
SCJP, SCWCD <br>
FINANCE TECHNOLOGY<br>
HSBC BANK PLC HBEU<br>
8 Canada Square,Canary Wharf,<br>
London,E14 5HQ,United Kingdom<br>
------------------------------------------------------<br>
Phone +44 207914720<br>
Mobile 07595530105<br>
Email. adarsh.chaini@hsbcib.com<br>
________________________________</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Mark Proctor <mproctor@codehaus.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Rules Users List <rules-users@lists.jboss.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">18/11/2013 17:12</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [rules-users] Drools Perm gen grows
constantly</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">rules-users-bounces@lists.jboss.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Are you saying the permgen is leaking? That you update
the rules, and no perigean space is reclaimed?<br>
<br>
There are some issues with the JVM, that I’ve seen before, which may be
the problem. Such as the CMSClassUnloadingEnabled issue:<br>
</font></tt><a href="http://java.dzone.com/articles/busting-permgen-myths"><tt><font size=2>http://java.dzone.com/articles/busting-permgen-myths</font></tt></a><tt><font size=2><br>
<br>
I’d be interested to know if this is a pergmen leak, and if it continues
on 6.x. If it does, maybe you could work with us to find out why it’s
not being reclaimed?<br>
<br>
Mark<br>
<br>
On 18 Nov 2013, at 16:56, pmander <paul.s.mander@gmail.com> wrote:<br>
<br>
> Thanks for clearing this up. The overhead for us is negligible and
more<br>
> important that the application is survivable. Using Java as the dialect<br>
> would appear to not be a option for anyone then?<br>
> <br>
> We are using drools to process around 50Mil transactions against 15k
rules.<br>
> This is distributed over 32 nodes to get the end to end performance
we need.<br>
> Using java dialect on initial run with a mac perm size of 512Mb copes
ok but<br>
> on subsequent runs we run out of perm gen space and the processes
take up<br>
> tons of cpu and then run out of memory. For each run we have to recreate
the<br>
> knowledge base.<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> --<br>
> View this message in context: </font></tt><a href="http://drools.46999.n3.nabble.com/Drools-Perm-gen-grows-constantly-tp4026673p4026812.html"><tt><font size=2>http://drools.46999.n3.nabble.com/Drools-Perm-gen-grows-constantly-tp4026673p4026812.html</font></tt></a><tt><font size=2><br>
> Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> rules-users mailing list<br>
> rules-users@lists.jboss.org<br>
> </font></tt><a href="https://lists.jboss.org/mailman/listinfo/rules-users"><tt><font size=2>https://lists.jboss.org/mailman/listinfo/rules-users</font></tt></a><tt><font size=2><br>
<br>
<br>
_______________________________________________<br>
rules-users mailing list<br>
rules-users@lists.jboss.org<br>
</font></tt><a href="https://lists.jboss.org/mailman/listinfo/rules-users"><tt><font size=2>https://lists.jboss.org/mailman/listinfo/rules-users</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
************************************************************<br>
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.<br>
<br>
HSBC Bank plc<br>
Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom<br>
Registered in England - Number 14259<br>
Authorised by the Prudential Regulation Authority and regulated by the
Financial Conduct Authority and the Prudential Regulation Authority<br>
************************************************************<br>
</font>
-----------------------------------------
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.