From: Martin Honermeyer (martinhonermeyer_at_web.de)
Date: Mon 17 Feb 2003 - 16:32:01 GMT
Hi,
I've got the same problem.
I bought a vserver (www.server4you.de) and soon realized that this is very limited.
I found out that my system uses technology from Virtuozzo (http://www.sw.ru/en/products/virtuozzo/).
They provide kernel statistics in /proc.
This is the output of cat /proc/user_beancounters:
Version: 2.5
uid resource held maxheld barrier limit failcnt
138027: kmemsize 1412237 2174829 2211840 2359296 0
lockedpages 0 0 32 32 0
privvmpages 19460 29888 65536 65536 0
shmpages 12 16653 24845 24845 0
dummy 0 0 0 0 0
numproc 36 60 100 100 0
physpages 13165 20127 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 13165 20127 6144 2147483647 0
numtcpsock 34 68 80 80 0
numflock 1 7 100 110 0
numpty 1 3 16 16 0
numsiginfo 0 9 256 256 0
tcpsndbuf 28224 363792 319488 524288 7058078
tcprcvbuf 0 144416 319488 524288 0
othersockbuf 6672 56304 122880 327680 0
dgramrcvbuf 0 49792 65536 65536 0
numothersock 16 30 80 80 0
dcachesize 224361 297776 491520 524288 0
numfile 752 964 1280 49152 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 5 5 128 128 0
Look at the line "numproc". It shows that there is limit of 100 processes!
This is really awkward.
I installed Tomcat and it crashes everytime I call a medium-sized JSP-page.
In the shell, it just says "not enough memory", although there is much system memory left (> top).
So I think I will not be able to run Tomcat on my vserver, right?
Greets,
Martin
On Monday 17 February 2003 12:10, Michael Hilscher wrote:
> Hi,
>
> are there any problems known with tomcat in an vserver? In my debian
> vserver installation tomcat needs neerly 2.5 more memory. In production
> use tomcat sometimes requests more ram until it kills itself (memory-leak).
>
> I didn't touch the capset - shall i give the tomcat vserver more caps to
> fix the problem (which ones are possible needed)?
>
>
> greetinXs,
> Michael Hilscher