Am 04.02.25 um 19:35 schrieb Mark Thomas:
The proposed Apache Tomcat 11.0.3 release is now available for voting.

The notable changes compared to 11.0.2 include:

- Allow readOnly attribute configuration on the Resources element and
   allow configuration of the readOnly attribute value of the main
   resources. The attribute value will also be used by the default and
   WebDAV Servlets.

- Correct a regression in the fix for bug 69382 that broke JSP
   include actions if both the page attribute and the body contained
   parameters. Pull request #803 provided by Chenjp.

- Expand the options for handling encoded '/' and '\' characters in
   URLs both in the Connector and when using a RequestDispatcher.

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.3/

The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1528

The tag is:
https://github.com/apache/tomcat/tree/11.0.3
6e6ddf18b5dd4baadd4470f2f48a71b9c4185122

The proposed 11.0.3 release is:
[ ] -1 Broken - do not release
[ ] +1 Stable - go ahead and release as 11.0.3

I see occasional OutOfMemoryErrors in org.apache.tomcat.util.net.TestSsl:

05-Feb-2025 01:33:51.440 SEVERE [https-jsse-nio2-127.0.0.1-auto-3-exec-5] org.apache.coyote.AbstractProtocol$ConnectionHandler.process Failed to complete processing of a request
java.lang.OutOfMemoryError: Java heap space
at java.base/java.util.Arrays.copyOf(Arrays.java:3537)
at java.base/java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:185) at org.apache.tomcat.util.net.TestSsl$SimplePostServlet.doPost(TestSsl.java:421)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:645)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:716)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:130) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:79) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:483) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:115) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:663) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:395) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:905) at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1688) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1422) at org.apache.tomcat.util.net.SecureNio2Channel$HandshakeWriteCompletionHandler.completed(SecureNio2Channel.java:129) at org.apache.tomcat.util.net.SecureNio2Channel$HandshakeWriteCompletionHandler.completed(SecureNio2Channel.java:122)
at java.base/sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:129)
at java.base/sun.nio.ch.Invoker.invokeDirect(Invoker.java:160)
at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.implWrite(UnixAsynchronousSocketChannelImpl.java:759) at java.base/sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:382) at java.base/sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:399) at org.apache.tomcat.util.net.SecureNio2Channel.handshakeInternal(SecureNio2Channel.java:310) at org.apache.tomcat.util.net.SecureNio2Channel.handshake(SecureNio2Channel.java:231) at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1665) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1422)
Unexpected EOF
Byte in position [0] had value [-1] rather than [1]

I do not know, whether they occured in previous versions. I had some TestSsl faliures before, but I think not as frequent as now. I was looking for OutOfMemory due to the observed (maybe unrelated) failures when testing TC 9.0.99.

Test currently run with Java 17.0.14, and fail for several vendors and for JSSE and also tcnative, OpenSSL versions 3.0 to 3.4 but now always.

JVM size is 256MB.

Best regards,

Rainer


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to