Hi Chris,
> > Yes, there's only the HTTP connector on port 8080. There's a load
> > balancer in front of this that handles HTTPS.
>
> If you connect the client directly to Tomcat, are you still able to
> reproduce the errors?
I have only seen the NPE thrown from CoyoteOutputStream.flush() in
prod
Michael,
On 1/17/25 4:21 PM, Michael wrote:
This sounds suspiciously like the application is keeping references to requests or
responses that have already been committed and recycled. Can you post your
configuration? In particular, what are the settings for the
discardFacades and discardRequ
> >> This sounds suspiciously like the application is keeping references to
> >> requests or responses that have already been committed and recycled. Can
> >> you post your configuration? In particular, what are the
> >> settings for the discardFacades and discardRequestsAndResponses attributes
> On Jan 17, 2025, at 12:45, Michael wrote:
>
> Thanks a lot for your comments, Chuck!
>
> On Fri, Jan 17, 2025 at 3:51 PM Chuck Caldarale wrote:
>>
>>
>>> On Jan 17, 2025, at 04:05, Michael wrote:
>>>
>>> I have two applications, A and B, running in Tomcat 10.1.28 on RHEL
>>> 8.10 with J
Thanks a lot for your comments, Chuck!
On Fri, Jan 17, 2025 at 3:51 PM Chuck Caldarale wrote:
>
>
> > On Jan 17, 2025, at 04:05, Michael wrote:
> >
> > I have two applications, A and B, running in Tomcat 10.1.28 on RHEL
> > 8.10 with Java 21 (OpenJDK Runtime Environment Red_Hat-21.0.5.0.10-1).
>
Hi Mark,
I'm not sure what you mean that the error is being reported client-side.
It is, yes, but the backend itself returns status 500 - so I guess
that's the reason Chrome gives net::ERR_HTTP2_PROTOCOL_ERROR. Or who
knows, I'm not sure. The relevant part from the log that I sent:
16:54:07.
Divyabharathi,
On 1/17/25 8:40 AM, Divyabharathi Sundaram wrote:
The client is disconnecting for some reason. What is the client? curl?
ant? Something else?
> We are trying to deploy the war file from browser
( eg: http://localhost:8080/Deploymanager)
Is that the Tomcat "manager" web applicat
James,
On 1/17/25 8:04 AM, James Matlik wrote:
When I'm talking about path parameters, it is in the context of how Open
API/Swagger defined them:
https://swagger.io/docs/specification/v3_0/describing-parameters/
Okay, that helps clear things up. In the URL specification (inherited by
HTTP) de
> On Jan 17, 2025, at 04:05, Michael wrote:
>
> I have two applications, A and B, running in Tomcat 10.1.28 on RHEL
> 8.10 with Java 21 (OpenJDK Runtime Environment Red_Hat-21.0.5.0.10-1).
You may want to try a newer version of 10.1; there have been several changes to
the Catalina and Coyote
Hi Christopher Schultz,
Please find the response inline below.
The client is disconnecting for some reason. What is the client? curl?
ant? Something else?
--->We are trying to deploy the war file from browser ( eg:
http://localhost:8080/Deploymanager)
Are you able to observe any errors from the cl
Mark,
When I'm talking about path parameters, it is in the context of how Open
API/Swagger defined them:
https://swagger.io/docs/specification/v3_0/describing-parameters/
The OS is AWS Linux running in a Docker container.
On Fri, Jan 17, 2025, 3:52 AM Mark Thomas wrote:
> James,
>
> A comment
I have two applications, A and B, running in Tomcat 10.1.28 on RHEL
8.10 with Java 21 (OpenJDK Runtime Environment Red_Hat-21.0.5.0.10-1).
Application uses an AsyncContext and SSE to send messages back to an
application running in a Chrome browser. Sometimes I get an NPE with
the following stacktra
James,
A comment and a question.
You are talking about the servlet path here. Path parameters are
something different
(.../path-segment;path-param-name=path-param-value/...)
Which operating system are you using?
Mark
16 Jan 2025 15:38:50 James Matlik :
Thank you for responding, Chris.
13 matches
Mail list logo
