Ok - I found the culprit - it wasn't Tomcat 6 at all. It was the upgrade from MyFaces 1.1.4 to MyFaces 1.1.5 that caused the issue. Tomcat 6 merely seems to be logging warnings about parameters which Tomcat 5.5. didn't do - that caused me to incorrectly suspect Tomcat 6.
I tested this by downgrading to Java 5 and Tomcat 5.5 - the problem still persisted. It was only when I downgraded from MyFaces 1.1.5 to MyFaces 1.1.4 that the issue was resolved. The bottom line seems to be that something changed in MyFaces 1.1.5 that stops my AjaxAnywhere implementation from working correctly. It may the "ajaxified" DisplayTag links code that I got from a sample Matt gave that needs updating (Matt -any comments on this?). Anyway - I'll post back here if I find a solution to the problem. jvosloo wrote: > > I recently upgraded my JSF 1.9.3 based app to Tomcat 6 and Java 6. > > Besides some minor issues with the build file etc. everything seemed fine > and I took the upgrade to production. > > I noticed the following in the log from time to time (but because > everything seemed to work - I ignored it): > > 2007/06/04 07:43:31 org.apache.tomcat.util.http.Parameters > processParameters > WARNING: Parameters: Invalid chunk ignored. > > I just now realized that my AjaxAnywhere based search pages stopped > working. It seems that the search field values that previously got > submitted via AjaxAnywhere, aren't being submitted anymore. The only clue > I have as to why is the above Tomcat 6 log entries I mentioned above, > which appears exactly when I perform a search. > > Any ideas/advice will be greatly appreciated. > -- View this message in context: http://www.nabble.com/AjaxAnywhere-and-Tomcat-6-tf3866784s2369.html#a10957806 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
