Graham,
On 11/28/23 14:11, Graham Leggett wrote:
On 28 Nov 2023, at 18:42, Christopher Schultz
wrote:
In your debugger, when you break-on-exception, what happens if you allow the
exception to propagate up to the first exception-handler? Does Tomcat swallow
the exception? Or it it caught
Graham,
On 11/29/23 05:01, Graham Leggett wrote:
On 28 Nov 2023, at 21:10, Graham Leggett wrote:
So the reason we get a 400 Bad Request with no error detail is that we arrive
at this line with throwable set to null:
On 28 Nov 2023, at 21:10, Graham Leggett wrote:
> So the reason we get a 400 Bad Request with no error detail is that we arrive
> at this line with throwable set to null:
>
> https://github.com/apache/tomcat/blob/9.0.x/java/org/apache/catalina/valves/ErrorReportValve.java#L129
>
> With no
On 29 Nov 2023, at 07:18, Thomas Hoffmann (Speed4Trade GmbH)
wrote:
>> I’m in dependency hell - java8 to java17, JAXB as used by Jersey2 broke. No
>> idea why, but an internal Oracle implementation is hardcoded somewhere.
>>
>> java.lang.ClassNotFoundException:
Hello Graham,
> -Ursprüngliche Nachricht-
> Von: Graham Leggett
> Gesendet: Dienstag, 28. November 2023 20:12
> An: Tomcat Users List
> Betreff: Re: 400 Bad Request - where do I find the detailed reason for the
> bad request so I can fix it?
>
> On 28 Nov 202
On 28 Nov 2023, at 19:11, Graham Leggett wrote:
>> In your debugger, when you break-on-exception, what happens if you allow the
>> exception to propagate up to the first exception-handler? Does Tomcat
>> swallow the exception? Or it it caught elsewhere?
>
> The exception eventually ends up
On 28 Nov 2023, at 18:42, Christopher Schultz
wrote:
> In your debugger, when you break-on-exception, what happens if you allow the
> exception to propagate up to the first exception-handler? Does Tomcat swallow
> the exception? Or it it caught elsewhere?
The exception eventually ends up
Graham,
On 11/28/23 12:12, Graham Leggett wrote:
On 28 Nov 2023, at 09:41, Mark Thomas wrote:
What do I need to do to see the exception that generated the bad request, so
that I know specifically what’s wrong and can fix it?
Enabling debug logging for
On 28 Nov 2023, at 09:41, Mark Thomas wrote:
>> What do I need to do to see the exception that generated the bad request, so
>> that I know specifically what’s wrong and can fix it?
>
> Enabling debug logging for
>
> org.apache.coyote.http11.Http11Processor may help.
>
> It is probably the
On 27/11/2023 20:09, Graham Leggett wrote:
Hi all,
Long running webapps, tomcat recently updated from tomcat7 to tomcat v9.0.65.
One webapp sends a request to another.
The request fails with a 400 Bad Request, with the detail message "The server
cannot or will not process the request due to
Hi all,
Long running webapps, tomcat recently updated from tomcat7 to tomcat v9.0.65.
One webapp sends a request to another.
The request fails with a 400 Bad Request, with the detail message "The server
cannot or will not process the request due to something that is perceived to be
a client
11 matches
Mail list logo
