Hi,
I have profiled the application using JProfiler,and it seems to me that its my
servlet which is taking the majority of time.
Though the time is in mili seconds,but I guess since the servlet is code is
same as with Tomcat 6.0.18 is it the Servlet 3.0 API which is causing the
reduced
On 20/05/2013 01:41, Martin Gainty wrote:
Hi Jesse
Jesse - please ignore Martin's reply. As usual, he is talking nonsense.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
On 19/05/2013 17:39, jieryn wrote:
Greetings,
I am using Apache Tomcat 7.0.40, via IBM Java 7 SR2. I am seeing the
following on Tomcat shutdown:
org.apache.catalina.loader.WebappClassLoader.checkThreadLocalMapForLeaks
The web application [] created a ThreadLocal with key of type
On 20/05/2013 06:59, Chirag Dewan wrote:
Hi,
I have profiled the application using JProfiler,and it seems to me
that its my servlet which is taking the majority of time.
Though the time is in mili seconds,but I guess since the servlet is
code is same as with Tomcat 6.0.18 is it the
Greetings,
On Mon, May 20, 2013 at 4:17 AM, Mark Thomas ma...@apache.org wrote:
Tomcat is not responsible for any ThreadLocals your application creates.
If your application creates them (or causes them to be created), your
application needs to clean them up.
Ok, I understand.
Depending on
On May 18, 2013, at 11:37 AM, James Snider wrote:
-Original Message-
From: Daniel Mikusa [mailto:dmik...@gopivotal.com]
Sent: Saturday, May 18, 2013 10:24 AM
To: Tomcat Users List
Subject: Re: Apache Tomcat service has been shutting down/stopping randomly.
On May 17, 2013, at
2013/5/19 jieryn jie...@gmail.com:
Greetings,
I am using Apache Tomcat 7.0.40, via IBM Java 7 SR2. I am seeing the
following on Tomcat shutdown:
org.apache.catalina.loader.WebappClassLoader.checkThreadLocalMapForLeaks
The web application [] created a ThreadLocal with key of type
HI,
We completely uninstalled/removed all previous Tomcat 5.5 versions from the
file system and registry, rebooted, then completed a clean re-install without
copying back any of the folders that could be causing issues as you have stated
below. We are still receiving this error and Apache
2013/5/20 James Snider james.sni...@hbcs.org:
HI,
We completely uninstalled/removed all previous Tomcat 5.5 versions from the
file system and registry, rebooted, then completed a clean re-install without
copying back any of the folders that could be causing issues as you have
stated
Hi,
when first reporting this issue I was mistaken about the configuration.
Although we use an older tomcat version, the tomcat-jdbc is pulled into our
application as a separate dependency. I have upgraded it to newest version
(7.0.39) and still see similar exception happening:
2013/5/19 Nick Williams nicho...@nicholaswilliams.net:
On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat
shutdown (memory leak, it looks like)
Log4j 1
I ran my test client on Hello World example servlet on Tomcat 7.0.30. It was
12K req/sec with 80% CPU utilization.
The same test case on tomcat 6.0.18 gave me similar req/sec but CPU utilization
of 70% . The results on my linux server,with client and server running on the
same machine. But
Please see below the tomcat7-stderr.2013-05-20.log regarding the memory leak.
2013-05-20 09:41:34 Commons Daemon procrun stderr initialized May 20, 2013
9:41:35 AM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.27 using APR version
From: Anil Goyal -X (anigoyal - Aricent Technologies at Cisco)
Sent: Monday, May 20, 2013 8:01 PM
To: Tomcat Users List
Subject: redirect valve in tomcat
Hi All,
I am adding a new service in tomcat with name catalina_new and deploy an
abc application under this.
This application was in
Hi All,
I am adding a new service in tomcat with name catalina_new and deploy an
abc application under this.
This application was in running under catalina service previously.
This new service is using connector port 8181 for http and 8444 for https.
Now I want all my request coming for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/19/13 11:25 AM, Nick Williams wrote:
Unfortunately, requiring users to call System.gc() before shutdown
for logging to work properly is no better than requiring users to
register a listener in a web application for logging to work
On May 20, 2013, at 10:17 AM, Tomasz Kowalczewski wrote:
Hi,
when first reporting this issue I was mistaken about the configuration.
Although we use an older tomcat version, the tomcat-jdbc is pulled into our
application as a separate dependency. I have upgraded it to newest version
On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/19/13 11:25 AM, Nick Williams wrote:
Unfortunately, requiring users to call System.gc() before shutdown
for logging to work properly is no better than requiring users to
On May 20, 2013, at 10:51 AM, James Snider wrote:
Please see below the tomcat7-stderr.2013-05-20.log regarding the memory leak.
snip
May 20, 2013 9:52:51 AM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread
Greetings,
On Mon, May 20, 2013 at 9:45 AM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
2013/5/19 jieryn jie...@gmail.com:
$ grep com.sun.xml.bind.v2.runtime.Coordinator *
Binary file jaxb-impl-2.2.1.1.jar matches
Apache Maven dependency:tree shows that this is coming from Apache
Wink
Dan/Konstantine,
Our web application was fine until the Tomcat 7 installation. So this make no
sense to us that we would look at our application as the issue.
Can you please explain wjhy this would be occurring now and not in the past in
more detail.
Thanks,
James
-Original
On May 20, 2013, at 1:47 PM, James Snider wrote:
Dan/Konstantine,
Our web application was fine until the Tomcat 7 installation. So this make no
sense to us that we would look at our application as the issue.
Your application has very likely been doing this all along.
Can you please
Our application was working prior to the detection being added. Is there a way
to turn of the detection and keep our applications running?
We may have been having this memory leak issue previously but it wasn't
causing this random service stoppage.
-Original Message-
From: Daniel
On May 20, 2013, at 2:10 PM, James Snider wrote:
Our application was working prior to the detection being added. Is there a
way to turn of the detection and keep our applications running?
We may have been having this memory leak issue previously but it wasn't
causing this random
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sascha,
On 5/17/13 7:22 AM, Sascha Troll wrote:
Can you give me a hint. I am just the server guy, so I can tell the
developer.
Tell the developers to set connection- and read-timeouts when using
HttpClient (or whatever uses HttpClient). They
Is there any way to use the Tomcat maven plugin with Tomcat 8 (i.e. trunk
snapshots)? The documentation lists how to configure Tomcat 6 and 7 only
[1].
Rossen
[1] http://tomcat.apache.org/maven-plugin-trunk/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 5/20/13 2:10 PM, James Snider wrote:
Our application was working prior to the detection being added.
Is there a way to turn of the detection and keep our applications
running?
Your application is probably still working.
We may have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 12:48 PM, Nick Williams wrote:
On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/19/13 11:25 AM, Nick Williams wrote:
Unfortunately, requiring users to
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Apache Tomcat service has been shutting down/stopping randomly.
Third, let's get some more information about the tcnative thing, as it
probably truly represents a bug in tcnative.
And start a new thread for that
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 12:48 PM, Nick Williams wrote:
On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/19/13
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/20/13 12:48 PM, Nick Williams wrote:
On May 20, 2013, at 10:56 AM,
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/20/13
On 5/20/2013 2:45 PM, Nick Williams wrote:
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
33 matches
Mail list logo
