Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4404D61E.106@labpro2000.com>
Date: Wed, 01 Mar 2006 12:00:46 +1300
From: "Nathan Smith" <nathan@labpro2000.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
References: <du1vmr$rdg$1@sea.gmane.org>
In-Reply-To: <du1vmr$rdg$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Tomasz,

you mentioned below that you have a MaxPermSize of 256m. I would suggest 
increasing this value to a much larger amount and even increasing your 
-Xms and -Xmx values.

We had a problem with our application in a live environment where it 
would regularly get errors like the following;
 
Exception java.lang.OutOfMemoryError: requested SIZE_FORMAT bytes for 
compute_new_size. Out of swap space?
Possible causes:
    - not enough swap space left, or
    - kernel parameter MAXDSIZ is very small.
( 0)  0xc5bf0474   vm_exit_out_of_memory__FUlPCcb + 0x47c  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1)  0xc5e89d78   compute_new_size__9PSPermGenFUl + 0x150  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2)  0xc5e86024   invoke_no_policy__11PSMarkSweepSFPbb + 0x244  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 3)  0xc5e8b814   invoke__10PSScavengeSFPb + 0x154  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 4)  0xc5e51f4c   failed_mem_allocate__20ParallelScavengeHeapFPbUlbT3 + 
0x64  [/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 5)  0xc5f6a78c   doit__29VM_ParallelGCFailedAllocationFv + 0x54  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 6)  0xc5f6a280   evaluate__12VM_OperationFv + 0xb0  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 7)  0xc5f691e0   evaluate_operation__8VMThreadFP12VM_Operation + 0x48  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 8)  0xc5f698a0   loop__8VMThreadFv + 0x558  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 9)  0xc5f68f24   run__8VMThreadFv + 0xd4  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
(10)  0xc5e39b20   _start__FPv + 0x148  
[/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
(11)  0xc004b168   __pthread_body + 0x44  [/usr/lib/libpthread.1]
(12)  0xc00549ec   __pthread_start + 0x14  [/usr/lib/libpthread.1]

In the end it was the fact that the PermGen space was all used up and 
JVM was trying to resize it. The PermGen may have become full because of 
the number of class files and JSP class files that were loaded into 
memory or other resources that are kept in PermGen by the JVM.

I would say with 8 applications running under Tomcat you would need to 
make as much of that 3Gb available to the JVM to use. My 2 cents worth.

Cheers.

Tomasz Nowak wrote:
> Probably important:
> ===================
> - 2x Xeon, 3 GB mem
> - Linux 2.4.26
> - Java 1.5.0_06-b05
> - Apache Tomcat 5.5.15
> - CATALINA_OPTS="\
>     -server \
>     -Djava.awt.headless=true \
>     -Dfile.encoding=UTF-8 \
>     -XX:MaxPermSize=256m \
>     -Xms1024m -Xmx1024m"
> - <Connector port="8009" protocol="AJP/1.3"
>     maxThreads="200" minSpareThreads="25" maxSpareThreads="50"
>     backlog="20" connectionTimeout="10000"
>     enableLookups="true" redirectPort="8443" />
>
> - mod_jk 1.2.15
> - Apache Httpd 1.3.34
> - 8 Tomcat vhosts
> - 8 webapps
> - each webapp runs on separate vhost
> - each webapp is Apache Cocoon 2.1.7
> - system load avarage: usually under 0.5
> - http load: not more then 20-30 concurrent req
>
> The pain: crashing Tomcat
> ======================
>
> Everything works right until Tomcat suddenly crashes,
> what happens almost every single day. Sometimes it crashes
> with OOME / out of heap (heh, is 1GB not enought!?), but
> somtimes NOTHING wrong is logged into the logs - it
> just stops responding to requests (hangs).
>
> When Tomcat stops responding to requests JK eats all
> of 256 Apache HTTPd MaxClients so other httpd vhosts
> stop responding also. Disaster!
>
> Any ideas before abandoning Java technology? ;)
>
> Default Tomcat logging facility seems to be useless to me.
> j.u.l. logging.properties semantics looks like a programmers
> joke made to users (!). And even with swallowOutput it logs
> everything into catalina.out (?) I found none decent
> log4j-tomcat-virtual-hosts-logging-manual in Tomcat docs
> also. Is Tomcat a production ready reference j2se server
> or just a "finish it yourself" proof of concept toy?
>
> I've been crond-restarting Tomcat 4.1 on Java 1.4 every
> night for more than a year, and now I have to restart
> Tomcat 5.5.15 on Java 1.5 AND apache httpd also almost
> every single day. From my -user point of view, Tomcat
> doesn't change in a good direction. In fact in it is
> probably changing in wrong direction - at least the
> 4.1.x logger element has been working 'out of the box'.
>
> Come on! Am I the only one that has such problems with Tomcat?
>  
>   

-- 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org