Hello Konstantin, thanks for sharing the valuable information. > On Dec 1, 2018, at 19:00, Konstantin Kolinko <knst.koli...@gmail.com> wrote: > >> * Our downstream Nginx instance (The client of our Tomcat instance) recorded >> the error "upstream sent no valid HTTP/1.0 header while reading response >> header from upstream" at that time and the error makes perfect sense >> concerning the response which has neither HTTP status line nor HTTP headers. > > 1. See the official FAQ / Troubleshoting page: > https://wiki.apache.org/tomcat/FAQ/Troubleshooting_and_Diagnostics > > Especially pay attention to > 1) configuring an access log > 2) setting system property > org.apache.catalina.connector.RECYCLE_FACADES=true
I've investigated "RECYCLE_FACADES" and understand that an improperly implemented application which keeps a reference to Request or Response objects outside of their lifecycle can make such an issue like mine happen (please correct me if I'm wrong..). But I still don't quite understand what does "RECYCLE_FACADES=true" do. The Wiki page says "This makes it easier to spot illegal access when it happens, instead of waiting until side effects of such access become visible" but how does it make easier? Does this property make Tomcat produce an Exception or make Tomcat produce some warning message to a log file or something when such accesses happen, for example? p.s. Speaking of the possibility of an improper implementation, I've found some discussions which seem to have some similarity to my case like the following: * http://tomcat.10.x6.nabble.com/NullPointerException-in-MimeHeaders-td2054107.html : I've seen some similar Exceptions at the "MimeHeaders" class which were recorded in my Tomcat's log too * http://tomcat.10.x6.nabble.com/Tomcat-occasionally-duplicating-responses-td5034710.html : A case where a bug in a Filter make Tomcat produce an invalid HTTP response Those discussions made me think of this possibility where my app might be improperly implemented. I'm going to check the application code from this perspective on Monday.. Best Regards, Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
