On 10/01/2010 23:25, Caldarale, Charles R wrote:
From: Patrick Flaherty [mailto:pflah...@rampageinc.com]
Sent: 2010 January 10, Sunday 16:28
To: Tomcat Users List
Can anyone post a virtual host snippet from their server.xml ?
Better if you post your server.xml and the Context elements from
Thanks for the pointers Chris.
I did some more research to isolate the cause of the issue (my web
application, java or tomcat).
I used a 5.5.28 tomcat installation and ensured that there is no webapp
running within tomcat.
Then I pointed JAVA_HOME to java 1.5 and 1.6 and looked at the file
SHORT SUMMARY:
===
When Apache HTTPD is used for both URL manipulation (request
redirecting) and load-balancing with mod_jk, the plus-characters seem
to behave strangely during character re-encoding. Is this a bug or a
feature, and how should the system be set up to ensure correct
Tomcat 6.0.20 zip (used service command to run as windows service)
Window 2003 Server 2.0GB RAM (1.3GB available)
My problem:
org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet servlet name threw exception
java.lang.OutOfMemoryError: Java heap space
I've
http://www.theserverside.com/news/thread.tss?thread_id=48390
http://wiki.apache.org/tomcat/FAQ/Memory
Try googling
On 01/11/2010 11:29 AM, Leo Donahue - PLANDEVX wrote:
Tomcat 6.0.20 zip (used service command to run as windows service)
Window 2003 Server 2.0GB RAM (1.3GB available)
My
From: Leo Donahue - PLANDEVX [mailto:leodona...@mail.maricopa.gov]
Subject: Tomcat memory settings
I've read many previous posts and online articles about increasing the
memory settings for Tomcat. As it stands, I've modified the
catalina.bat file and set the CATALINA_OPTS variable from
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory. I
have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version 1.6.0_17
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build
dmesg
check if the linux out of memory kill struck you :)
Andy
On 01/11/2010 04:37 PM, Carl wrote:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory.
I have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version
2010/1/11 Carl c...@etrak-plus.com:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory.
I have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version 1.6.0_17
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Peter and Andy,
Thanks for your quick responses.
Memory: Physical - $GB
Used - 2.4GB to 3.0 GB (according to top... have never seen
it above 3GB)
Swap - 19GB, none ever used (or, at least I have never seen
any used.)
The above are all from top.
The 2.4GB is
I assume $GB means 4GB :)
With that kind of memory use it doesn't sound entirely like the OOM
killer. Have you looked around the filesystem for hs_err[pid].pid
files? This usually is written to the cwd of the java process. That
might give you ideas if it's a native crash. If so, it'll have the
Andy,
Yes, that is 4GB... just a little stressed.
I did a 'find' for all 'hs_err*.pid' files and turned up nothing, no files
were found.
I am using catalina.sh to start Tomcat and I had always assumed that the
java JVM was started in that process somewhere. I apologize for my
ignorance
2010/1/12 Carl c...@etrak-plus.com:
Peter and Andy,
Thanks for your quick responses.
Memory: Physical - $GB
Used - 2.4GB to 3.0 GB (according to top... have never seen it
above 3GB)
Swap - 19GB, none ever used (or, at least I have never seen
any used.)
The
Konstantin,
Yes, it was started using startup.sh in tomcat/bin and used the same ports
(8080, 8443, 443) as the tomcat that died. The fact that the OS did not
recover the memory implied to me (could be wrong, even very wrong) that the
JVM just died. However, as you point out, how did the
On 11/01/2010 23:06, Peter Crowther wrote:
2010/1/11 Carlc...@etrak-plus.com:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory. I
have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version 1.6.0_17
Java(TM) SE
Aha, for some reason, I thought perm gen was included in the general heap so
the maximum for the two combined was constrained by the 2400m I had defined
for the heap. Somewhere around 2:00AM (I am US east coast), I can restart
the server with the new settings.
I have taken several heap dumps
tomcat 6:
I am seeing following exception in localhost file with no stack trace.
There is no clue as to why this might be happening. How do I get the
full stack trace to narrow down the problem? We also have our
application log where our application specific exceptions get logged
with full stack
Hi Everyone,
I am running tomcat 5.5 on Debian Linux (uname says Linux 2.6.26-2-amd64,
/etc/debian_version says 5.0.2). The JVM version is 1.5.0_14-b03.
We have 9 servlets running.
The tomcat process itself is managed by monit.
We see tomcat memory usage growing over time and have set monit
I am using JRockit as my java runtime. When I manually start Tomcat, I have no
problems with it. However, when I try to run Tomcat as a service with JRockit
as my java runtime, I get an error that says that it cannot start the service.
I looked in the service.bat file and I think that I may
2010/1/12 Mohit Anchlia mohitanch...@gmail.com:
tomcat 6:
I am seeing following exception in localhost file with no stack trace.
There is no clue as to why this might be happening. How do I get the
full stack trace to narrow down the problem? We also have our
application log where our
20 matches
Mail list logo
