Hi
is there a way to externally influence the switch between versions with
the new parallel deployment method. As I understand it tomcat
automatically switches to the new version for new requests as soon as
the context with the new version is started. Instead I would like to
manually control wich
Hi,
An instance running tomcat 6.0.24 as root in our developer network was
compromised today by a scanning bot which deployed a war file and then
deleted the on disk file, before scanning for new hosts until the IDS
detected it.
Obviously this is not a flaw in tomcat, but I was hoping someon
On 11 Apr 2012, at 14:42, Lazar Kirchev wrote:
> ServletContainerInitializer
Only exists in Servlet 3.0. Supporting it in lower spec versions would
be non-compliant.
And silly.
p
-
To unsubscribe, e-mail: users-unsubscr...@t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke,
On 4/11/12 5:17 PM, Luke Meyer wrote:
> Just noticed what I was missing about connectionTimeout - it's the
> default for keepAliveTimeout. So, that clears that up.
>
> Still don't think it's a "huge negative performance impact!" to
> disable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ashima,
On 4/11/12 4:27 PM, Ashima Sharma wrote:
> Most of the jsps have this issue...but it happens randomly. For
> e.g., i wd be able to access the registration page 5 times w/o any
> issue, and the 6th time I'd get this error. Its bizarre that tomc
Just noticed what I was missing about connectionTimeout - it's the default for
keepAliveTimeout. So, that clears that up.
Still don't think it's a "huge negative performance impact!" to disable
connection reuse.
- Original Message -
From: "Luke Meyer"
To: users@tomcat.apache.org
Sent:
Most of the jsps have this issue...but it happens randomly. For e.g., i wd
be able to access the registration page 5 times w/o any issue, and the 6th
time I'd get this error.
Its bizarre that tomcat tries to recompile the already compiled jsp at some
random point even though the page hasn't changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ashima,
On 4/11/12 11:05 AM, Ashima Sharma wrote:
> We just did a tomcat upgrade (from 6.0.36 to 7.0.26) for a legacy
> struts-1.3.10 app on Windows 2008 R2 (64-bit). Ever since, there's
> been an intermittent occurence of the following 2 exceptions
We just did a tomcat upgrade (from 6.0.36 to 7.0.26) for a legacy
struts-1.3.10 app on Windows 2008 R2 (64-bit).
Ever since, there's been an intermittent occurence of the following 2
exceptions (for random jsps) -
*2012-04-10 18:27:45,751 ERROR [org.apache.struts.tiles.taglib.InsertTag] -
ServletE
On Wed, Apr 11, 2012 at 3:54 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Lazar Kirchev [mailto:lazar.kirc...@gmail.com]
> > Subject: Re: Using ServletContainerInitializer for 2.5 applications
>
> > I want the ServletContainerInitializer to be called for all applications
"http-443-205" daemon prio=10 tid=0x096a8400 nid=0x2a04 runnable
[0x3089d000..0x3089e130]
java.lang.Thread.State: RUNNABLE
at org.apache.tomcat.jni.Socket.sendbb(Native Method)
at
org.apache.coyote.http11.InternalAprOutputBuffer.flushBuffer(InternalAprOutputBuffer.
> From: Lazar Kirchev [mailto:lazar.kirc...@gmail.com]
> Subject: Re: Using ServletContainerInitializer for 2.5 applications
> I want the ServletContainerInitializer to be called for all applications I
> deploy, not only with web.xml version 3.0, but also with lower version. Is
> this possible?
2012/4/11 Lazar Kirchev :
> I want the ServletContainerInitializer to be called for all applications I
> deploy, not only with web.xml version 3.0, but also with lower version. Is
> this possible?
1. Do not top post. Write answers below the questions.
2. You would even be able to load the class t
I want the ServletContainerInitializer to be called for all applications I
deploy, not only with web.xml version 3.0, but also with lower version. Is
this possible?
On Wed, Apr 11, 2012 at 3:17 PM, Mikolaj Rydzewski wrote:
> On 11.04.2012 14:10, Lazar Kirchev wrote:
>
> In servlet 3.0 specifica
On 11.04.2012 14:10, Lazar Kirchev wrote:
In servlet 3.0 specification ServletContainerInitilizer class is
defined to
allow programatic addition of servlet/filters/listeners. I am using a
ServletContextInitializer to add a ServletContextListener to the
ServletContext. I use Tomcat 7.0.25. This
Hello,
In servlet 3.0 specification ServletContainerInitilizer class is defined to
allow programatic addition of servlet/filters/listeners. I am using a
ServletContextInitializer to add a ServletContextListener to the
ServletContext. I use Tomcat 7.0.25. This works fine if the web.xml major
versio
Pid wrote:
>On 11/04/2012 03:47, Peter wrote:
>> hey Christopher,
>>
>> the app I used that uncovered the issue is one I use exclusively to
>validate tomcat releases;) it is a "hello world" style app using
>spring/servlet3.0. it has simple spring aop point cutting via jamon ,
>simple spring jm
On 11/04/2012 03:47, Peter wrote:
> hey Christopher,
>
> the app I used that uncovered the issue is one I use exclusively to validate
> tomcat releases;) it is a "hello world" style app using spring/servlet3.0. it
> has simple spring aop point cutting via jamon , simple spring jms (active mq)
>
For those who interested I opened Bug 53061 for this issue
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Tuesday, April 10, 2012 10:52 AM
To: Tomcat Users List
Subject: RE: tomcat asynchronous invocation problem
Vyacheslav Trainin wrote:
>I reproduced it on:
>
19 matches
Mail list logo
