Chris,

I apologize, I thought I had to specify the other classes.
I do not have the Tomcat native library installed and it looks to be http-nio, 
here are the log entries:

21-Jan-2015 15:44:17.118 INFO [main] org.apache.coyote.AbstractProtocol.start 
Starting ProtocolHandler ["http-nio-8080"]
21-Jan-2015 15:44:17.118 INFO [main] org.apache.coyote.AbstractProtocol.start 
Starting ProtocolHandler ["http-bio-8443"]
21-Jan-2015 15:44:17.118 INFO [main] org.apache.coyote.AbstractProtocol.start 
Starting ProtocolHandler ["ajp-nio-8009"]
21-Jan-2015 15:44:17.118 INFO [main] org.apache.catalina.startup.Catalina.start 
Server startup in 2547 ms

Shaun Morton
Legal Files Software
217-726-6000 Ext. 341
sh...@legalfiles.com 
www.legalfiles.com

-----Original Message-----
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Wednesday, January 21, 2015 4:54 PM
To: Tomcat Users List
Subject: Re: Tomcat 8.0.17 output buffer issues

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Shaun,

On 1/21/15 5:27 PM, Shaun Morton wrote:
> Just so you know we are only using class Http11Protocol not 
> Http11NioProtocol or Http11AprProtocol.
> 
> This is our connector port which is also the default: <Connector 
> port="8080" protocol="HTTP/1.1" connectionTimeout="20000"
> redirectPort="8443" />

This will auto-select between the NIO and APR connectors. If you have the 
Tomcat native library available to Tomcat, then it will default to using the 
APR connector. If not, the default is the NIO connector.

Can you tell us which one you are using? You can confirm this by looking at the 
startup log messages. For instance, when I start my Tomcat, I get messages 
about the connectors like this:

Jan 12, 2015 3:52:08 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-nio-8215"] Jan 12, 2015 3:52:08 PM 
org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-8217"]

That indicates that I'm running one AJP-NIO connector and one HTTP-NIO handler. 
Your startup logs will tell you which is being effectively auto-selected.

Thanks,
- -chris

> -----Original Message----- From: Christopher Schultz 
> [mailto:ch...@christopherschultz.net] Sent: Wednesday, January 21,
> 2015 4:11 PM To: Tomcat Users List Subject: Re: Tomcat 8.0.17 output 
> buffer issues
> 
> Mark,
> 
> On 1/21/15 4:59 PM, Mark Thomas wrote:
>> On 21/01/2015 21:51, Shaun Morton wrote:
>>> Sorry no, it happens on both connectors, 8080(HTTP) and 8443(HTTPS).
>>> 
>>> The 8080 connector is the default out of the installation.  I try to 
>>> stick to defaults for trouble shooting purposes.
> 
>> I must confess I suspected the two were related as well when I read 
>> your mail. Since you are being far more responsive that the OP that 
>> filed that bug, my current plan is to fix the issue you are seeing 
>> and then evaluate BZ 57476 in light of what we discover the root 
>> cause of this issue is.
> 
>> I will say that 8.0.18 is likely to appear fairly soon after we track 
>> this one down.
> 
>> So, my question to you is this. With a clean 8.0.17 install, that is 
>> the easiest way to reproduce this bug? Ideally, if you could provide 
>> the simplest possible JSP that triggers this that would be great. 
>> (Since we are assuming the reports are linked, just attach it to that 
>> BZ report.)
> 
> FWIW, I'm using 8.0.17 in development with no ill effects.
> 
> Environment: Oracle Java 1.7.0_67 Tomcat 8.0.17 (release candidate, 
> identical to released version) Debian Linux 7.0, 2.6.32 kernel 
> Connector configuration:
> 
> <Connector port="8215" redirectPort="443" 
> protocol="org.apache.coyote.ajp.AjpNioProtocol" 
> URIEncoding="UTF-8" executor="tomcatThreadPool" />
> 
> <Connector port="8217" 
> protocol="org.apache.coyote.http11.Http11NioProtocol" 
> address="127.0.0.1" secure="false" URIEncoding="UTF-8" 
> executor="tomcatThreadPool" />
> 
> The AJP connector is the one getting primary use through Apache httpd 
> and mod_jk. The HTTP connector is used for loopback requests from 
> another service also running under a similar configuration.
> 
> We are using almost no JSP resources at all. I quickly tested one of 
> our JSPs and it seems to work file. The response size is 39,777 bytes, 
> content type is application/xhtml+xml, and there is no explicit buffer 
> size set in the .jsp source.
> 
> -chris
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJUwC4DAAoJEBzwKT+lPKRYOv4P/jeUTWEvRL70rVbTY+1THsnI
EpUxc3zO+EiHzqlDUuyy/2MwK6bndgecMZHsVSHq/Zd9bC8xfpbsy4m7EzgP8wTT
KSCCfm2jIGBBF62e67qGkKddejEqUZ6oDXDP0XBz7ERfsYcneDcUEYTAjIC8fCOi
19/n2uyjRlmnK62SHBLC0U6AqYt0joAv/LR/YK4qHh2caGh+Y8geNIq7oBjfrMJe
LgiZm+I+ZvLn9Hsdv5tRywajDFWKR8PWNgiye/tXjhdidlW+nTPrac4JIWTgU4AQ
pKals71fJZh5Z3oCtVFoHY/Yz9RtWNwaJSNkv/ZEaByykgq9aHI3SzP1udShz+Be
qxXzM8jWl9rd3lC8c/uSivTRtgv6/wRc6zia353Hl3ZSNqa8sO4qYnwVbZOtx1Q9
VKXmSzJbWmeNEl67ber2zeGr9zyoeajyQiO/laQeEv4JGciR2ysmKI+W8GbQ3zpv
YMpqHzl8SvcKwpZons72MmjQZOSKtB3uPopzY7XYr6y5GCebUaNhXF0EtXoM8CDk
tGjHTq5i/H+Oq35ZArsmGQx6oVPmATW0xCu0uUj54UlbB655YaHuQGZaRwgfpHOk
VjH4qpJI/lpmnrVb3Ey0rLXGsgHFzWG7qEnotYlbeew788JgmcdVCecF39q+fBkG
ijV29Rmofivmxib3vBE4
=iuNt
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to