How to resolve 'This stream is not writable' Tomcat error?
S
Stephanie Fourrier
a créé un sujet
presque 2 ans il y a
How to resolve 'This stream is not writable' Tomcat error?
Meilleure réponse
S
Stephanie Fourrier
a dit
presque 2 ans il y a
If you are seeing this stack trace in your PDE Log and have HTTP 2.0 configured on your Tomcat 9 server, you may be encountered an issue where the HTTP 2.0 connection closed due too much overhead.
org.apache.catalina.authenticator.FormAuthenticator.forwardToErrorPage Unexpected error forwarding to error page org.apache.catalina.connector.ClientAbortException: org.apache.coyote.CloseNowException: Connection [1031], Stream [11], This stream is not writable
To resolve the issue, you will need to set the overhead threshold to 0.
First Stop Tomcat
Edit the server.xml file to set the overhead threshold. Similar to this example.
If you are seeing this stack trace in your PDE Log and have HTTP 2.0 configured on your Tomcat 9 server, you may be encountered an issue where the HTTP 2.0 connection closed due too much overhead.
org.apache.catalina.authenticator.FormAuthenticator.forwardToErrorPage Unexpected error forwarding to error page org.apache.catalina.connector.ClientAbortException: org.apache.coyote.CloseNowException: Connection [1031], Stream [11], This stream is not writable
To resolve the issue, you will need to set the overhead threshold to 0.
First Stop Tomcat
Edit the server.xml file to set the overhead threshold. Similar to this example.
Stephanie Fourrier
How to resolve 'This stream is not writable' Tomcat error?
If you are seeing this stack trace in your PDE Log and have HTTP 2.0 configured on your Tomcat 9 server, you may be encountered an issue where the HTTP 2.0 connection closed due too much overhead.
To resolve the issue, you will need to set the overhead threshold to 0.
This should resolve the error message.
Stephanie Fourrier
If you are seeing this stack trace in your PDE Log and have HTTP 2.0 configured on your Tomcat 9 server, you may be encountered an issue where the HTTP 2.0 connection closed due too much overhead.
To resolve the issue, you will need to set the overhead threshold to 0.
This should resolve the error message.
-
xDM Compatibility with Java 17?
-
xDM on Docker
-
How to Upgrade Apache Tomcat?
-
Application Server Gives 404 Error
-
Amazon Aurora support
-
Change Prod Repository Type Without Reinstallation
-
Is It Possible to Import a V5.1.1 Data Model to V5.2.8?
-
"500 Internal Server Error" While Opening with Localhost
-
Enable Access to Azure File Storage?
-
Why am I getting Status 404 -- Not Found Error on Azure?
Voir tous les 27 sujets