Hi,
thanks for your answer.
We use the methods Runtime.getRuntime().freeMemory() and Runtime.getRuntime().totalMemory() to check the mem size. We don't have any loops that run continuously.
Michael
____________________________________________
SinnerSchrader Aktiengesellschaft
mailto:[EMAIL PROTECTED]
http://www.sinnerschrader.de
fon +49.(0) 40.39 88 55-0
fax +49.(0) 40.39 88 55-55
Planckstrasse 13 | 22765 Hamburg | Germany
____________________________________________
| Rikard Westlund <[EMAIL PROTECTED]>
Sent by: <[EMAIL PROTECTED]> 17.11.00 15:56
|
To: "'Java Apache Users'" <[EMAIL PROTECTED]> cc: Subject: SV: Memory Problem |
Hi!
What tool do u use to check the mem size on Solaris?? When it comes to the OutOfMemory error I would give the code a second look over. If you have java loops that execute/run continuously, make sure that they cleanup after them self's and try to use inheriting as much as you can
-Rikard
-----Ursprungligt meddelande-----
Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Skickat: den 17 november 2000 15:01
Till: [EMAIL PROTECTED]
Ämne: Memory Problem
Hello,
we are using Jserv 1.1 together with Apache 1.3.9 on a machine running Solaris 2.7.
The problem is the following:
When we run our servlets under NT, about 40 MB of memory is allocated after the initalisation of all servlets. When we check the memory on the Solaris machine, a minimum of 300 MB is allocated. The max. heapsize available for the vm is 800 MB, somtimes it happens that we run out of memory. What could be the reason for this different behaviour?
Thanks in advance!
Michael Volz
____________________________________________
SinnerSchrader Aktiengesellschaft
mailto:[EMAIL PROTECTED]
http://www.sinnerschrader.de
fon +49.(0) 40.39 88 55-0
fax +49.(0) 40.39 88 55-55
Planckstrasse 13 | 22765 Hamburg | Germany
____________________________________________
