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
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
> 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
2010/4/19 Woude, Alexander van der
> Sorry a small correction. The client times out, because the tomcat gives a
> Heap Space memory error.
>
> config in startup.sh :
>
> export JAVA_OPTS="-Xms128m -Xmx512m"
> export CATALINA_OPTS="-Xms512m -XX:MaxPermSize=512m"
>
> My apps are 7 war, that each c
On 19/04/2010 12:54, Woude, Alexander van der wrote:
> Sorry a small correction. The client times out, because the tomcat gives a
> Heap Space memory error.
>
> config in startup.sh :
>
> export JAVA_OPTS="-Xms128m -Xmx512m"
> export CATALINA_OPTS="-Xms512m -XX:MaxPermSize=512m"
You're setting
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 CATALINA_OPTS.
> Now I ge
Sorry a small correction. The client times out, because the tomcat gives a Heap
Space memory error.
config in startup.sh :
export JAVA_OPTS="-Xms128m -Xmx512m"
export CATALINA_OPTS="-Xms512m -XX:MaxPermSize=512m"
My apps are 7 war, that each contain its own deps. Size of 1 war is 14 MB
How do
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
14 matches
Mail list logo
