When upgrading from 7.0.26 to 7.0.29, MyEclipse cannot start the Tomcat
instance without reaching an OutOfMemoryError exception that results
from a GC overhead limit exceeded when Tomcat begins it's
multi-threaded deployment process. MyEclipse is running with 1GB of
maximum memory and still
The OOME I am getting is coming from Heap, and that's even giving Tomcat
1GB of maximum heap. The instance seems to start successfully outside
of the MyEclipse environment; however inside MyEclipse it fails
miserably. The surprising part of this is that the instance has ran
with half that amount
Thanks Mark!
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Monday, July 16, 2012 12:35 PM
To: Tomcat Users List
Subject: RE: OOME while expanding a war with tomcat 7.0.29 but not with tomcat
7.0.28
CRANFORD, CHRIS chris.cranf...@setech.com wrote:
The OOME I am
Eric -
One could argue what's the true benefit here though? Production shouldn't be
restarted or unavailable except during an outage, whether it's planned or
unplanned, right?
-Original Message-
From: Eric Bouer [mailto:ericbo...@gmail.com]
Sent: Monday, September 19, 2011 6:46 AM
I use SC which allows you to communication with a remote Service Control
Manager on an NT platform to stop the Tomcat service; deploy the WAR
file and then restart the server in one simple execution. On *nix you
could use some flavor of an secure shell script to stop the process, do
your secure
I have II7 setup with the ISAPI AJP connector and it works just dandy
when using a single worker pointed to a particular tomcat instance. I
now need to use some rewrite functionality so that the following occurs:
http://mydomain.com/sdm = tomcat SDM instance and runs webapp /myapp
: Re: Destroying Context Listeners
On 16/08/2010 18:32, CRANFORD, CHRIS wrote:
I recently upgraded my Tomcat installation from 6.0.x to Tomcat 7
(Win64) and I am actively testing our current web applications for
backward compatibility, and so forth. One of these web applications
14:11, CRANFORD, CHRIS wrote:
When I check the version of Tomcat 7, it says it is 7.0.0.0.
It's the compiled version from 6/13/2010.
Try downloading the latest beta, (or compile from trunk).
http://people.apache.org/~markt/dev/tomcat-7/v7.0.2/bin/
And yes, the log calls
Upgrading to 7.0.2 resolved the issue, thanks!
-Original Message-
From: CRANFORD, CHRIS [mailto:chris.cranf...@setech.com]
Sent: Tuesday, August 17, 2010 10:23 AM
To: Tomcat Users List
Subject: RE: Destroying Context Listeners
Pid -
I will download the latest beta and give
I recently upgraded my Tomcat installation from 6.0.x to Tomcat 7
(Win64) and I am actively testing our current web applications for
backward compatibility, and so forth. One of these web applications
creates a set of context listeners to manage various things during the
lifecycle of the web
Theresa -
So far I haven't experienced any major issues with Tomcat 7. The only
open issue I have observed is that my ServletContextListener
implementation is not receiving the contextDestroyed() notification for
some strange reason. That's the only thing that is holding me off
pushing toward
11 matches
Mail list logo
