Hmm, I'm now getting an A grade using:
If I'm sufficiently motivated next week, I'll see if I can sort out exactly what
the deal was. But for now, it's Friday and pau hana time...
(yes, tomcat 8.5.x and Java 1.8_x)
On Fri, May 11, 2018 at 07:39:25AM +0100, Mark Thomas wrote:
>On 11/05/18 0
>
> On 11/05/18 18:21, Максим Гумеров wrote:
> > Hi! I am running Tomcat 8 as part of Spring Boot application. As usual,
> > acceptCount defaults to 100 and maxThreads to 200. According to
> > https://tomcat.apache.org/tomcat-8.5-doc/config/http.html#NIO_specific_
> configuration
> > I am expecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 5/11/18 2:46 PM, Mark Thomas wrote:
> On 08/05/18 17:59, Christopher Schultz wrote:
>
>> This bites enough people that it may be worth correcting, or at
>> least changing the behavior when it happens.
>>
>> AJP already encodes the packet
On 11/05/18 18:21, Максим Гумеров wrote:
> Hi! I am running Tomcat 8 as part of Spring Boot application. As usual,
> acceptCount defaults to 100 and maxThreads to 200. According to
> https://tomcat.apache.org/tomcat-8.5-doc/config/http.html#NIO_specific_configuration
> I am expecting Tomcat to acce
On 08/05/18 17:59, Christopher Schultz wrote:
> This bites enough people that it may be worth correcting, or at least
> changing the behavior when it happens.
>
> AJP already encodes the packet-size in the header of each packet. Why
> not simply compare that to the MaxPacketSize on the Tomcat si
Hi! I am running Tomcat 8 as part of Spring Boot application. As usual,
acceptCount defaults to 100 and maxThreads to 200. According to
https://tomcat.apache.org/tomcat-8.5-doc/config/http.html#NIO_specific_configuration
I am expecting Tomcat to accept 200 "long" requests (each taking say 20
second
On 08/05/18 19:07, sri devops wrote:
> Hello Team,
>
> Currently I have apache-tomcat-8.5.23 installed and running on
> RHEL7.x86_64. I have a war deployed and application is running under
> tomcat. While application is running, if i make any manual changes to some
> config files [ context.xml or
On 04/05/18 12:50, Randy Oun wrote:
> As an update, the override code worked. Thanks for the guidance.
>
> Here is the code we packaged in a jar and place in the server lib:
>
> package company.catalina.realm;
>
> import java.security.Principal;
> import org.apache.catalina.realm.GenericPrincip
Also, Baron, about the URL you're testing on your site via by SSLLabs: is that
really one being served by Tomcat's web server? That's whose connector you're
showing here.
If instead you are fronting/proxying Tomcat with Apache or IIS, then my
understanding is that the SSL support is handled b
"Is there an easy way?" Depends on what you find easy. :-/
I usually just load old and new server.xml into a maximized Emacs with
two windows, and thoughtfully copy stuff over, after reading the
release notes to learn of stuff to look out for. Other configuration
I usually don't touch, and webap
On 11/05/18 12:28, Mark Thomas wrote:
> I do see some slightly odd behaviour in that the attributes are not
> replicated for the first session created after starting up the cluster.
> I'm currently looking in to what might be going wrong there.
The session created event was being processed in t
On 01/05/18 12:57, Stefan Hall wrote:
> Hi,
>
> I've probably read everything in the last few days and tried even more,
> but it won't work. I need your experience.
>
> First, my expectations of the Tomcat Cluster
> 1. session failover when a Tomcat dies (simulated via kill -9)
> 2. session fai
I don't think I saw any error messages at all in Tomcat. Just in the apache
logs. When I debugged I noticed an EOFException in the AJPProcessor. The
service method catches all type of IOExceptions and sets the error state but
doesn't log anything.
/Andreas
-Original Message-
From: Chr
13 matches
Mail list logo
