It's been on my plate to research this and the memory for permanent generation (GC for class information) is fixed at 4MB so if we're running out, no brainer to increase.
Default max Heap size it a little more complicated depending on resources detected. http://www.oracle.com/technetwork/java/ergo5-140223.html It will either allow for up to 1/4 the memory up to 1GB if its a server class, or 64MB if it thinks its on a client class. I wonder if folks are reporting this issue on vms that match client-class machines according to java. If so, I wonder if we should just force server-class with the "-server" option. On Wed, Sep 22, 2010 at 10:34 AM, Krisztian Ganyai <[email protected]> wrote: > Hi, > > > > I reckon the other memory errors were heap related. If someone has them, > could he/she please try to add -Xmx=512M (or -Xmx=768M in case of lot of > RAM) to the CLI options and see if the errors go away? > > > > The param should be added the same way MaxPermGen mentioned below is added. > > > > BR, > > Chris > > > > ________________________________ > > From: Matt White [mailto:[email protected]] > Sent: Thursday, September 16, 2010 4:32 PM > To: [email protected] > Subject: Re: [sipx-dev] Java Out of Memory Errors > > > > Increasing the PermGen has fixed it for my builds. However I have seen > reports of people with Java memory issues that do NOT log a PermGen > error....but some other type of memory error. > > For those, I do not think the PermGen helps. I've only had PermGen errors > on my SuSe builds. > > -M > >>>> Douglas Hubler <[email protected]> 09/16/10 10:24 AM >>> > On Thu, Sep 16, 2010 at 10:05 AM, jnolen <[email protected]> wrote: >> Customer is running: >> >> sipXconfig (4.2.1-018930 2010-06-04T15:26:43 build31). >> >> While manipulating Speed Dial entries, they are getting Java Out of >> Memory Errors -- see sipxconfig log snippet below. >> >> I've seen discussions of this condition in previous post -- mostly >> having to do with CDR reports. I don't see a confirmation of an >> adequate 'fix'. >> >> Is there a tested solution to this problem? > > Last response was to add > > -XX:MaxPermGen=128M > > to sipxconfig java CLI options. I can add this to 4.2.1 if someone > can acknowledge this solved their problem > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
