https://bz.apache.org/bugzilla/show_bug.cgi?id=65565
Bug ID: 65565
Summary: Tomcat responds with HTTP status code 503 with
response body upstream connect error or
disconnect/reset before headers. reset reason: remote
refused stream reset
Product: Tomcat 9
Version: 9.0.52
Hardware: All
OS: All
Status: NEW
Severity: blocker
Priority: P2
Component: WebSocket
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
Hello, I have following configuration setup in my production environment:
Java Application with following configuration:
1. Sprint boot server version 2.5.4
2. Tomcat version 9.0.52
3. Inside our Application we have enabled HTTP 2 version by using following
bean code
```
@Bean
public TomcatConnectorCustomizer customizer() {
return (connector) -> connector.addUpgradeProtocol(new Http2Protocol());
}
```
4. All the other Spring boot and Tomcat configuration/properties are default
5. Running this Application as docker container (using base image of alpine) on
cloud in which we have installed tomcat-native which has following libs
https://pkgs.alpinelinux.org/contents?branch=edge&name=tomcat-native&arch=x86&repo=community
Issue faced: When the client call this java application, it receives HTTP
status code 503 with response body as "upstream connect error or
disconnect/reset before headers. reset reason: remote refused stream reset"
They happen almost 2-3 times in an hour with normal load
We didnt get these errors while using HTTP 1 but have started to notice this
issue when we upgraded Tomcat to use HTTP 2
We also enabled internal logs for tomcat to be printed by using these
application property
logging.level.org.apache.tomcat=ERROR
logging.level.org.apache.catalina=ERROR
but no additional information was printed out when we get this error.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
