Mark, On Sat, Dec 6, 2025 at 6:12 PM Igal Sapir <[email protected]> wrote:
> Mark, > > On Tue, Dec 2, 2025 at 10:12 AM Mark Thomas <[email protected]> wrote: > >> The proposed Apache Tomcat 11.0.15 release is now available for voting. >> >> The notable changes compared to 11.0.14 include: >> >> - Add strictSNI attribute on the Connector to allow matching the >> SSLHostConfig configuration associated with the SNI host name to the >> SSLHostConfig configuration matched from the HTTP protocol host name. >> Non matching configurations will cause the request to be rejected. The >> attribute default value is true, enabling the matching. >> >> - Correct a regression introduced in 11.0.11 that broke some clustering >> configurations. >> >> - Update Commons Daemon to 1.5.0. >> >> For full details, see the change log: >> https://nightlies.apache.org/tomcat/tomcat-11.0.x/docs/changelog.html >> >> Applications that run on Tomcat 9 and earlier will not run on Tomcat 11 >> without changes. Java EE applications designed for Tomcat 9 and earlier >> may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat >> will automatically convert them to Jakarta EE and copy them to the >> webapps directory. Applications using deprecated APIs may require >> further changes. >> >> It can be obtained from: >> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-11/v11.0.15/ >> >> The Maven staging repo is: >> https://repository.apache.org/content/repositories/orgapachetomcat-1572 >> >> The tag is: >> https://github.com/apache/tomcat/tree/11.0.15 >> 692d6ffc5aa75d6804749ffcc14353c6b046fd92 >> >> The proposed 11.0.15 release is: >> [ ] -1 Broken - do not release >> [ ] +1 Stable - go ahead and release as 11.0.15 >> > > I have a unit test failing and I'm not sure if it is just flaky or if > there is an issue > here: > TEST-org.apache.tomcat.websocket.server.TestAsyncMessagesPerformance.NIO2.txt > > 06-Dec-2025 18:02:30.123 WARNING [http-nio2-127.0.0.1-auto-1-exec-3] > org.apache.tomcat.util.net.AbstractEndpoint.processSocket Executor rejected > socket > [org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper@78ffe6dc:Closed > Nio2Channel] for processing > java.util.concurrent.RejectedExecutionException: Executor not running, > can't force a command into the queue > at org.apache.tomcat.util.threads.TaskQueue.force(TaskQueue.java:60) > at org.apache.tomcat.util.threads.TaskQueue.force(TaskQueue.java:32) > at > org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1101) > at > org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1582) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.failed(Nio2Endpoint.java:651) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.failed(Nio2Endpoint.java:608) > at org.apache.tomcat.util.net.Nio2Channel$3.read(Nio2Channel.java:285) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper.fillReadBuffer(Nio2Endpoint.java:1162) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper.fillReadBuffer(Nio2Endpoint.java:1129) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper.read(Nio2Endpoint.java:950) > at > org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:74) > at > org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:184) > at > org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:164) > at > org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) > at > org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:60) > at > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:57) > at > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:903) > at > org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1677) > at > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) > at > org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1584) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:632) > at > org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:608) > at java.base/sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:121) > at java.base/sun.nio.ch.Invoker$1.run(Invoker.java:201) > at > java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:108) > at > org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:946) > at > org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:480) > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:57) > at java.base/java.lang.Thread.run(Thread.java:1474) > ------------- ---------------- --------------- > > Testcase: testAsyncTiming took 26.548 sec > FAILED > null > junit.framework.AssertionFailedError > at > org.apache.tomcat.websocket.server.TestAsyncMessagesPerformance.testAsyncTiming(TestAsyncMessagesPerformance.java:69) > at > java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) > > Running Java 25 on Ubuntu > > Any thoughts? > Thanks for RM'ing The aforementioned test failed twice on the main branch, and then on 10.x it failed twice and passed twice, so I am writing it off as a flaky test The proposed 11.0.15 release is: > [ ] -1 Broken - do not release > [X] +1 Stable - go ahead and release as 11.0.15 > The build is reproducible and unit tests are passing with an intermittent failure that seems to be a faulty test Igal > > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
