[GUMP@vmgump]: Project tomcat-trunk-test-apr (in module tomcat-trunk) failed

/commons-daemon-20160902-native-src.tar.gz -Dexamples.sources.skip=true -Dbase.path=/srv/gump/public/workspace/tomcat-trunk/tomcat-build-libs -Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.5-201506032000/ecj-4.5.jar -Dtest.apr.loc=/srv/gump/public/workspace/tomcat-native-trunk/dest-20160902/lib

Re: [VOTE] Release Apache Tomcat 8.0.37

The proposed 8.0.37 release is: [ ] Broken - do not release [ X ] Stable - go ahead and release as 8.0.37 No test failure. Examples ok. Our test app works fine. -- From:Mark Thomas Time:2016 Sep 1 (Thu) 18:57

buildbot success in on tomcat-8-trunk

The Buildbot has detected a restored build on builder tomcat-8-trunk while building . Full details are available at: https://ci.apache.org/builders/tomcat-8-trunk/builds/753 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build Reason: The AnyBranchScheduler

[Bug 59961] Provide an option to disable processing of Class-Path entry in a jar's manifest file

https://bz.apache.org/bugzilla/show_bug.cgi?id=59961 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED

svn commit: r1759021 - in /tomcat/tc8.0.x/trunk: ./ java/org/apache/tomcat/util/scan/StandardJarScanner.java webapps/docs/changelog.xml webapps/docs/config/jar-scanner.xml

Author: markt Date: Fri Sep 2 19:23:43 2016 New Revision: 1759021 URL: http://svn.apache.org/viewvc?rev=1759021=rev Log: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=59961 Add an option to the StandardJarScanner to control whether or not JAR Manifests are scanned for additional class path

svn commit: r1759020 - in /tomcat/tc8.5.x/trunk: ./ java/org/apache/tomcat/util/scan/StandardJarScanner.java webapps/docs/changelog.xml webapps/docs/config/jar-scanner.xml

Author: markt Date: Fri Sep 2 19:22:58 2016 New Revision: 1759020 URL: http://svn.apache.org/viewvc?rev=1759020=rev Log: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=59961 Add an option to the StandardJarScanner to control whether or not JAR Manifests are scanned for additional class path

svn commit: r1759019 - in /tomcat/trunk: java/org/apache/tomcat/util/scan/StandardJarScanner.java webapps/docs/changelog.xml webapps/docs/config/jar-scanner.xml

Author: markt Date: Fri Sep 2 19:22:19 2016 New Revision: 1759019 URL: http://svn.apache.org/viewvc?rev=1759019=rev Log: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=59961 Add an option to the StandardJarScanner to control whether or not JAR Manifests are scanned for additional class path

[Bug 60076] ClientAbortException / IOException occurs only when using HttpServletResponseWrapper

https://bz.apache.org/bugzilla/show_bug.cgi?id=60076 --- Comment #4 from Mark Thomas --- (In reply to Olivier Jaquemet from comment #3) > It really seems to me that there is a change in Tomcat behavior somewhere, > otherwise exception would occur everytime, don't you think ?

Re: more protection around pauseNonContainerThread()?

~business code (simplified): public void myBusiness(AsyncResponse wrapperOfAsyncContext) { new Thread() { @Override public void run() { wrapperOfAsyncContext.synchronizedDispatch(); } }.start(); wrapperOfAsyncContext.synchronizedMethod(); } If

Re: more protection around pauseNonContainerThread()?

On 02/09/2016 14:45, Romain Manni-Bucau wrote: > PS: this pauseNonContainerThread breaks CXF apps cause they synchronize an > instance (AsyncResponseImpl) which potentially deadlock with tomcat cause > of that. Would be nice to solve it in a manner not requiring all apps/libs > to know that. Can

Re: more protection around pauseNonContainerThread()?

PS: this pauseNonContainerThread breaks CXF apps cause they synchronize an instance (AsyncResponseImpl) which potentially deadlock with tomcat cause of that. Would be nice to solve it in a manner not requiring all apps/libs to know that. Romain Manni-Bucau @rmannibucau

Re: [VOTE] Release Apache Tomcat 8.5.5

