An update to close this issue: After fiddling with many other things, I finally updated from 7.0.6 to 7.0.22. That fixed the issue.
The behavior was very strange & inconsistent. Apparently randomly, most AJP requests to Tomcat would come back with incorrect Content-type. As you can imagine, this caused some hard-to-track down errors. I couldn;t find any pattern to the errors. The same objects could be returned correctly after a reload (or not). In case it helps someone else ... -- Jonathan Rosenberg Founder & Executive Director Tabby's Place, a Cat Sanctuary http://www.tabbysplace.org/ On Fri, Nov 18, 2011 at 4:58 PM, Daniel Mikusa <dmik...@vmware.com> wrote: > On Fri, 2011-11-18 at 13:28 -0800, Jonathan Rosenberg wrote: >> Setup basics (all on Linux box): >> >> - Apache Tomcat/7.0.6 >> - JVM: 1.6.0_22-b04 >> - Apache httpd 2.2.17 >> -- proxied via "ProxyPass /Catalog ajp://localhost:8009/Catalog" >> > > You might want to give an updated version of Tomcat 7 a try. 7.0.22 is > the latest. > > If nothing else, you'll pick up an important security fix related to > AJP. > > https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.21 > > Dan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
