dot fixes
the problem.
However, this does seem to be a difference in the behavior of Tomcat 8.0
and 8.5, It should probably be mentioned in
https://tomcat.apache.org/migration-85.html.
On Mon, Aug 29, 2016 at 2:35 AM, Mark Thomas wrote:
> On 29/08/2016 03:09, Mike Wertheim wrote:
>
I don't see any such errors in the logs.
Did cookie validation change between Tomcat 8.0 and Tomcat 8.5, or would
you expect them to behave identically?
On Mon, Aug 29, 2016 at 2:35 AM, Mark Thomas wrote:
> On 29/08/2016 03:09, Mike Wertheim wrote:
> > I took a look using the L
6:10 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mike,
>
> On 8/27/16 8:44 PM, Mike Wertheim wrote:
> > I've found a difference in behavior between Tomcat 8.0.33 and
> > Tomcat 8.5
I've found a difference in behavior between Tomcat 8.0.33 and Tomcat 8.5.4.
Here's the setup...
I have some Tomcat servers behind an F5 load balancer. There are two
top-level domains (which I'll call domain1.com and domain2.com) pointing to
the load balancer. In addition, there is a separate se
drom_apache/certs/dev-apr.pem"
>SSLCertificateKeyFile="/opt/_cdrom_apache/certs/key.pem"
>SSLCACertificateFile="/opt/_cdrom_apache/certs/CA.pem"
>/>
>
> I hope this will work for you.
>
> Regards,
>
I should have included this in the previous message.
The AprLifecycleListener is declared in server.xml like this:
On Wed, Dec 17, 2014 at 5:12 PM, Mike Wertheim wrote:
>
> I'm trying to upgrade from Tomcat 7.0.41 with APR to Tomcat 8.0.15 with
> APR. (I'm using JDK
I'm trying to upgrade from Tomcat 7.0.41 with APR to Tomcat 8.0.15 with
APR. (I'm using JDK 1.8.0.25 on CentOS.)
My first step was to upgrade to Tomcat Native library 1.1.32 and APR 1.5.1
while still using Tomcat 7.0.41. This combination works great. My webapp
starts up and is accessible using
The change log for Tomcat 7.0.25 contains this entry:
"Correct error in fix for 49683. (markt)"
Is this bug fix expected to fix the file descriptor leak that was
reported in Tomcat 7.0.23?
-
To unsubscribe, e-mail: users-unsubscr
Has a bug been logged for this issue (what seems to be a file descriptor leak)?
On Tue, Jan 3, 2012 at 1:17 PM, Mark Thomas wrote:
> I am trying to bring together all the information I have gleaned on this
> so far from the multiple threads to try and find the common factors.
>
> So far I have:
>
On Tue, Jan 3, 2012 at 1:17 PM, Mark Thomas wrote:
> I am trying to bring together all the information I have gleaned on this
> so far from the multiple threads to try and find the common factors.
>
> So far I have:
> - 7.0.21 is OK
> - 7.0.22 has an fd leak
> - 7.0.23 has an fd leak and may leak
On Mon, Jan 2, 2012 at 6:55 PM, Mike Wertheim wrote:
> On Mon, Jan 2, 2012 at 3:09 PM, Christopher Schultz
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Mike,
>>
>> On 12/29/11 9:01 PM, Mike Wertheim wrote:
>>> I did a stac
On Mon, Jan 2, 2012 at 3:09 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mike,
>
> On 12/29/11 9:01 PM, Mike Wertheim wrote:
>> I did a stack dump on 7.0.23 when it was in its messed up state.
>> No threads are blocked
On Mon, Jan 2, 2012 at 4:31 PM, Konstantin Kolinko
wrote:
> 2011/12/31 Janne Jalkanen :
>> Hi all!
>>
>> I am seeing odd behaviour with 7.0.23, with the tomcat user's open file
>> count increasing slowly, but consistently. Two other instances running the
>> exact same codebase on identical hardw
If a simple test case isn't discovered, I'm happy to test out
potential fixes (by deploying the fixes to one of my production
servers and seeing whether or not the server dies after running for a
day).
On Sun, Jan 1, 2012 at 7:17 AM, wrote:
> Janne Jalkanen wrote:
>
>>APR + native. Good catch t
On Sat, Dec 31, 2011 at 12:53 PM, Pid * wrote:
> On 31 Dec 2011, at 16:14, Mike Wertheim wrote:
>
>> I'm using the APR Connector.
>>
>> Here's my server.xml:
>>
>>
>>
>>
>> > SSLEngine="on" />
>>
>
7.0.21 and 7.0.22, keeping an eye out for
anything that could be causing a file leak.
On Sat, Dec 31, 2011 at 11:17 AM, Pid * wrote:
> On 31 Dec 2011, at 18:19, Mike Wertheim wrote:
>
>> I'm not sure how useful this comment is, but... I also recently
>> posted about an app th
I'm not sure how useful this comment is, but... I also recently
posted about an app that runs fine on Tomcat 7.0.21 and dies a slow
horrible death on Tomcat 7.0.23. It would seem that a bug was
introduced in either 7.0.22 or 7.0.23.
On Sat, Dec 31, 2011 at 6:48 AM, André Warnier wrote:
> Jann
I'm using the APR Connector.
Here's my server.xml:
On Sat, Dec 31, 2011 at 5:39 AM, Pid wrote:
> On 30/12/2011 02:01, Mike Wertheim wrote:
>> I have an app that runs on Tomcat 7
I have an app that runs on Tomcat 7.0.21 and APR 1.4.7 just fine. The
app serves both SSL and non-SSL traffic. SSL traffic makes up roughly
1% of the overall traffic. The Connectors for SSL and non-SSL both
use the default value (200) for maxThreads.
When I try to run the app on Tomcat 7.0.23 (
t DSL
connection or cable connection, could I get away with reducing it to
perhaps to 2 seconds, or just 1 second?
On Fri, Dec 16, 2011 at 8:20 AM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: mike.werth...@gmail.com [mailto:mike.werth...@gmail.com] On
&
In my server.xml, I have this line which turns on APR:
And the Connectors look like this:
With this configuration, can I assume that the Connector that I'm using is
the APR/native Connector (the 3rd one in the Connector Comparison table)?
On Fri, Dec 16, 2011 at 5:21 AM, Caldarale,
I have a Java app running on Tomcat 7.0.21 with APR 1.4.7. The app runs on
64-bit Java 7 Update 1 on CENT OS servers, with an A10 load balancer that
sends traffic to the servers. On average, each server is handling about 80
requests per second.
We are having problems with our network connections
3 (70%)
Number of those file descriptors that have filename with "eventpoll": 5579 (29%)
On Tue, Nov 29, 2011 at 3:04 PM, Caldarale, Charles R
wrote:
>> From: mike.werth...@gmail.com [mailto:mike.werth...@gmail.com] On Behalf Of
>> Mike Wertheim
>> Subject: Re: increase
descriptors but
fewer active connections.
Does this info help? Is there anything else I can tell you?
Any idea in what changed between 7.0.21 and 7.0.23 that could account for this?
Thanks!
Mike
On Tue, Nov 29, 2011 at 12:35 AM, Pid * wrote:
> On 29 Nov 2011, at 01:05, Mike Wertheim wrot
I have a web app that has been running on Tomcat 7.0.21 with APR 1.4.2
and Tomcat Native 1.1.20 on 64-bit Java 1.6.0.23 on CentOS Linux.
I upgraded half of my servers to Tomcat 7.0.23 and left the other half
at 7.0.21. I copied the modified server.xml, context.xml and web.xml
files from the 7.0.2
I have a webapp running on Tomcat 6.0.16 under Red Hat 4 Linux (version
2.6.22.7).
99% of the time it runs fine. But every once in a while, one of the JSP
pages (that was working just fine) will stop working. When I try to access
that JSP, Tomcat gets a JasperException, with this root cause except
26 matches
Mail list logo
