[Bug 68932] Occasional 404 or 500 errors

2024-05-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68932

--- Comment #9 from Nathan  ---
(In reply to Nathan from comment #8)
> I will try other versoins like 8.5.100 later. It is truely difficult to
> reproduce this bug in other applications in test environment. Here is some
> infos.
> 
> 1.We use the same url path (e.g /test/foo ,not the real uri, I will deal
> with params in my application), so i think it has nothing to do with HTTP
> specification compliance.Also I don't think there is any sort of pattern in
> url.
> And I don't test it in websocket or http2. 
> 2.It is deployed in standalone type. I didn't pay attention to the embedding
> type yet.And we didn't use ROOT or manager, just put applications into
> webapps directoty.
> 
> Additionally, I came across a phenomenon during debugging in ide. When I
> debug in ide, It will go into timeout method, and it will return 404. After
> that, It will return 404 forever. But in product environment, I don't think
> it will happen.
> 
> 
> --
> org.apache.tomcat.util.net.NioEndpoint$Poller#run()
>   // Process timeouts
>   timeout(keyCount,hasEvents);
> 
> --
> org.apache.tomcat.util.net.NioEndpoint$Poller#timeout(int keyCount, boolean
> hasEvents)
> 
> } else if (!processSocket(socketWrapper, SocketEvent.ERROR, true)) {
> cancelledKey(key, socketWrapper);
> }
> --

Sorry, correct the description above:

 Additionally, I came across a phenomenon during debugging in ide. When I
 debug in ide, It will go into timeout method, and it will return 404. After
 that, the Poller thread  [http-nio-8080-Poller] will invoke the code every
time a request comes in in 60 seconds, while the browser get a 200 response .

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: [VOTE] Release Apache Tomcat 9.0.89

2024-05-06 Thread Rémy Maucherat
On Fri, May 3, 2024 at 10:37 PM Rémy Maucherat  wrote:
>
> The proposed Apache Tomcat 9.0.89 release is now available for voting.
>
> The notable changes compared to 9.0.88 are:
>
> - Refactor HTTP header parsing to use common parsing code and fix
>non-blocking reads of chunked request bodies including trailer fields
>
> - Add more timescale options to AccessLogValve and
>ExtendedAccessLogValve
>
> - WebDAV locking handling fixes
>
> For full details, see the changelog:
> https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.89/
>
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1494
>
> The tag is:
> https://github.com/apache/tomcat/tree/9.0.89
> 661a5978828212bbe4a324dd7c854894f34a561b
>
> The proposed 9.0.89 release is:
> [ ] -1, Broken - do not release
> [X] +1, Stable - go ahead and release as 9.0.89

Rémy

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



Re: [VOTE] Release Apache Tomcat 11.0.0-M20

2024-05-06 Thread Rémy Maucherat
On Fri, May 3, 2024 at 6:22 PM Mark Thomas  wrote:
>
> The proposed Apache Tomcat 11.0.0-M20 release is now available for
> voting.
>
> Apache Tomcat 11.0.0-M20 is a milestone release of the 11.0.x branch and
> has been made to provide users with early access to the new features in
> Apache Tomcat 11.0.x so that they may provide feedback. The notable
> changes compared to the previous milestone include:
>
> - Add OpenSSL FFM classes to tomcat-embed-core.jar
>
> - Refactor HTTP header parsing to use common parsing code and fix
>non-blocking reads of chunked request bodies including trailer fields
>
> - Add more timescale options to AccessLogValve and
>ExtendedAccessLogValve
>
>
> 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.0-M20/
>
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1493
>
> The tag is:
> https://github.com/apache/tomcat/tree/11.0.0-M20
> c400bf727cbc10198d3f52c29849d18660050b0c
>
> The proposed 11.0.0-M20 release is:
> [ ] -1 Broken - do not release
> [X] +1 Alpha  - go ahead and release as 11.0.0-M20

Rémy

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



Re: [VOTE] Release Apache Tomcat 9.0.89

