On 29/01/2016 11:07, Guo, Denny wrote: > Yes, we do have this option on for MaxPermSize, it is set to 512M. > > If that is related to PermSize, should we get this message " > java.lang.OutOfMemoryError: PermGen space". However we never see this message > in the log.
Use a profiler. Find out what is using all that memory. Mark > > -----Original Message----- > From: kidambi madhu [mailto:madhu.kida...@gmail.com] > Sent: Thursday, January 28, 2016 11:43 PM > To: Tomcat Users List > Subject: Re: FW: Re: tomcat 6.0.41 heap size issue > > Ok What's the size of the war file you have deployed to Tomcat? > > I suspect the problem is with PermSize (The class loading part of JVM) than > Heap though the error points out Java Heap. > > Pls set the PermSize with -XX:PermSize and -XX:MaxPermSize options and test. > > Thanks, > Madhu > > On Fri, Jan 29, 2016 at 8:53 AM, Guo, Denny <d...@livingstonintl.com> wrote: > >> Thanks for quick response. Here is the information. >> >> java version "1.6.0_45" >> Java(TM) SE Runtime Environment (build 1.6.0_45-b06) Java HotSpot(TM) >> 64-Bit Server VM (build 20.45-b01, mixed mode) >> >> >> -----Original Message----- >> From: kidambi madhu [mailto:madhu.kida...@gmail.com] >> Sent: Thursday, January 28, 2016 10:15 PM >> To: Tomcat Users List >> Subject: Re: FW: Re: tomcat 6.0.41 heap size issue >> >> Hi Denny, >> >> Which JDK you are using Oracle JDK/JRockit and which version. >> >> Some memory tuning options depend on JDK product used. >> >> Thanks, >> Madhu >> >> On Fri, Jan 29, 2016 at 8:39 AM, Guo, Denny <d...@livingstonintl.com> >> wrote: >> >>> >>> Hi All, >>> >>> Looking for help on tomcat heap size issue. >>> >>> We are see below GC activity before tomcat reports the heap size error. >>> Please see below message. However, we assign -Xmx=24G to the heap >>> size, why tomcat reports error even not reach 20G heap size usage ? >>> Can someone please help. How the tomcat decides how much memory >>> allocate to young/old generation? >>> >>> We are running tomcat 6.0.41 on red hat linux as per our vendor. >>> >>> Thanks, >>> Denny >>> >>> 2016-01-28T21:20:56.173-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222720K)], 26.7667120 secs] [Times: >>> user=26.77 sys=0.01, real=26.76 secs] >>> 2016-01-28T21:21:22.942-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222720K)], 26.5016220 secs] [Times: >>> user=26.51 sys=0.01, real=26.50 secs] >>> 2016-01-28T21:21:49.444-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222912K)], 26.7081550 secs] [Times: >>> user=26.70 sys=0.01, real=26.70 secs] >>> 2016-01-28T21:22:16.154-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222912K)], 26.7299520 secs] [Times: >>> user=26.73 sys=0.01, real=26.72 secs] >>> 2016-01-28T21:22:42.884-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222912K)], 26.7488570 secs] [Times: >>> user=26.75 sys=0.00, real=26.75 secs] >>> 2016-01-28T21:23:09.635-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777215K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222912K)], 26.7899470 secs] [Times: >>> user=26.80 sys=0.00, real=26.79 secs] >>> 2016-01-28T21:23:36.425-0500: [Full GC [PSYoungGen: >>> 761K->761K(2880K)] >>> [PSOldGen: 16777215K->16777216K(16777216K)] >>> 16777977K->16777977K(16780096K) >>> [PSPermGen: 222628K-222628K(222912K)], 43.0072820 secs] [Times: >>> user=43.01 sys=0.02, real=43.00 secs] >>> 2016-01-28T21:24:19.435-0500: [Full GC [PSYoungGen: 761K->0K(2880K)] >>> [PSOldGen: 16777216K->632811K(4342144K)] >>> 16777977K->632811K(4345024K) >>> [PSPermGen: 222628K->222628K(222912K)], 4.9992850 secs] [Times: >>> user=4.96 sys=0.04, real=5.00 secs] >>> 2016-01-28T21:24:19.435-0500: [Full GC [PSYoungGen: 761K->0K(2880K)] >>> [PSOldGen: 16777216K->632811K(4342144K)] >>> 16777977K->632811K(4345024K) >>> [PSPermGen: 222628K->222628K(222912K)], 4.9992850 secs] [Times: >>> user=4.96 sys=0.04, real=5.00 secs] Exception in thread "Low Memory >>> Detector" java.lang.OutOfMemoryError: Java heap space >>> 2016-01-28T21:24:24.438-0500: [GC [PSYoungGen: 128K->224K(8960K)] >>> 632939K->633035K(4351104K), 0.0045990 secs] [Times: user=0.02 >>> 632939K->sys=0.00, >>> real=0.01 secs] >>> 2016-01-28T21:24:24.444-0500: [GC [PSYoungGen: 288K->192K(9088K)] >>> 633099K->633003K(4351232K), 0.0032440 secs] [Times: user=0.02 >>> 633099K->sys=0.00, >>> real=0.00 secs] >>> 2016-01-28T21:24:24.449-0500: [GC [PSYoungGen: 254K->160K(9280K)] >>> 633098K->633003K(4351424K), 0.0032180 secs] [Times: user=0.02 >>> 633098K->sys=0.00, >>> real=0.01 secs] >>> Jan 28, 2016 9:24:24 PM >>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor >>> processChildren >>> SEVERE: Exception invoking periodic operation: >>> java.lang.OutOfMemoryError: Java heap space >>> at >>> >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycle >> Support.java:139) >>> at >>> >> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase >> .java:1389) >>> at >>> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.pr >> ocessChildren(ContainerBase.java:1653) >>> at >>> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.ru >> n(ContainerBase.java:1642) >>> at java.lang.Thread.run(Thread.java:662) >>> Jan 28, 2016 9:24:24 PM org.apache.coyote.http11.Http11Processor >>> process >>> SEVERE: Error processing request >>> >>> >>> [Facebook] <https://www.facebook.com/livingstoninternational/> >>> [Twitter] <https://twitter.com/livingston_intl> [LinkedIn] < >>> http://www.linkedin.com/company/livingston-international> [Google+] >>> < https://plus.google.com/+Livingstonintl/posts> >>> [Livingston Logo] >>> >>> >>> >>> >>> >>> This e-mail may contain privileged and confidential information. If >>> you are not the intended recipient, you are hereby notified that any >>> review, dissemination, distribution or duplication of this >>> communication is strictly prohibited. You are requested to notify >>> the sender and delete this message and all copies thereof. Internet >>> e-mail is not guaranteed to be secure or error-free. This sender >>> will not be liable for the risks associated with e-mail. | Ce >>> message ?lectronique pourrait contenir des informations privil?gi?es >>> et confidentielles. Si vous n'en ?tes pas le r?cipiendaire pr?vu, >>> nous vous signalons qu'il est strictement interdit d'examiner, de >>> diffuser, de distribuer et de >> reproduire le pr?sent message. >>> Veuillez pr?venir l'exp?diteur, puis effacer ce message et en >>> d?truire toute copie. Le courrier ?lectronique n'est pas garanti >>> s?curitaire ni exempt d'erreurs. L'exp?diteur n'est pas responsable >>> des risques associ?s au courrier ?lectronique. >>> >> [Facebook] <https://www.facebook.com/livingstoninternational/> >> [Twitter] <https://twitter.com/livingston_intl> [LinkedIn] < >> http://www.linkedin.com/company/livingston-international> [Google+] >> < https://plus.google.com/+Livingstonintl/posts> >> [Livingston Logo] >> >> >> >> >> >> This e-mail may contain privileged and confidential information. If >> you are not the intended recipient, you are hereby notified that any >> review, dissemination, distribution or duplication of this >> communication is strictly prohibited. You are requested to notify the >> sender and delete this message and all copies thereof. Internet e-mail >> is not guaranteed to be secure or error-free. This sender will not be >> liable for the risks associated with e-mail. | Ce message électronique >> pourrait contenir des informations privilégiées et confidentielles. Si >> vous n'en êtes pas le récipiendaire prévu, nous vous signalons qu'il >> est strictement interdit d'examiner, de diffuser, de distribuer et de >> reproduire le présent message. >> Veuillez prévenir l'expéditeur, puis effacer ce message et en détruire >> toute copie. Le courrier électronique n'est pas garanti sécuritaire ni >> exempt d'erreurs. L'expéditeur n'est pas responsable des risques >> associés au courrier électronique. >> > [Facebook] <https://www.facebook.com/livingstoninternational/> [Twitter] > <https://twitter.com/livingston_intl> [LinkedIn] > <http://www.linkedin.com/company/livingston-international> [Google+] > <https://plus.google.com/+Livingstonintl/posts> > [Livingston Logo] > > > > > > This e-mail may contain privileged and confidential information. If you are > not the intended recipient, you are hereby notified that any review, > dissemination, distribution or duplication of this communication is strictly > prohibited. You are requested to notify the sender and delete this message > and all copies thereof. Internet e-mail is not guaranteed to be secure or > error-free. This sender will not be liable for the risks associated with > e-mail. | Ce message électronique pourrait contenir des informations > privilégiées et confidentielles. Si vous n'en êtes pas le récipiendaire > prévu, nous vous signalons qu'il est strictement interdit d'examiner, de > diffuser, de distribuer et de reproduire le présent message. Veuillez > prévenir l'expéditeur, puis effacer ce message et en détruire toute copie. Le > courrier électronique n'est pas garanti sécuritaire ni exempt d'erreurs. > L'expéditeur n'est pas responsable des risques associés au courrier > électronique. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
