On Thu, Apr 26, 2018 at 10:15:03AM +0100, Mark Thomas wrote:
>On 26/04/18 02:37, Baron Fujimoto wrote:
>> We're working on upgrading from 8.0.x to 8.5.x in preparation for 8.0's
>> impending EOL.
>> Our initial 8.5 deployment which essentially uses our legacy server.xml SSL
>> connectors from 8.0
On 03/05/18 15:47, R Mundell wrote:
> I don’t believe it’s actually possible for the filters or the servlet to
> remove headers even if they want to (they don’t appear to have any access to
> the MimeHeaders of the Coyote “Response” object, and the HttpServletResponse
> object doesn’t have an
On 03/05/18 20:17, Mark Thomas wrote:
> On 02/05/18 16:08, Dirk Ooms wrote:
>> Mark,
>>
>> you can reproduce it using the FormAuthentication example in the
>> examples (http://localhost:8080/examples/jsp/security/protected/)
>>
>> edit index.jsp
>> 1. add the line "RequestURI: <%= request.getReques
On 02/05/18 16:08, Dirk Ooms wrote:
> Mark,
>
> you can reproduce it using the FormAuthentication example in the
> examples (http://localhost:8080/examples/jsp/security/protected/)
>
> edit index.jsp
> 1. add the line "RequestURI: <%= request.getRequestURI() %>" in
> begin of body
> 2. change the
Hello Martin,
If you use the default tomcat logging [1] probably setting
org.apache.catalina.ha.level = FINE or FINEST
in your $CATALINA_BASE/conf/logging.properties will give you the
information you need.
Hope it helps,
Luis
[1] https://tomcat.apache.org/tomcat-7.0-doc/logging.html
2
Attention Tomcat developers who know how the Coyote bit of Tomcat works… I’ve
got a tricky one for you! :-)
We’re struggling with a puzzling problem where intermittently, calls to a
servlet are delivered back to the client with all of the headers missing except
the ones that Coyote adds.
In ro
Hi,
one question on Tomcat HA clustering. Is there a way (e.g. a log file
pattern to look for) to find out that a sessions activity has actually been
transfered to another cluster node? We are operating a productive
environment with 6 clustered TC processes and we would like to know how
oftenthe
Ah, I see!
Thank you very much for the quick and helpful answer!
/Andreas
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: den 3 maj 2018 13:37
To: Tomcat Users List
Subject: Re: Changing the packetSize in AJP connector causes 503 Internal
Server Error in Tomcat 9
On 03/05/18 10:59, Andreas Bergander wrote:
> Thank's for investigating Mark!
>
> I think it's only possible to change the packet size in mod_jk, not in
> mod_proxy_ajp, right?
Wrong.
ProxyIOBufferSize
Mark
> So either we need to switch to mod_jk or stick with a packet size of 8192.
>
> A bit
Thank's for investigating Mark!
I think it's only possible to change the packet size in mod_jk, not in
mod_proxy_ajp, right? So either we need to switch to mod_jk or stick with a
packet size of 8192.
A bit strange though that it worked fine in Tomcat 8.5, maybe it adapted to
httpd and still us
On 03/05/18 10:36, Mark Thomas wrote:
> On 03/05/18 09:48, Andreas Bergander wrote:
>> Hi,
>>
>> I've upgrade from Tomcat 8.5 to 9.0.7 and I've got an issue regarding the
>> packet size in the AJP connector. It seems like only the default value
>> (8192) works now. If I set it to anything greater
On 03/05/18 09:48, Andreas Bergander wrote:
> Hi,
>
> I've upgrade from Tomcat 8.5 to 9.0.7 and I've got an issue regarding the
> packet size in the AJP connector. It seems like only the default value (8192)
> works now. If I set it to anything greater than that I'll get 503 Internal
> Server E
Hi,
I've upgrade from Tomcat 8.5 to 9.0.7 and I've got an issue regarding the
packet size in the AJP connector. It seems like only the default value (8192)
works now. If I set it to anything greater than that I'll get 503 Internal
Server Error when trying to access a web page. It worked fine in
13 matches
Mail list logo