On 31/08/2016 21:48, Mark Thomas wrote: > The proposed 8.5.5 release is: > [ ] Broken - do not release > [ ] Alpha - go ahead and release as 8.5.5 > [ ] Beta - go ahead and release as 8.5.5 > [X] Stable - go ahead and release as 8.5.5 +1 On Fri, Sep 2, 2016 at 5:17 AM, Huxing Zhang

Re: [VOTE] Release Apache Tomcat 9.0.0.M10

2016-08-31 19:21 GMT+03:00 Mark Thomas : > The proposed 9.0.0.M10 release is: > [ ] Broken - do not release > [X] Alpha - go ahead and release as 9.0.0.M10 +1 On Fri, Sep 2, 2016 at 5:15 AM, Huxing Zhang wrote: > The proposed 9.0.0.M10 release is:

Re: [VOTE] Release Apache Tomcat 8.0.37

2016-09-01 12:56 GMT+02:00 Mark Thomas : > The proposed 8.0.37 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 8.0.37 +1 Unit tests pass on linux with tcnative 1.2.8 and my test suite looks good. On Fri, Sep 2, 2016 at 4:31 AM, Mark Thomas

Re: [VOTE] Release Apache Tomcat 8.5.5

The proposed 8.5.5 release is: [ ] Broken - do not release [ ] Alpha - go ahead and release as 8.5.5 [ ] Beta - go ahead and release as 8.5.5 [ X ] Stable - go ahead and release as 8.5.5 No test failure. Examples ok. Our test app works fine.

Re: [VOTE] Release Apache Tomcat 9.0.0.M10

The proposed 9.0.0.M10 release is: [ ] Broken - do not release [ X ] Alpha - go ahead and release as 9.0.0.M10 No test case failure except the following: [concat] Testsuites with failed tests: [concat]

Re: [VOTE] Release Apache Tomcat 8.0.37

On 01/09/2016 11:56, Mark Thomas wrote: > The proposed Apache Tomcat 8.0.37 release is now available for voting. > > The main changes since 8.0.36 are: > > - treat paths used to obtain a request dispatcher as encoded > (configurable) > > - update the packaged version of the Tomcat Native

Re: [VOTE] Release Apache Tomcat 8.5.5

On 31/08/2016 21:48, Mark Thomas wrote: > The proposed Apache Tomcat 8.5.5 release is now available for voting. > > The major changes compared to the 8.5.4 release are: > > > - limited support for wildcard Host names and aliases > > - fix regressions in JSSE TLS handshake > > - treat paths

Re: [VOTE] Release Apache Tomcat 9.0.0.M10

On 31/08/2016 17:21, Mark Thomas wrote: > The proposed Apache Tomcat 9.0.0.M10 release is now available for voting. > > This is a milestone release for the 9.0.x branch. It should be > noted that, as a milestone release: > - Servlet 4.0 is not finalised > - The EGs have not started work on JSP

Re: [VOTE] Release Apache Tomcat 8.0.37

2016-09-01 12:56 GMT+02:00 Mark Thomas : > The proposed 8.0.37 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 8.0.37 > > Rémy

[Bug 60076] ClientAbortException / IOException occurs only when using HttpServletResponseWrapper

https://bz.apache.org/bugzilla/show_bug.cgi?id=60076 --- Comment #3 from Olivier Jaquemet --- Thank you Mark for this analysis. I am completely ok to accept that IE behaves like sh%t, this would not be the first time. However, how do you explain the fact that

Re: [VOTE] Release Apache Tomcat 8.5.5

2016-09-01 5:48 GMT+09:00 Mark Thomas : > The proposed Apache Tomcat 8.5.5 release is now available for voting. > > The major changes compared to the 8.5.4 release are: > > > - limited support for wildcard Host names and aliases > > - fix regressions in JSSE TLS handshake > > -

Re: [VOTE] Release Apache Tomcat 8.0.37

2016-09-01 19:56 GMT+09:00 Mark Thomas : > The proposed Apache Tomcat 8.0.37 release is now available for voting. > > The main changes since 8.0.36 are: > > - treat paths used to obtain a request dispatcher as encoded > (configurable) > > - update the packaged version of the

Re: [VOTE] Release Apache Tomcat 9.0.0.M10

2016-09-01 1:21 GMT+09:00 Mark Thomas : > The proposed Apache Tomcat 9.0.0.M10 release is now available for voting. > > This is a milestone release for the 9.0.x branch. It should be > noted that, as a milestone release: > - Servlet 4.0 is not finalised > - The EGs have not