maxHttpHeaderSize only applies to Tomcat reading requests from clients.
It has no impact on the headers Tomcat sends to the client.
Given that the issue is size dependent and the the header is missing
only on the larger responses, I would guess that the Servlet is writing
the header after the
On 11/04/2021 11:03, Peter Chamberlain wrote:
I've been investigating this some more, as I'm not convinced nio2 isn't
behaving strangely in this case. I think there may of been some sort of
reversion as it is much less likely to refuse connections for nio2 in
tomcat 9.0.13 when compared to
On Mon, 12 Apr 2021, 09:07 Mark Thomas, wrote:
> On 11/04/2021 11:03, Peter Chamberlain wrote:
>
>
>
> > I've been investigating this some more, as I'm not convinced nio2 isn't
> > behaving strangely in this case. I think there may of been some sort of
> > reversion as it is much less likely to
Hi Konstantin,
thank you *very* much for your extremely helpful information, which gives me
quite something to
digest and think about!
Your remark about the JVM and loading a native library through one classloader
only makes me think
that it would not be possible at the moment to have two or
Thank you.
Can you suggest a way to confirm the problem is size related? Or are you
convinced by the numbers shown?
The client is a Java 15 app so there’s a chance I could use trailer headers.
I’m not explicitly using chunked encoding currently.
I don’t like the idea of buffering the entire
We are hosting our tomcats on windows vms behind a reverse proxy and have
enabled RemoteIPValve.
In the same time we have many hardware which talk to tomcat through a vpn.
Recently we updated our tomcats to a more recent version (8.5.43 to 8.5.53) and
our apps running on hardware through vpn had
Am 12.04.21 um 15:49 schrieb Bourdais Nicolas:
> We are hosting our tomcats on windows vms behind a reverse proxy and have
> enabled RemoteIPValve.
> In the same time we have many hardware which talk to tomcat through a vpn.
> Recently we updated our tomcats to a more recent version (8.5.43 to
> On Apr 12, 2021, at 8:43 AM, Rob Sargent wrote:
>
>
>
>
> Begin forwarded message:
>
>> From: Konstantin Kolinko
>> Date: April 12, 2021 at 8:38:14 AM MDT
>> To: Tomcat Users List
>> Subject: Re: Again with the missing headers
>> Reply-To: Tomcat Users List
>>
>> пн, 12 апр. 2021 г.
пн, 12 апр. 2021 г. в 16:50, Bourdais Nicolas
:
>
> We are hosting our tomcats on windows vms behind a reverse proxy and have
> enabled RemoteIPValve.
> In the same time we have many hardware which talk to tomcat through a vpn.
> Recently we updated our tomcats to a more recent version (8.5.43 to
> -Message d'origine-
> De : Felix Schumacher
> Envoyé : lundi 12 avril 2021 16:55
> À : users@tomcat.apache.org
> Objet : Re: RemoteIpValve resolving localname is really slow
>
>
> Am 12.04.21 um 15:49 schrieb Bourdais Nicolas:
> > We are hosting our tomcats on windows vms behind a
Hi there,
are there other comments on that? I'd like to implement this and want to
provide a CR On GitHub, if there is a fair chance, that this enhancement
will make it into Tomcat :)
Trying to summarize what has been discussed so far: (read the other
posts for more information)
The
> -Message d'origine-
> De : Konstantin Kolinko
> Envoyé : lundi 12 avril 2021 17:10
> À : users@tomcat.apache.org
> Objet : Re: RemoteIpValve resolving localname is really slow
>
> пн, 12 апр. 2021 г. в 16:50, Bourdais Nicolas
> :
> >
> > We are hosting our tomcats on windows vms behind
> On Apr 11, 2021, at 12:24 PM, Suvendu Sekhar Mondal wrote:
>
> Hi Chris,
>
>> On Sat, Apr 10, 2021 at 12:33 AM Chris Cheshire wrote:
>>
>> My googlefu is failing me here.
>>
>> I am trying to figure out some anomalous database connection behavior in my
>> tomcat web app. I have
пн, 12 апр. 2021 г. в 16:20, Rob Sargent :
>
> Thank you.
>
> Can you suggest a way to confirm the problem is size related? Or are you
> convinced by the numbers shown?
Look at "ServletResponse.isCommitted()"
пн, 12 апр. 2021 г. в 18:05, Rob Sargent :
> > [...]
>
> The datum of concern is handled via the session.
>
> //Hold the offset of the first explicit marker in the chased
> //segment. That marker at most 16th locus up-stream of
> //segment. Less at pter. There are more markers found within
Dana,
On 4/11/21 05:18, dana whitelow wrote:
Hi,I ran the migration tool against the sample.war
./migrate.sh sample.war webapp.war
Performing migration from source
[/home/dana/servers/jakartaee-migration-0.2.0/bin/sample.war] to destination
Dana,
On 4/10/21 16:34, dana whitelow wrote:
Thanks. I used the migration tool.
The problem is still there.
I believe this simple *.nix shell script can do a better job
grep -RiIl 'javax' | xargs sed -i 's/javax/jakarta/g'
That will migrate lots of APIs which haven't moved to Jakarta.
Mark,
On 4/12/21 04:16, Mark Thomas wrote:
maxHttpHeaderSize only applies to Tomcat reading requests from clients.
It has no impact on the headers Tomcat sends to the client.
Given that the issue is size dependent and the the header is missing
only on the larger responses, I would guess that
> On Apr 9, 2021, at 3:02 PM, Chris Cheshire wrote:
>
> My googlefu is failing me here.
>
> I am trying to figure out some anomalous database connection behavior in my
> tomcat web app. I have enabled JMX/RMI and have visualvm running on my local
> machine.
>
> I found the ability to
> On Apr 12, 2021, at 5:00 PM, Christopher Schultz
> wrote:
>
> Chris,
>
> On 4/12/21 12:50, Chris Cheshire wrote:
On Apr 9, 2021, at 3:02 PM, Chris Cheshire wrote:
>>> My googlefu is failing me here.
>>> I am trying to figure out some anomalous database connection behavior in my
Chris,
On 4/12/21 12:50, Chris Cheshire wrote:
On Apr 9, 2021, at 3:02 PM, Chris Cheshire wrote:
My googlefu is failing me here.
I am trying to figure out some anomalous database connection behavior in my
tomcat web app. I have enabled JMX/RMI and have visualvm running on my local
> On Apr 12, 2021, at 2:04 PM, Christopher Schultz
> wrote:
>
> Mark,
>
> On 4/12/21 04:16, Mark Thomas wrote:
>> maxHttpHeaderSize only applies to Tomcat reading requests from clients. It
>> has no impact on the headers Tomcat sends to the client.
>> Given that the issue is size dependent
I'm getting TC crashes (ver 8.5) with "out of memory" errors. I
understand heap space and the parameters to set it. But I need a bit of
help with "out of memory", not "out of heap space". This is running in
an EC2 on AWS. It's a development server, so activity is minimal
compared to
23 matches
Mail list logo
