I got an error [1] running unit tests.  Will run it again in case it's just
a fluke or a fragile test case.

Igal

[1] Testcase: testExceedMaxActiveStreams02[0] took 0.282 sec
        Caused an ERROR
End of input stream
java.io.IOException: End of input stream
        at
org.apache.coyote.http2.Http2TestBase$TestInput.fill(Http2TestBase.java:979)
        at
org.apache.coyote.http2.Http2Parser$Input.fill(Http2Parser.java:707)
        at
org.apache.coyote.http2.Http2Parser.readFrame(Http2Parser.java:78)
        at
org.apache.coyote.http2.Http2Parser.readFrame(Http2Parser.java:71)
        at
org.apache.coyote.http2.TestHttp2Section_5_1.testExceedMaxActiveStreams02(TestHttp2Section_5_1.java:303)
        at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
        at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

07-Oct-2020 14:19:13.286 FINE [http-nio-127.0.0.1-auto-6-exec-4]
org.apache.coyote.http2.Http2UpgradeHandler.upgradeDispatch Connection error
        org.apache.coyote.http2.ConnectionException: There was an error
during the HPACK decoding of HTTP headers
                at
org.apache.coyote.http2.Http2Parser.readHeaderPayload(Http2Parser.java:488)
                at
org.apache.coyote.http2.Http2Parser.readHeadersFrame(Http2Parser.java:269)
                at
org.apache.coyote.http2.Http2AsyncParser$FrameCompletionHandler.completed(Http2AsyncParser.java:249)
                at
org.apache.coyote.http2.Http2AsyncParser$FrameCompletionHandler.completed(Http2AsyncParser.java:164)
                at
org.apache.tomcat.util.net.SocketWrapperBase$VectoredIOCompletionHandler.completed(SocketWrapperBase.java:1087)
                at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper$NioOperationState.run(NioEndpoint.java:1511)
                at
org.apache.tomcat.util.net.SocketWrapperBase$OperationState.start(SocketWrapperBase.java:1039)
                at
org.apache.tomcat.util.net.SocketWrapperBase.vectoredOperation(SocketWrapperBase.java:1450)
                at
org.apache.tomcat.util.net.SocketWrapperBase.read(SocketWrapperBase.java:1293)
                at
org.apache.tomcat.util.net.SocketWrapperBase.read(SocketWrapperBase.java:1265)
                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:339)
                at
org.apache.coyote.http2.Http2AsyncUpgradeHandler.upgradeDispatch(Http2AsyncUpgradeHandler.java:40)
                at
org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54)
                at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
                at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
                at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
                at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
                at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
                at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
                at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
                at java.base/java.lang.Thread.run(Thread.java:834)
        Caused by: org.apache.coyote.http2.HpackException: Connection [5],
Stream [5], received multiple [:method] headers
                at
org.apache.coyote.http2.Stream.emitHeader(Stream.java:329)
                at
org.apache.coyote.http2.HpackDecoder.emitHeader(HpackDecoder.java:431)
                at
org.apache.coyote.http2.HpackDecoder.addStaticTableEntry(HpackDecoder.java:300)
                at
org.apache.coyote.http2.HpackDecoder.handleIndex(HpackDecoder.java:267)
                at
org.apache.coyote.http2.HpackDecoder.decode(HpackDecoder.java:111)
                at
org.apache.coyote.http2.Http2Parser.readHeaderPayload(Http2Parser.java:485)
                ... 22 more


On Wed, Oct 7, 2020 at 2:15 PM Raymond Auge
<raymond.a...@liferay.com.invalid> wrote:

> On Tue, Oct 6, 2020 at 10:49 AM Mark Thomas <ma...@apache.org> wrote:
>
> > The proposed Apache Tomcat 9.0.39 release is now available for voting.
> >
> > The notable changes compared to the 9.0.38 release are:
> >
> > - Refactor the handling of closed HTTP/2 streams to reduce the heap
> >   usage associated with used streams and to retain information for more
> >   streams in the priority tree.
> >
> > - Allow using the utility executor for annotation scanning. Patch
> >   provided by Jatin Kamnani.
> >
> > - Add a bloom filter to speed up archive lookup and improve deployment
> >   speed of applications with a large number of JARs. Patch provided by
> >   Jatin Kamnani.
> >
> > Along with lots of other bug fixes and improvements.
> >
> > For full details, see the changelog:
> > https://ci.apache.org/projects/tomcat/tomcat9/docs/changelog.html
> >
> > It can be obtained from:
> > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.39/
> > The Maven staging repo is:
> > https://repository.apache.org/content/repositories/orgapachetomcat-1281/
> > The tag is:
> > https://github.com/apache/tomcat/tree/9.0.39
> > 6989c4e9360b4f9443862968c15a95d17f264321
> >
> > The proposed 9.0.39 release is:
> > [ ] Broken - do not release
> > [X] Stable - go ahead and release as 9.0.39
> >
>
> - Ray
>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: dev-h...@tomcat.apache.org
> >
> >
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
>

Reply via email to