Am 03.11.2016 um 18:32 schrieb Christopher Schultz:
Felix,
On 11/3/16 10:43 AM, Felix Schumacher wrote:
Hi all,
change r1767357 broke ajp connector with an executor.
Tomcat fails to set the thread priority, since the ajp connector
reports a default priority of -1 and Thread#setPriority will throw an
IAE in line 583 of AbstractProtocol#start.
To reproduce this enable the commented executor in server.xml and add
that executor to the ajp connector.
I'm using this configuration with 8.5 with no ill effects:
<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
maxThreads="150" minSpareThreads="4"/>
<Connector port="@connector-port@"
redirectPort="443"
protocol="org.apache.coyote.ajp.AjpNioProtocol"
URIEncoding="UTF-8"
packetSize="65536"
executor="tomcatThreadPool" />
<Connector port="@secure-connector-port@"
protocol="org.apache.coyote.http11.Http11NioProtocol"
address="127.0.0.1"
secure="false"
URIEncoding="UTF-8"
executor="tomcatThreadPool" />
Which exact connector are you using? How do I need to change my
configuration to confirm the problem?
I used the conf/server.xml from output/build. In fact I changed into
output/build and edited conf/server.xml with
--- conf/server.xml.orig 2016-11-03 18:43:48.737312712 +0100
+++ conf/server.xml 2016-11-03 18:44:29.069284390 +0100
@@ -53,10 +53,8 @@
<Service name="Catalina">
<!--The connectors can use a shared executor, you can define one
or more named thread pools-->
- <!--
<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
maxThreads="150" minSpareThreads="4"/>
- -->
<!-- A "Connector" represents an endpoint by which requests are
received
@@ -108,7 +106,7 @@
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
- <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
+ <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
executor="tomcatThreadPool" />
<!-- An Engine represents the entry point (within Catalina) that
processes
and started tomcat with ./bin/startup.sh
Regards,
Felix
A second rather minor point is a white space policy violation in
webapps/docs/config/http2.xml:160.
Oh noes! :)
-chris
Am 2. November 2016 15:15:03 MEZ, schrieb Mark Thomas <ma...@apache.org>:
The proposed Apache Tomcat 8.5.7 release is now available for voting.
The major changes compared to the 8.5.6 release are:
- Implement header limits for HTTP/2
- Improve handling of I/O errors with async processing
- Fail earlier on invalid HTTP requests
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.7/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1102/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_7/
The proposed 8.5.7 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.5.7
[ ] Beta - go ahead and release as 8.5.7
[ ] Stable - go ahead and release as 8.5.7
---------------------------------------------------------------------
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
