-----BEGIN PGP SIGNED MESSAGE-----
On 9/6/17 3:52 PM, James H. H. Lampert wrote:
> On 9/6/17, 11:19 AM, Mark Thomas wrote:
>> The old format will work with 8.5.x.
>> What were the stack traces?
> And Alejandro Vargas wanted to see the stack traces, too.
> Seeing as how this was the first stack trace (of 20, most with
> "caused by" sub-stack-traces):
>> org.apache.coyote.http11.Http11Protocol [snip]
> I tried putting the old-style connector tag back in, with the class
> name changed from "org.apache.coyote.http11.Http11Protocol" to
> "org.apache.coyote.http11.Http11NioProtocol" and this time, it
> worked perfectly.
> I should have tried that when I first noticed there was a
> difference. It actually DID jump right out at me, but I couldn't
> believe that was the only thing wrong, with 20 stack traces.
Yes, conf/server.xml is not forward-compatible. When you upgrade, it's
best to compare your conf/server.xml with the one that came with your
old stock Tomcat version, and essentially perform the same diff
against the new Tomcat's stock conf/server.xml.
Otherwise, things like this happen. In your case, the BIO connector
was removed from Tomcat, leaving only the NIO, NIO2, and APR connectors.
If you use "HTTP/1.1" as the protocol, you don't have to specify a
class name (and you'll get NIO by default). Or, you can leave the
"protocol" attribute completely absent and you'll get the default
(which is "HTTP/1.1", which implies NIO).
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org