How to resolve 'This stream is not writable' Tomcat error?
S
Stéphanie FOURRIER
started a topic
over 4 years ago
How to resolve 'This stream is not writable' Tomcat error?
Best Answer
S
Stéphanie FOURRIER
said
over 4 years ago
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.
Stéphanie 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.
Stéphanie 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 on Docker
-
Application Server Gives 404 Error
-
Change Prod Repository Type Without Reinstallation
-
Enable Access to Azure File Storage?
-
Why am I getting Status 404 -- Not Found Error on Azure?
-
Resolve "Unable to Create Work Directory" Error
-
What's the default font for Semarchy application?
-
Plain Text Password in Tomcat Config Files
-
How Can I Resolve "CREATE TABLE permission denied" error in SQL Server?
See all 16 topics