2024-05-06 Thread Rémy Maucherat
On Mon, May 6, 2024 at 4:57 AM Rainer Jung  wrote:
>
> Am 03.05.24 um 22:37 schrieb Rémy Maucherat:
> > The proposed Apache Tomcat 9.0.89 release is now available for voting.
> >
> > The notable changes compared to 9.0.88 are:
> >
> > - Refactor HTTP header parsing to use common parsing code and fix
> > non-blocking reads of chunked request bodies including trailer fields
> >
> > - Add more timescale options to AccessLogValve and
> > ExtendedAccessLogValve
> >
> > - WebDAV locking handling fixes
> >
> > For full details, see the changelog:
> > https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html
> >
> > It can be obtained from:
> > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.89/
> >
> > The Maven staging repo is:
> > https://repository.apache.org/content/repositories/orgapachetomcat-1494
> >
> > The tag is:
> > https://github.com/apache/tomcat/tree/9.0.89
> > 661a5978828212bbe4a324dd7c854894f34a561b
> >
> > The proposed 9.0.89 release is:
> > [ ] -1, Broken - do not release
> > [X] +1, Stable - go ahead and release as 9.0.89
> >
> > Rémy
>
> +1, builds fine (on RHEL8 using JDK22).
>
> Tested via unit test suite on RHEL 6, 7, 8 and 9, SLES 11, 12 and 15 and
> Solaris 10 and 11 using latest patch levels of JDK 8, 11, 17, 21, 22
> from Adoptium Temurin, Zulu Azul, Amazon Coretto, Oracle and RedHat (the
> latter only on RHEL) plus JDK 23 EA 18. Solaris tests limited to JDK
> 1.8.0 and 11. A total of 161 test runs for NIO+NIO2.
>
> Also ran the few relevant tests for all of these platforms and JVMs in
> combination with tcnative 1.3.0 and 2.0.7 built with OpenSSL 3.0.13,
> 3.1.5, 3.2.1 and 3.3.0. A total of 1288 test runs for NIO+NIO2. Tests
> assumed to be relevant were
> org/apache/coyote/http2/TestLargeUpload.java,org/apache/**/Test*SSL*.java,org/apache/**/Test*Ssl*.java,org/apache/**/Test*openssl*.java,org/apache/tomcat/util/net/**/Test*.java,org/apache/tomcat/jni/**/Test*.java
>
> No testing done for APR connectors.
>
> Test adjustments:
>
> - TestMapperPerformance increased maxTime from 5000 to 25000
> - TesterTagHandlerPoolPerformance lowered loop count from 500, to 50
> - SimpleHttpClient increased soTimeout from 1 to 2
>
> No unusual test failures:
>
> 1) sporadic tcnative crashes (probably during shutdown, running with 2
> test threads):
>
> - org.apache.tomcat.util.net.TestClientCert FAILED (crashed)
>1 rh_jdk1.8.0-rhel9.x86_64-tcnative-1.3.0-320-1
>
> - org.apache.tomcat.util.net.TestClientCertTls13 FAILED (crashed)
>1 amazon_jdk1.8.0-rhel9.x86_64-tcnative-2.0.7-300-1
>
> - org.apache.tomcat.util.net.TestSsl FAILED (crashed)
>1 amazon_jdk1.8.0-rhel9.x86_64-tcnative-2.0.7-300-1
>1 oracle_jdk1.8.0-sles12.x86_64-tcnative-2.0.7-310-2
>1 amazon_jdk21-sles12.x86_64-tcnative-2.0.7-320-1
>1 amazon_jdk21-sles15.x86_64-tcnative-1.3.0-310-2
>1 rh_jdk21-rhel8.x86_64-tcnative-2.0.7-320-1
>
> - org.apache.catalina.valves.rewrite.TestResolverSSL FAILED (crashed)
>1 zulu_jdk21-sles12.x86_64-tcnative-2.0.7-300-1
>
>
> 2) very sporadic JSSE failures for Linux:
>
> - org.apache.tomcat.websocket.server.TestSlowClient FAILED
>1 amazon_jdk1.8.0-rhel6.x86_64-jsse
>1 oracle_jdk17-rhel6.x86_64-jsse
>
> -
> org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator
> FAILED
>1 adopt_jdk22-rhel8.x86_64-jsse
>
> 3) sporadic JSSE failures for Solaris:
>
> - org.apache.catalina.connector.TestConnector FAILED
>1 oracle_jdk1.8.0-solaris10.sparc-jsse
>
> - org.apache.catalina.core.TestSwallowAbortedUploads FAILED
>1 adopt_jdk1.8.0-solaris11.sparc-jsse
>2 oracle_jdk1.8.0-solaris11.sparc-jsse
>2 zulu_jdk1.8.0-solaris11.sparc-jsse
>
> - org.apache.tomcat.websocket.TestWebSocketFrameClientSSL FAILED
>1 zulu_jdk11-solaris11.sparc-tcnative-1.3.0-300-1
>
> - org.apache.tomcat.websocket.server.TestClose FAILED
>1 zulu_jdk1.8.0-solaris11.sparc-jsse

Thanks :) Your testing is getting more extensive every time !

Rémy

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

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



[Bug 68932] Occasional 404 or 500 errors

2024-05-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68932

--- Comment #8 from Nathan  ---
I will try other versoins like 8.5.100 later. It is truely difficult to
reproduce this bug in other applications in test environment. Here is some
infos.

1.We use the same url path (e.g /test/foo ,not the real uri, I will deal with
params in my application), so i think it has nothing to do with HTTP
specification compliance.Also I don't think there is any sort of pattern in
url.
And I don't test it in websocket or http2. 
2.It is deployed in standalone type. I didn't pay attention to the embedding
type yet.And we didn't use ROOT or manager, just put applications into webapps
directoty.

Additionally, I came across a phenomenon during debugging in ide. When I debug
in ide, It will go into timeout method, and it will return 404. After that, It
will return 404 forever. But in product environment, I don't think it will
happen.


--
org.apache.tomcat.util.net.NioEndpoint$Poller#run()
  // Process timeouts
  timeout(keyCount,hasEvents);

--
org.apache.tomcat.util.net.NioEndpoint$Poller#timeout(int keyCount, boolean
hasEvents)

} else if (!processSocket(socketWrapper, SocketEvent.ERROR, true)) {
cancelledKey(key, socketWrapper);
}
--

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org