On 25/06/2019 12:58, Christoph Hanke wrote:
> Hi,
>
> I have got a jspx Page which gets reloaded every 30 seconds to show some
> status information. Consequently there are database requests every 30
> seconds. Before switching from glassfish to tomcat (7.0.94) there were
> no issues with that, but
Hi,
I have got a jspx Page which gets reloaded every 30 seconds to show some
status information. Consequently there are database requests every 30
seconds. Before switching from glassfish to tomcat (7.0.94) there were
no issues with that, but now the memory consumption is bloating over time.
Look
On 21/06/2016 15:52, Afaf Zahkya wrote:
> Hello,
>
> I m using tomcat 8.0.21.
>
> I want to send *up* to 4 MB of text messages through a websocket connection
> to my tomcat server. I set the MaxTextMessageBufferSize to 4 MB.Now as a
> result, every time I open a websocket connection and I send a
Hello,
I m using tomcat 8.0.21.
I want to send *up* to 4 MB of text messages through a websocket connection
to my tomcat server. I set the MaxTextMessageBufferSize to 4 MB.Now as a
result, every time I open a websocket connection and I send a message , I
can see that 4 MB are being allocated in
Just for completeness on anyone reading this...
Setting development mode to false has vastly improved the performance, as is
no doubt already known by most people! My Old Generation memory now cycles
nicely, clearing out by 75% each time.
I also added the "checkInterval" parameter (at anything gr
Bugger thanks.
I looked at this but, when I did, I simply compared the two web.xml
files between Tomcat-7.0.8 and Tomcat-7.0.10 to see if a specific
setting for development mode was used differently, but the two files
were exactly the same, with no development mode setting mentioned.
Which means t
On 29/07/2011 09:53, Ian Marsh wrote:
> Ok thanks... so here's the trace of the 3 biggest
> org.apache.jasper.servlet.JspServletWrapper objects.
>
> I'm just showing the path of the objects that retain the biggest sizes
> at each nested level to save from overkill on detail. There are
> references
Ok thanks... so here's the trace of the 3 biggest
org.apache.jasper.servlet.JspServletWrapper objects.
I'm just showing the path of the objects that retain the biggest sizes
at each nested level to save from overkill on detail. There are
references to parent objects at some levels which show a lar
On 28/07/2011 12:29, Ian Marsh wrote:
> Right, I have taken a memory snapshot using YourKit of the system
> running Tomcat-7.0.10 after about 1 hour, when the Old Gen memory was
> beginning to reach its maximum.
OK. I think a little more digging is required but this might be heading
somewhere usef
Right, I have taken a memory snapshot using YourKit of the system
running Tomcat-7.0.10 after about 1 hour, when the Old Gen memory was
beginning to reach its maximum.
I am not completely sure what information is useful for you to know as
I have not used YourKit before so I am working from the dem
On 26/07/2011 10:43, Ian Marsh wrote:
> Unfortunately the conf changes to fork the compilation of JSPs and the
> increased 'modificationTestInterval' value made no real improvement so
> I am continuing to work towards replacing the language text request
> scope variables with property files referen
Unfortunately the conf changes to fork the compilation of JSPs and the
increased 'modificationTestInterval' value made no real improvement so
I am continuing to work towards replacing the language text request
scope variables with property files references.
However, if this is a problem, this has
Good morning and thanks for the replies!
Unfortunately, as far as I am aware, our bank determines who we must
use as the PCI Auditor so our hands are tied with that one, but it
does seem like they're just covering their backs by choosing the
latest available version rather than actually determinin
On 22/07/2011 20:17, Mark Thomas wrote:
> On 22/07/2011 17:26, Ian Marsh wrote:
>> Hi,
>>
>> I am in charge of running a Apache-2, Tomcat-7, Ubuntu-10.04 set up
>> for which we have to be PCI Compliant. We recently upgraded to
>> Apache-2.2.17 and Tomcat-7.0.8 (from Apache-2.0.x and Tomcat 5.0.28)
On 22/07/2011 20:17, Mark Thomas wrote:
> On 22/07/2011 17:26, Ian Marsh wrote:
>> It seems that the character arrays [C, java.lang.String and
>> javax.servlet.jsp.tagext.TagAttributeInfo entries are considerably
>> higher in Tomcat-7.0.10 than in Tomcat-7.0.8 and I am wondering if
>> this could l
On 22/07/2011 17:26, Ian Marsh wrote:
> Hi,
>
> I am in charge of running a Apache-2, Tomcat-7, Ubuntu-10.04 set up
> for which we have to be PCI Compliant. We recently upgraded to
> Apache-2.2.17 and Tomcat-7.0.8 (from Apache-2.0.x and Tomcat 5.0.28)
> in order to comply with the requirements of
cycling. The Old
Generation slowly increases until garbage collection runs and clears
out the Old Gen memory level, dropping considerably as expected.
So to the upgrading! Upgrading Apache has been successful and without
problem, however upgrading Tomcat has caused memory problems which, as
yet, I
> What is the quickest way to find out?
jmap -heap
p
>
> Van: Pid [...@pidster.com]
> Verzonden: maandag 19 april 2010 15:33
> Aan: Woude, Alexander van der
> Onderwerp: Re: memory problems / time outs
>
> On 19/04/2010 14:05,
Onderwerp: Re: memory problems / time outs
On 19/04/2010 13:24, Woude, Alexander van der wrote:
> Thanks for the suggestions this far.
> I had an oversight with the tomcat monitoring, didnt notice it on the site.
>
> I will try that just as the suggestions about JStack etc.
>
> why 2
> Verzonden: maandag 19 april 2010 14:16
> Aan: Tomcat Users List
> Onderwerp: Re: memory problems / time outs
>
> 2010/4/19 Woude, Alexander van der
>
>> Sorry a small correction. The client times out, because the tomcat gives a
>> Heap Space memory error.
I was wrong?
>
> Thanks
> Alex
>
> Van: Harry Metske [harry.met...@gmail.com]
> Verzonden: maandag 19 april 2010 14:16
> Aan: Tomcat Users List
> Onderwerp: Re: memory problems / time outs
>
> 2010/4/19 Woude, Alexander van der
Alex
Van: Harry Metske [harry.met...@gmail.com]
Verzonden: maandag 19 april 2010 14:16
Aan: Tomcat Users List
Onderwerp: Re: memory problems / time outs
2010/4/19 Woude, Alexander van der
> Sorry a small correction. The client times out, because
to monitor real time memory usage.
> Greetings
> Alex
>
>
>
> Van: Woude, Alexander van der [alexander.vander.wo...@capgemini.com]
> Verzonden: maandag 19 april 2010 13:49
> Aan: users@tomcat.apache.org
> Onderwerp: memory problems / time outs
>
u could post the result of that here.
p
> Greetings
> Alex
>
>
>
> Van: Woude, Alexander van der [alexander.vander.wo...@capgemini.com]
> Verzonden: maandag 19 april 2010 13:49
> Aan: users@tomcat.apache.org
> Onderwerp: m
On 19/04/2010 12:49, Woude, Alexander van der wrote:
> Hello All
>
> For a client I developed a few Data webservices. In total there are 7
> services.
> All are CXF based webservices that use hibernate.
>
> I keep having memory problems, so I increased both JAVA_OPTS as C
1 war is 14 MB
How do I check the memory the tomcat uses?
Greetings
Alex
Van: Woude, Alexander van der [alexander.vander.wo...@capgemini.com]
Verzonden: maandag 19 april 2010 13:49
Aan: users@tomcat.apache.org
Onderwerp: memory problems / time outs
Hello
Hello All
For a client I developed a few Data webservices. In total there are 7 services.
All are CXF based webservices that use hibernate.
I keep having memory problems, so I increased both JAVA_OPTS as CATALINA_OPTS.
Now I get timed out errors and tomcat blocks completely, I only can resolve
2009/10/5 prashant sharma :
> Tomcat: 5.0.
That's old, and no longer supported. Why are you using this version?
(And exactly which version of 5.0 are you using, by the way?)
> OS: Windows Server HPC edition.
32- or 64-bit? I ask because the maximum contiguous memory you'll get
in 32-bit is som
Hi,
We are using the following configuration:
Tomcat: 5.0.
OS: Windows Server HPC edition.
JVM: 5.0
There is one basic doubt that I have. When we load/stress our Tomcat server, we
hit thresholds mentioned below once in a while. The root of the problem is that
when I increase the clients, I
orten
Enviada em: terça-feira, 21 de agosto de 2007 09:11
Para: users@tomcat.apache.org
Assunto: Re: Memory problems
>> Are there any way to stop Tomcat from cached these large byte[]
>> internally?
>> The ByteChunks are referenced from IntermediateOutputstream,
>> C2BConv
>> Are there any way to stop Tomcat from cached these large
>> byte[] internally?
>> The ByteChunks are referenced from IntermediateOutputstream,
>> C2BConverter and OutputBuffer.
>Hmm. Those are all Tomcat util classes, so they're almost certainly
>held by something else. Can you find out what'
> From: Morten
> According to a heap dump done by jmap, there are many
> org.apache.tomcat.util.buf.ByteChunk instances referencing
> large byte[],
> which we suspect to be previously used pictures.
>
> We have tried both Tomcat 5.5.9 and Tomcat 6 under JBoss
> 4.2.0. Both showed
> the same b
Hi
We have implemented a picture server in Tomcat.
The pictures are cached in a map. When the memory is nearly full, some
entries are removed from map.
However, eventually the entries in the map become fewer and fewer even
though the memory consumption stays high. In other words more and more
m its internal cache?
Best regards,
Morten Knudsen
--
View this message in context:
http://www.nabble.com/Tomcat-5.5.9-memory-problems-tf3992793.html#a11338090
Sent from the Tomcat - User mailing list archive at Nabble.com.
---
I have some servlets that run without problem on tomcat 4, but when I
upgraded to Tomcat 5.5.15, everytime a servlet is accessed, it uses a
little more memory, and finally after many users, runs out of heap
space. Any clues?
Thanks Dan Gross
-
35 matches
Mail list logo
