May I know the tomcat version please.
- It is apache-tomcat-8.0.41
-Original Message-
From: dku...@ccilindia.co.in [mailto:dku...@ccilindia.co.in]
Sent: 26 February 2020 19:01
To: 'Tomcat Users List'
Subject: Error parsing HTTP request header
Dear Team,
We are getting below error in cat
May I know the tomcat version please.
-Original Message-
From: dku...@ccilindia.co.in [mailto:dku...@ccilindia.co.in]
Sent: 26 February 2020 19:01
To: 'Tomcat Users List'
Subject: Error parsing HTTP request header
Dear Team,
We are getting below error in catelina log while starting the
On 26.02.2020 14:30, dku...@ccilindia.co.in wrote:
Dear Team,
We are getting below error in catelina log while starting the tomcat.
26-Feb-2020 18:57:36.795 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in 21520 ms
26-Feb-2020 18:57:38.277 INFO [http-nio-443-exec-11]
org
On 26/02/2020 13:30, dku...@ccilindia.co.in wrote:
> Dear Team,
>
> We are getting below error in catelina log while starting the tomcat.
>
> 26-Feb-2020 18:57:36.795 INFO [main]
> org.apache.catalina.startup.Catalina.start Server startup in 21520 ms
> 26-Feb-2020 18:57:38.277 INFO [http-nio-443
:
12/8/19 09:12 (GMT+05:30) To: Tomcat Users List Cc:
ch...@christopherschultz.net Subject: Re: Error parsing HTTP request header
Well this isn't an issue with Tomcat. I'm using an embedded version ofTomcat in
the BeAPI API Toolkit and this does not occur; mainly because itautomate
Well this isn't an issue with Tomcat. I'm using an embedded version of
Tomcat in the BeAPI API Toolkit and this does not occur; mainly because it
automates 100% of the api functionality. I would say it is most likely your
application.
How are you testing your app? You should be doing integration t
Hi Chris,
Thanks for trying to help here. As suggested I have checked the access logs
and find the below error line when ever the above exception occurs in
catalina.out.
"GET null null" 400 -
Thanks
Ram
On Wed, Dec 4, 2019 at 7:41 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ram,
On 12/4/19 06:02, thulasiram k wrote:
> Hi,
>
> we recently upgrade our tomcat from 7.0.91 to 7.0.94 in windows
> platform. Post upgrade we are seeing the below exception in logs
> very frequently. can you please suggest to avoid this.
>
> De
Thanks. I'll try the logging change to see if i can at least narrow it down
a bit more.
On Wed, Feb 21, 2018 at 7:49 PM, Konstantin Kolinko
wrote:
> 2018-02-21 22:19 GMT+03:00 Alex O'Ree :
> > That's the error message. The problem is I have no idea which client it
> is
> > and what character it
2018-02-21 22:19 GMT+03:00 Alex O'Ree :
> That's the error message. The problem is I have no idea which client it is
> and what character it is sending that is causing the issue. Thus I would
> like to get the offending header logged in some way.
The "http-nio-8080-exec-3" in the message is the th
On 21/02/18 19:19, Alex O'Ree wrote:
> That's the error message. The problem is I have no idea which client it is
> and what character it is sending that is causing the issue. Thus I would
> like to get the offending header logged in some way.
That sounds like an enhancement request for the log me
That's the error message. The problem is I have no idea which client it is
and what character it is sending that is causing the issue. Thus I would
like to get the offending header logged in some way.
On Tue, Feb 20, 2018 at 4:25 PM, Coty Sutherland
wrote:
> On Tue, Feb 20, 2018 at 4:01 PM, Alex
On Tue, Feb 20, 2018 at 4:01 PM, Alex O'Ree wrote:
> I keep running into the an IllegalArgumentException at or near startup of
> tomcat 8.5 with a bunch of cxf web services deployed and I have no idea
> what's causing it. The error message mentions turning on logging at the
> debug level.
Random
13 matches
Mail list logo