[GUMP@vmgump-vm3]: Project tomcat-tc8.0.x-test-nio2 (in module tomcat-8.0.x) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc8.0.x-test-nio2 has an issue affecting its community

[VOTE] Release Apache Tomcat 6.0.50

The proposed Apache Tomcat 6.0.50 release is now available for voting. Note: This is the last Tomcat 6 release. It can be obtained from: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.50/ The Maven staging repo is:

svn commit: r17920 [2/2] - in /dev/tomcat/tomcat-6/v6.0.50: ./ bin/ bin/extras/ src/

Added: dev/tomcat/tomcat-6/v6.0.50/src/apache-tomcat-6.0.50-src.tar.gz.asc == --- dev/tomcat/tomcat-6/v6.0.50/src/apache-tomcat-6.0.50-src.tar.gz.asc (added) +++

svn commit: r17920 [1/2] - in /dev/tomcat/tomcat-6/v6.0.50: ./ bin/ bin/extras/ src/

Author: violetagg Date: Sun Jan 22 15:59:15 2017 New Revision: 17920 Log: Stage 6.0.50 RC Added: dev/tomcat/tomcat-6/v6.0.50/ dev/tomcat/tomcat-6/v6.0.50/KEYS dev/tomcat/tomcat-6/v6.0.50/README.html dev/tomcat/tomcat-6/v6.0.50/RELEASE-NOTES dev/tomcat/tomcat-6/v6.0.50/bin/

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #6 from John D. Ament --- Just to clarify: - If you don't specify the setting, or have it set to 0, you get the old behavior. - If you set it to 1, you get the new behavior. - If you set it to anything

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #5 from John D. Ament --- Romain, what would be the benefit of current behavior when threads == 1? This is specific to helping fix a problem w/ Weld and Tomcat integration where a deadlock can occur because

svn commit: r1779821 - in /tomcat/tc6.0.x/tags/TOMCAT_6_0_50: ./ build.properties.default

Author: violetagg Date: Sun Jan 22 14:56:50 2017 New Revision: 1779821 URL: http://svn.apache.org/viewvc?rev=1779821=rev Log: Tag 6.0.50 Added: tomcat/tc6.0.x/tags/TOMCAT_6_0_50/ (props changed) - copied from r1779819, tomcat/tc6.0.x/trunk/ Modified:

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #4 from romain.manni-bucau --- Can 1 keep current behavior and 0 or negative values use an executor executing directly the task? 1 is used and relying on deployer threads avoids to leak data where this change

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #3 from John D. Ament --- I also created a PR not sure which would be easier. https://github.com/apache/tomcat85/pull/6 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #2 from John D. Ament --- Created attachment 34660 --> https://bz.apache.org/bugzilla/attachment.cgi?id=34660=edit Proposed code changes (based on dev discussion) -- You are receiving this mail because:

[Bug 60623] When startStopThreads is 1, don't rely on an executor and instead start synchronously

https://bz.apache.org/bugzilla/show_bug.cgi?id=60623 --- Comment #1 from Michael Osipov <1983-01...@gmx.net> --- Alternatively, one can provide a #join() method just like Jetty does in Server.class. -- You are receiving this mail because: You are the assignee for the bug.