I agree, this seems to be a regression. The package was incorrectly
built with Java 10 previously, but this was fixed as part of #895866.
Apparently, the problem seems to have reappeared. Verified with Java
1.8.0_181-8u181-b13-1-b13 (package list below).
ii openjdk-8-jdk-headless:amd64 8u181-b13-1
amd64 OpenJDK Development Kit (JDK) (headless)
ii openjdk-8-jre:amd64 8u181-b13-1
amd64 OpenJDK Java runtime, using Hotspot JIT
ii openjdk-8-jre-headless:amd64 8u181-b13-1
amd64 OpenJDK Java runtime, using Hotspot JIT (headless)
For reference, here is the stack trace:
<2>Error reading request, ignored
<2>java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
<2> at
org.apache.coyote.http11.Http11InputBuffer.init(Http11InputBuffer.java:696)
<2> at
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:669)
<2> at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
<2> at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:800)
<2> at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1471)
<2> at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
<2> at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
<2> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
<2> at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
<2> at java.lang.Thread.run(Thread.java:748)
