@tomcat.apache.org
Subject: Re: Java Heap Space Error
Pratik,
On 4/20/23 03:35, pratik.kulka...@shell.com.INVALID wrote:
> I guess you're right, Tomcat 9 allocates less default memory compared
> to Tomcat 8; I checked our logs and below are the memory parameters
> which seem t
Pratik,
On 4/20/23 03:35, pratik.kulka...@shell.com.INVALID wrote:
I guess you're right, Tomcat 9 allocates less default memory compared to Tomcat
8; I checked our logs and below are the memory parameters which seem to be
passed in,
Tomcat 9 -
14-Apr-2023 02:47:55.567 INFO [main]
org.apache
Thanks Chris,
I guess you're right, Tomcat 9 allocates less default memory compared to Tomcat
8; I checked our logs and below are the memory parameters which seem to be
passed in,
Tomcat 9 -
14-Apr-2023 02:47:55.567 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command li
Pratik,
On 4/13/23 22:55, pratik.kulka...@shell.com.INVALID wrote:
Chris - I see. So we already have installed a service and I tried to
set the environment variable after we got the error. Is there a way
for Tomcat to read the variables we set after installation?
If you are running the Windows S
On 14.04.23 04:55, pratik.kulka...@shell.com.INVALID wrote:
Hi All,
Thanks for your quick suggestions.
As Olaf suggested, I tried to set the same values to Xms and Xmx; the
application immediately crashes after Tomcat restart and I am not able to
access it. I tried it with different values,
23 09:00
To: users@tomcat.apache.org
Subject: Re: Java Heap Space Error
Think Secure. This email is from an external source.
Pratik,
You're getting the error when executing a DB query. How many rows does it
return? Could it be returning too
timer scheduled
14-Apr-2023 02:48:30.591 SEVERE [https-jsse-nio-443-exec-2] . Java heap space
java.lang.OutOfMemoryError: Java heap space
at
oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:165)
at
oracle.jdbc.driver.T4CCallableStatem
led
14-Apr-2023 02:48:30.591 SEVERE [https-jsse-nio-443-exec-2] . Java heap space
java.lang.OutOfMemoryError: Java heap space
at
oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:165)
at
oracle.jdbc.driver.T4CCallableStatem
Pratik,
On 4/13/23 05:35, pratik.kulka...@shell.com.INVALID wrote:
This email concerns an error I encountered while using Oracle Apex with ORDS 3.0.9 and
Tomcat 9. Specifically, I receive a "Java heap space" error when accessing the
application.
To troubleshoot the issue, I hav
Pratik,
> -Original Message-
> From: pratik.kulka...@shell.com.INVALID
>
> Sent: Thursday, April 13, 2023 4:36 AM
> To: users@tomcat.apache.org
> Subject: Java Heap Space Error
>
> Hello,
>
> This email concerns an error I encountered while using Ora
LID wrote:
> > Hello,
> >
> > This email concerns an error I encountered while using Oracle Apex with
> ORDS 3.0.9 and Tomcat 9. Specifically, I receive a "Java heap space" error
> when accessing the application.
> >
> > To troubleshoot the issue, I have tried t
Hi Pratik,
On 13.04.23 11:35, pratik.kulka...@shell.com.INVALID wrote:
Hello,
This email concerns an error I encountered while using Oracle Apex with ORDS 3.0.9 and
Tomcat 9. Specifically, I receive a "Java heap space" error when accessing the
application.
To troubleshoot the iss
Hello,
This email concerns an error I encountered while using Oracle Apex with ORDS
3.0.9 and Tomcat 9. Specifically, I receive a "Java heap space" error when
accessing the application.
To troubleshoot the issue, I have tried to increase the maximum heap size of
the JVM using the -
//
One correction, option -XX:-HeapDumpOnOutOfMemoryError disables heapdumps on
OOM, you should use -XX:+HeapDumpOnOutOfMemoryError - with plus sign, to enable
it.
//
Thanks for the follow-up.
--Eric
2015-03-21 12:37 GMT+02:00 Антон Мацюк :
> 2015-03-21 2:06 GMT+02:00 Eric Robinson :
>>> Set this options to JVM, and it will make heapdumps automatically.
>> Will these heap dumps be the same size as the current tomcat memory
>> utilization?
> Yeap, and OOM will guarantee that there is no garbage
2015-03-21 2:06 GMT+02:00 Eric Robinson :
>> I think if you have vendor-locked app in vendor-locked environment (am I
>> right?)
> Yes indeed.
So, worth a try, at least.
>> Set this options to JVM, and it will make heapdumps automatically.
> Will these heap dumps be the same size as the current
//
I think if you have vendor-locked app in vendor-locked environment (am I
right?)
//
Yes indeed.
//
As I said above, there is an options for JVM:
-XX:-HeapDumpOnOutOfMemoryError - it will make heapdump on OOM.
-XX:HeapDumpPath=./java_pid.hprof - give it an reasonable path to file.
Set this o
2015-03-20 22:29 GMT+02:00 Eric Robinson :
>> Very good information. I much prefer finding the actual root causes of
>> things rather than just bumping the memory, but I'm not sure how much that
>> would help because the best I can do is report the issue to the vendor.
>> Changing the code is of
//
Mostly leaner - a 32-bit JVM uses 32-bit pointers, so object references consume
less heap and stack space. Whether or not the code runs faster or slower
depends on what you're doing, since the tradeoff is fewer registers available
in 32-bit mode, which can lead to more register spills and re
//
You can look for biggest objects in heap (using MAT, Leak Suspects report,
Dominators Tree report).
This way you can try to find what was the exact reason of OOM instead of just
thinking "eh, I need to give instances more memory".
MAT does things good. I've already found using MAT+JVVM the rea
> From: Eric Robinson [mailto:eric.robin...@psmnv.com]
> Subject: RE: Java Heap Space / Thread Dump Numbers
> > If you have the option, you might want to run a 32-bit JVM; it will
> > probably run leaner
> > and faster than a 64-bit JVM will.
> What do you mean my
2015-03-20 22:09 GMT+02:00 Eric Robinson :
>> I've posted above some howtos, have you looked at them?
> No, I'm not sure how useful I would find them. I think the heap summary is
> probably all I need, but I may be wrong. Would the heap dump provide more
> actionable intel as far as tuning my me
> From: Eric Robinson [mailto:eric.robin...@psmnv.com]
> Subject: RE: Java Heap Space / Thread Dump Numbers
> Would the heap dump provide more actionable intel as far as tuning my memory
> parameters?
It would provide information about what types of objects are consuming the heap
//
Recent 64-bit JVMs will automatically use "-XX:+UseCompressedOops".
I'm not sure about your version, specifically. If you have the option, you
might want to run a 32-bit JVM; it will probably run leaner and faster than a
64-bit JVM will.
//
Interesting. What do you mean my faster and leaner?
//
Yeah, heapdumps.
I've posted above some howtos, have you looked at them?
//
No, I'm not sure how useful I would find them. I think the heap summary is
probably all I need, but I may be wrong. Would the heap dump provide more
actionable intel as far as tuning my memory parameters?
--Eric
2015-03-20 1:15 GMT+02:00 Eric Robinson :
> Heap dumps?
> What we do is called a thread dump, as far as I know. We use kill -3 on
> Linux, which dumps the thread activity. The memory data shows up at the
> bottom of that. See:
> http://producthelp.sdl.com/WorldServer/10.2/en/GUID-4F09CD10-BC4F-4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric,
On 3/19/15 7:15 PM, Eric Robinson wrote:
> Christopher Shultz wrote: // Time to upgrade. Tomcat is hideously
> out of date (probably because you are using RedHat's Tomcat
> package), at least by version number. I'm not sure what RedHat
> doe
Christopher Shultz wrote:
//
Time to upgrade. Tomcat is hideously out of date (probably because you are
using RedHat's Tomcat package), at least by version number. I'm not sure what
RedHat does (if anything) about security fixes, etc. but a vanilla 6.0.18 is
probably vulnerable and has been for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric,
On 3/19/15 11:15 AM, Eric Robinson wrote:
> Thanks for the feedback. We run various versions of RHEL (5.5 to
> 6.3) x64. Tomcat is mostly 6.0.18. Java is mostly 6u21 x 64.
Time to upgrade. Tomcat is hideously out of date (probably because yo
> PSYoungGen total 95808K, used 22323K [0x2aaac377,
> 0x2aaaca21, 0x2aaaca21)
> eden space 82432K, 10% used
> [0x2aaac377,0x2aaac402f7f8,0x2aaac87f)
> from space 13376K, 99% used
> [0x2aaac87f,0x2aaac94fd5a8,0x2aaac950)
>
remotely.
Good luck! :)
2015-03-19 3:35 GMT+02:00 Caldarale, Charles R :
>> From: Eric Robinson [mailto:eric.robin...@psmnv.com]
>> Subject: Java Heap Space / Thread Dump Numbers
>
>> PSYoungGen total 95808K, used 22323K [0x2aaac377,
>> 0x2aaaca21,
> From: Eric Robinson [mailto:eric.robin...@psmnv.com]
> Subject: Java Heap Space / Thread Dump Numbers
> PSYoungGen total 95808K, used 22323K [0x2aaac377,
> 0x2aaaca21, 0x2aaaca21)
> eden space 8
When we see these errors in the tomcat logs...
java.lang.OutOfMemoryError: Java heap space
... we do a thread dump and examine the memory numbers, resulting in output
such as the following...
PSYoungGen total 95808K, used 22323K [0x2aaac377,
0x2aaaca21
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/30/2011 12:24 PM, André Warnier wrote:
> Note also that running out of Heap space does not necessarily mean that
> your classes have leaks. It can also mean that they are just using
> memory to a point where your allocated Heap space is s
tp11Protocol.java:166)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:288)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
Exception in thread
"ContainerBackgroundProcessor[StandardEngine[Catalina]]"
java.lang.
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: Exception in thread ""http-bio-8080"-exec-9"
> java.lang.OutOfMemoryError: Java heap space
> I apologise (a little bit) for my original answer
You shouldn't apologize; the OP has still not p
that this is a bug in tomcat 7. Let me know in case you can make
any sense out of the trace.
===
Exception in thread ""http-bio-8080"-exec-12" java.lang.OutOfMemor
You are kidding us, right ?
But just in case you are not, what is the part which you do not understand in
"java.lang.OutOfMemoryError: Java heap space".
?
http://lmgtfy.com/?q=java.lang.OutOfMemoryError:%20Java%20heap%20space
sunil.sheva...@wipro.com wrote:
Hi,
I am gettin
Hi,
I am getting an error as follows
"Exception in thread ""http-bio-8080"-exec-9"
java.lang.OutOfMemoryError: Java heap space".
I am running my jsp application on a windows machine with Tomcat 7.0.8
Any pointers?
Thanks in advance,
Sunil.
Please do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Another correction to the code:
On 10/8/2009 4:22 PM, Christopher Schultz wrote:
> public static class SoftReferenceSessionWrapper
> implements HttpSession
> {
Remember to implement getValue and putValue to call getAttribute and
setAttr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
A correction to my code:
On 10/8/2009 4:22 PM, Christopher Schultz wrote:
> public class SoftReferenceFilter
> implements Filter
> {
This class needs two additional methods:
public void init(FilterChain chain) { }
public void des
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 10/8/2009 12:12 PM, Joe Hansen wrote:
> I will now think twice before I store anything in the session and
> will make sure I remove no longer used objects from the HTTP
> Session.
It's always a good goal to limit your session size, but it's n
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: java.lang.OutOfMemoryError: Java heap space
>
> Is the use of SoftReference popular?
You'll find it as the underlying mechanism of many cache managers, since it
automatically adapts reasonably well to whate
> Yup, it looks like you have more of your application objects taking up
> memory than the tickets you were worried about.
So True! We are right now designing and developing our next generation
of websites and this experience will surely come handy. I will now
think twice before I store anything i
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: java.lang.OutOfMemoryError: Java heap space
>
> There are even techniques that will allow your session objects to
> expire when memory gets tight (which is super cool IMO).
To put a name on the above
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 10/7/2009 8:40 PM, Joe Hansen wrote:
> WoW! "jmap" was a great command to learn Chris! Thank you so much!
Yeah, it's great as a poor-man's memory profiler. On the other hand, I
haven't seen a big-time memory profiler offer such a simple view
WoW! "jmap" was a great command to learn Chris! Thank you so much!
I generated a histogram of the Objects in the java heap (while things
were stable) and here's what I got:
Object Histogram:
SizeCount Class description
---
149989048
in memory and/or sessions?
> I am *guessing* :
> I changed the session timeout to 4 hours for the Jasig CAS
> Single-Signon web application. This stores a ton of tickets in memory.
> During a 4 hour period when there are more http requests, the 512MB of
> Java Heap space is not suffi
2009/10/6 Joe Hansen :
> Andre, you are right. Memory is cheap. However, the machine has 8GB of
> memory already. I am thinking that it should be sufficient.
You might wish to dedicate more of that 8 Gbyte to Java, though. It
depends on the performance characteristics of your application - looks
moryError, followed by MySQL errors when
>> TWFotoSetListDAO.getAllFotosets tried to get a database connection.
>>
>> I am *guessing* :
>> I changed the session timeout to 4 hours for the Jasig CAS
>> Single-Signon web application. This stores a ton of tickets in memo
Rainer Jung wrote:
On 06.10.2009 21:44, Joe Hansen wrote:
...
It seems your application is CPU heavy. Either the data objects handled
are to heavy weight (maybe some user having huge Fotoset or Email list)
or the request rate is simply to large. Is the CPU saturated during the
problems?
I wou
when
> TWFotoSetListDAO.getAllFotosets tried to get a database connection.
>
> I am *guessing* :
> I changed the session timeout to 4 hours for the Jasig CAS
> Single-Signon web application. This stores a ton of tickets in memory.
> During a 4 hour period when there are more http re
anged the session timeout to 4 hours for the Jasig CAS
Single-Signon web application. This stores a ton of tickets in memory.
During a 4 hour period when there are more http requests, the 512MB of
Java Heap space is not sufficient to store all these tickets. During
that time OutOfMemoryError happen
On 06.10.2009 19:44, Joe Hansen wrote:
I will only comment the threads for the AJP pool. Everything else seems
not relevant:
Dump 1:
20 threads connected to Apache, waiting for the next request
3 threads idle in the pool
1 thread waiting for the next connection
0 threads working on requests
D
There were 29 httpd processes running when the websites crashed.
One thing that was clear from the thread dumps was there were lots of
entries for org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner:
Starting cleaning of expired tickets from ticket registry at ...
Does that indicat
Rainer,
I spoke to soon! As I suspected, the problem isn't fixed yet and the
websites crashed again. This time I took three thread dumps at the
time tomcat was down. Here they are: http://pastebin.com/m2a7e1198
I will learn from your previous analysis of the thread dumps and I try
to understand w
Rainer,
Thanks for looking at those long thread dumps for me!!
I am sorry. I did NOT take these dumps at the right time (i.e. when
Tomcat was inundated with requests and couldn't cope with the load).
After I increased the heap size to 512MB (from 64MB default), I am not
getting the OutOfMemoryErr
On 05.10.2009 18:58, Joe Hansen wrote:
> Thank you so much for your tips, Rainer!
>
> The websites went down yet again. Increasing the java heap size took
> care of the OutOfMemoryError, but the number of httpd processes keep
> increasing until the websites crash. I haven't added any new code in
>
public web server yourself.
>>
>> If you don't want to post in public, you can also mail it to me, I will
>> post the result, in case I find something relevant.
>>
>> Regards,
>>
>> Rainer
>>
>>> On Sat, Oct 3, 2009 at 12:24 PM, Rainer Jung
On 05.10.2009 22:04, André Warnier wrote:
> André Warnier wrote:
> ...
> and still wants to add something :
>
> - a new KeepAlive connection is made from the browser to Apache (httpd).
> - then a request comes in on that connection, and it happens to be one
> that gets forwarded to Tomcat. So a m
Andre, Thanks for pointing out the high KeepAliveTimeout value in the
config file. I have read the docs and have changed it to 5 seconds
(which is the default).
I am hoping that Rainer could find out from the thread dump where the
requests are getting stuck, so that I can put this issue to bed.
T
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: java.lang.OutOfMemoryError: Java heap space
>
> The bottleneck would be in Tomcat, but it would show up at the
> httpd level.
The bottleneck might also be in something external to Tomcat, such as a
database or so
André Warnier wrote:
...
and still wants to add something :
- a new KeepAlive connection is made from the browser to Apache (httpd).
- then a request comes in on that connection, and it happens to be one
that gets forwarded to Tomcat. So a mod_jk connection is made to
Tomcat, Tomcat allocates
Joe Hansen wrote:
Thank you for the reply, Andre.
I now understand how setting KeepAlive to On would improve the
performance of a website (The Apache manual says that a 50% increase
in throughput could be expected). So I changed the KeepAlive to On and
restarted the server.
Now wait.
You shoul
Thank you for the reply, Andre.
I now understand how setting KeepAlive to On would improve the
performance of a website (The Apache manual says that a 50% increase
in throughput could be expected). So I changed the KeepAlive to On and
restarted the server.
I however wonder if this will fix the is
Joe Hansen wrote:
Rainer,
Here are the KeepAlive values in httpd.conf:
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimout 15
Well, since you have "KeepAlive Off", the other 2 do not matter.
But as such, it means that each request of each browser is going to
create a new connection to the
Rainer,
Here are the KeepAlive values in httpd.conf:
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimout 15
Thanks,
Joe
> What are your KeepAlive* settings ?
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
F
not have a public web server yourself.
>
> If you don't want to post in public, you can also mail it to me, I will
> post the result, in case I find something relevant.
>
> Regards,
>
> Rainer
>
>> On Sat, Oct 3, 2009 at 12:24 PM, Rainer Jung wrote:
>>>
Joe Hansen wrote:
I found the following error message in the Apache logs:
[Sat Oct 03 04:10:49 2009] [error] server reached MaxClients setting,
consider raising the MaxClients setting
Here's a snippet from the httpd.conf, which deals with MaxClients.
StartServers 8
MinSpareServers5
Ma
levant.
Regards,
Rainer
> On Sat, Oct 3, 2009 at 12:24 PM, Rainer Jung wrote:
>> On 03.10.2009 20:07, Joe Hansen wrote:
>>> Hey All,
>>>
>>> I get this error (java.lang.OutOfMemoryError: Java heap space) after
>>> my Apache 2.0/Tomcat 5.5/mod_jk ins
be able to please tell me what should I be
>> looking for within this long thread dump?
>>
>> Thanks again, Rainer :)
>>
>> Joe
>>
>> On Sat, Oct 3, 2009 at 12:24 PM, Rainer Jung wrote:
>>> On 03.10.2009 20:07, Joe Hansen wrote:
>>>&g
>> On 03.10.2009 20:07, Joe Hansen wrote:
>>> Hey All,
>>>
>>> I get this error (java.lang.OutOfMemoryError: Java heap space) after
>>> my Apache 2.0/Tomcat 5.5/mod_jk installation has been up and running
>>> for a few hours. This problem started just since
;>
>> I get this error (java.lang.OutOfMemoryError: Java heap space) after
>> my Apache 2.0/Tomcat 5.5/mod_jk installation has been up and running
>> for a few hours. This problem started just since two days. Never had
>> this issue before!
>>
>> I have also notic
On 03.10.2009 20:07, Joe Hansen wrote:
> Hey All,
>
> I get this error (java.lang.OutOfMemoryError: Java heap space) after
> my Apache 2.0/Tomcat 5.5/mod_jk installation has been up and running
> for a few hours. This problem started just since two days. Never had
> this issue b
Hey All,
I get this error (java.lang.OutOfMemoryError: Java heap space) after
my Apache 2.0/Tomcat 5.5/mod_jk installation has been up and running
for a few hours. This problem started just since two days. Never had
this issue before!
I have also noticed that as soon as I startup the server, 9
Thanks a lot it seems I also need to do the same.
Regards,
Ningappa Koneri
mLifestyle | www.comviva.com
-Original Message-
From: Suleyman Akpinar [mailto:suleyman.akpi...@hititcs.com]
Sent: Tuesday, September 01, 2009 1:49 PM
To: Özkan Dülger; Serdar Gür
Subject: Re: java heap space
Many thanks Pid,
Your solution seems very reasonable. I will fulfill your advice.
Best Regards,
Suleyman
Pid wrote:
On 01/09/2009 08:58, Suleyman Akpinar wrote:
Hi all,
I have a java web application running on tomcat and I get java heap
space not enough error temporarily. Each time I am
On 01/09/2009 08:58, Suleyman Akpinar wrote:
Hi all,
I have a java web application running on tomcat and I get java heap
space not enough error temporarily. Each time I am increasing the JMV
heap option by modifying the system variable CATALINA_OPTS. However,
this solves the problem temporarily
Hi all,
I have a java web application running on tomcat and I get java heap
space not enough error temporarily. Each time I am increasing the JMV
heap option by modifying the system variable CATALINA_OPTS. However,
this solves the problem temporarily. I get the same error when I work
for
Dear Todd,
I'm not sure I can use session counting, as my
session size is not consistent. I could try to estimate
the size of each session, and keep a global counter,
but that seems like a lot of work.
JMX offers quite a bit of insight in what your GC is doing. You could
implement throttling
> From: André Warnier [mailto:a...@ice-sa.com]
> Thanks, Chuck and Peter, for the clarifications on OOM.
> I believe that unconsciously, with my "large object
> reservation" theory,
> I was vaguely remembering something I had read some time in the past.
> So I searched Google for "java +parachute +
Thanks, Chuck and Peter, for the clarifications on OOM.
I believe that unconsciously, with my "large object reservation" theory,
I was vaguely remembering something I had read some time in the past.
So I searched Google for "java +parachute +memory" and this is something
I found :
http://mail-
> From: Todd Hivnor [mailto:spambox_98...@yahoo.com]
> Subject: Re: Preventing OutOfMemoryError: Java heap space
>
> In my tests, as the RAM becomes depleted, the server
> response becomes slower and slower.
That's because you're going through garbage collecti
On 13.05.2009 08:07, Peter Crowther wrote:
>> From: André Warnier [...@ice-sa.com] would it not be easier to catch
>> the OOM exception and then return a "sorry, server overloaded" page
>> to the browser ?
>
> At that point, it's too late. A thread, somewhere in the system,
> tried to allocate so
> From: Todd Hivnor [mailto:spambox_98...@yahoo.com]
> One challenge with Peter's suggestion of tracking the
> number of sessions myself is that I have a collection
> of webapps. So I can't just set up a shared static counter;
> I need a counter which works across multiple webapps.
> The only way I
> From: André Warnier [...@ice-sa.com]
> would it not be easier to catch the OOM exception and then return a
> "sorry, server overloaded" page to the browser ?
At that point, it's too late. A thread, somewhere in the system, tried to
allocate some memory for an object and couldn't. This could h
>> But would it not be easier to catch the OOM exception and then
>> return a "sorry, server overloaded" page to the browser ?
> It's difficult to do that when the OOME may occur in Tomcat code,
> outside of control of the webapp.
Wow I had assumed I could always catch this type of exception.
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: Preventing OutOfMemoryError: Java heap space
>
> > I'm going to add an explicit request for garbage
> > collection, _before_ the memory becomes seriously
> > depleted.
To the OP: explicitly callin
Todd Hivnor wrote:
From: Todd Hivnor [spambox_98...@yahoo.com]
I would like to proactively avoid running out of heap
space. I would like people get a "Server Too Busy"
message, _before_ the heap is actually exhausted.
I would rather serve 40 users well than 45 users
poorly.
Rather than moni
>> From: Todd Hivnor [spambox_98...@yahoo.com]
>> I would like to proactively avoid running out of heap
>> space. I would like people get a "Server Too Busy"
>> message, _before_ the heap is actually exhausted.
>
>> I would rather serve 40 users well than 45 users
>> poorly.
> Rather than monito
> From: Todd Hivnor [spambox_98...@yahoo.com]
> I would like to proactively avoid running out of heap
> space. I would like people get a "Server Too Busy"
> message, _before_ the heap is actually exhausted.
> I would rather serve 40 users well than 45 users
> poorly.
Rather than monitor memory, w
I think the results are going to be pretty erratic.
The issue that I see is that the garbage collector operation is (to my
knowledge) not deterministic.
IOW, you're not really accounting for memory that could be garbage
collected. So, I think that you'll have a systematic bias showing less
m
I have a Java application running under Tomcat 6.0.18
on Ubuntu. This is using Sun's 1.6.0_07 JVM. I know
how to set the max heap space by setting -Xmx256m
in CATALINA_OPTS. But with a lot of sessions, I still
have the possibility of running out of heap space. My
application uses a lot of memo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan,
Stefan Rainer wrote:
> we are running a Tomcat 5.0.28 on W2k Server with 2 GB RAM and JVM
> 1.5.0_11-b03 which is mainly used as application server for (Axis-based)
> SOAP Services.
>
> From time to time our Tomcat blows up to use almost
> From: Stefan Rainer [mailto:[EMAIL PROTECTED]
> Subject: AW: IOException while loading persisted sessions /
> java.lang.OutOfMemoryError: Java heap space
>
> Is there any possibiliy in Tomcat 5.0.28 to turn off
> session-persistence?
First, you should be aware that 5.0.28 is n
hricht-
Von: André Warnier [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 01. Dezember 2008 11:47
An: Tomcat Users List
Betreff: Re: IOException while loading persisted sessions /
java.lang.OutOfMemoryError: Java heap space
Sorry, I was so shocked by the last info about 64 MB, that I missed wha
persistant sessions in our
applications.
??
Thanks, Stefan
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 01. Dezember 2008 11:47
An: Tomcat Users List
Betreff: Re: IOException while loading persisted sessions /
java.lang.OutOfMemoryError: Java
Sorry, I was so shocked by the last info about 64 MB, that I missed what
you wrote about the physical machine...
Stefan Rainer wrote:
Hello,
we are running a Tomcat 5.0.28 on W2k Server with 2 GB RAM and JVM
1.5.0_11-b03 which is mainly used as application server for (Axis-based)
SOAP Services
Stefan Rainer wrote:
[...]
SEVERE: An exception or error occurred in the container during the request
processing
java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-16302-Processor151" java.lang.OutOfMemoryError:
Java heap space
Extract from configuration / status,
of Tomcat is not possible and the following lines
can be found in stdout.log:
SEVERE: An exception or error occurred in the container during the request
processing
java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-16302-Processor151" java.lang.OutOfMemoryError:
Java h
1 - 100 of 121 matches
Mail list logo
