rBase.read(SocketWrapperBase.java:1323)
at
org.apache.tomcat.util.net.SocketWrapperBase.read(SocketWrapperBase.java:1295)
at
org.apache.coyote.http2.Http2AsyncParser.readFrame(Http2AsyncParser.java:138)
at
org.apache.coyote.http2.Http2Parser.readFrame(Http2Parser.java:71)
at
org.apache.coyote.http2.Http2UpgradeHandler.upgradeDispatch(Http2UpgradeHandler.java:346)
at
org.apache.coyote.http2.Http2AsyncUpgradeHandler.upgradeDispatch(Http2AsyncUpgradeHandler.java:41)
at
org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:60)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1747)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:834)
21-Feb-2022 17:36:38.550 FINE [ilm-https-jsse-nio-9080-exec-8]
org.apache.coyote.http2.Http2UpgradeHandler.upgradeDispatch Entry, Connection
[17], SocketStatus [ERROR]
21-Feb-2022 17:36:38.550 FINE [ilm-https-jsse-nio-9080-exec-8]
org.apache.coyote.http2.Http2UpgradeHandler.init Connection [17], State [CLOSED]
Thanks,
Kedar
-Original Message-
From: Mark Thomas
Sent: Monday, February 21, 2022 2:26 PM
To: users@tomcat.apache.org
Subject: Re: ERR_HTTP2_PROTOCOL_ERROR with Tomcat 9.0.58
External email from: users-return-274602-dkedar=ptc@tomcat.apache.org
On 21/02/2022 08:17, Deshmukh, Kedar wrote:
> Hello,
>
> We are consistently seeing error "ERR_HTTP2_PROTOCOL_ERROR" in browser
> console when we try to open any web page deployed on Tomcat 9.0.58 server in
> test environment. This issue is observed only when HTTP/2 is enabled.
> Otherwise, we do not see any issue with HTTP/1.1.
> Basically, we are assessing the possibility to switch to HTTP/2, however this
> issue is somehow blocking us.
>
> Enabled HTTP/2 with --> className="org.apache.coyote.http2.Http2Protocol"/>
>
> Is there any particular issue with HTTP/2 ?
No.
> Any additional configuration required at tomcat side to overcome it?
No.
Enable debug logging for HTTP/2 (see logging.properties), run the simplest test
that exhibits the problem and review the logs.
If the issue isn't clear from reviewing the logs, put the log file somewhere we
can download it and someone will take a look.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org