-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jim,
On 8/22/17 2:03 PM, Johnson, Jim wrote: >> What led you to believe that there was a particular system >> property that had any effect? > > Because I've seen other properties such as: > > server.tomcat.connector.max-post-size=XXXXXXXX > server.max-http-header-size=XXXXXX server.use-forward-headers=true > server.ajp.port=XXXX Those aren't anything that Tomcat itself understands. Those must be Spring Boot configuration settings. > And I guess honestly, I was hoping that perhaps there was some > standard that if it's a configurable option in an AJP Connector > stanza, then there's a corresponding command line system property > that can be used instead. This line of thinking of course would > require that Spring Boot was using some "official" embedded Tomcat > code that had a zillion options all ready to be used but as I read > through your response, it's dawning on me that my line of thinking > is completely off. It was a reasonable assumption... it just happens to be incorrect :) > That it's really up to the developer of the spring boot app I'm > using to put into their code whatever options or settings that they > need tomcat to use. Correct. One of the problems with properties like those you describe is that they suppose that there is only *one* configuration for e.g. a connector. Tomcat can support an arbitrary number of connectors, each with separate port numbers, AJP header sizes, etc. so to properly-support Tomcat's full capabilities, you'd need to have properties like: server.tomcat.connector.1.max-post-size=XXXXXXX server.tomcat.connector.1.max-http-header-size=xxxxx etc. > If their code doesn’t use AJP or do anything with server.ajp.port, > then no matter how hard I try, I'll never get an AJP connector to > work. Exactly. > I think I get it now. My apologies, this is my first stint doing > sysadmin work with embed and I've been treating it like a full > blown Tomcat instance that comes with everything turned off, but > still included, thinking I need to supply all these different > arguments to turn stuff on. It's more like it's available but not > included - the developer needs to supply the code to turn on the > tomcat feature. Correct. If Spring Boot is being used, then SB needs to supply the configuration details to Tomcat, and their documentation should tell you how to specify them. It's possible a particular setting isn't supported (yet) and needs to be added to Spring Boot. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJZnIcjAAoJEBzwKT+lPKRYGeIQAKLnJnlwZGzXNVuNIGLuUaL7 JL6tgRJ99yX2yClERWTzPPjhLNkNRORFbwQuAOTXOhpeOnAOnqPdcYLVKNi3bx51 zxH/DwK/vnIj4MfkKRD+h6SeaApeb0mZUuqn7Ds1cE0Gspkj3935X7yQwLWUQgM6 bTw/DpAXOzL/COjQK6wAxxYHqNKVGGOliJcLpi7URjjUE8nqLt7/Sx33xs/X8rt5 nL/o+LhVcJM3DjUpF9Y/VbwglltUgZCvoOKyDAdB2uKP24qniipNwt3XHA7jtTSg n8biWkod3ksPbWJvt/gRUkIbgQioW7xU3xTr47U48eOFtEKrgUm1o2KWwJrfIwVT zoyqWfyFxuPJPVK+JcmCxwxCwyII/psG7LK2ui82SVy8Hn1wuC53HQI0bGuHvi0B Si2hRaSXWzqueS8Ji8SFgrhz6i9J6Yac1Twj4tuhaTmdKfu8XYeRmCHS/JUWM/T7 pzavMTlekV3nvGJ/Gtp0DDuW8K1xCm0yZIbxBpzYXj79SSawzMy8cmlQDyPfzGCI RIxn7ePhB7EpDlIbvhqos1Ajv7suy3lV4RXeVIrdvUgmvJpITJ/HUJIDwaDEG1P6 fEWm6pe8AdnSmyK/wng2Psvabj5tDUHV/faVGeC1uSaw7/oWpMdX+DwufhSDfGhY GdPuTP4dCBaiIfb0KnLU =cux+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
