https://bz.apache.org/bugzilla/show_bug.cgi?id=58063
Bug ID: 58063 Summary: Some async responses are empty when using Javamelody and Spring-webmvc Product: Tomcat 7 Version: 7.0.47 Hardware: PC Status: NEW Severity: normal Priority: P2 Component: Catalina Assignee: dev@tomcat.apache.org Reporter: ever...@free.fr Created attachment 32840 --> https://bz.apache.org/bugzilla/attachment.cgi?id=32840&action=edit Source to reproduce the issue I have a test webapp using async with Javamelody 1.56 and Spring-webmvc, in Tomcat 7.0.47 with JDK 1.7.0_80. When running in Tomcat 7.0.47, some async cases do not work and http responses are empty (buttons Async, Callable, Forward Async and Forward Callable), while others are OK (buttons Ajax, Redirect Ajax, Redirect Async, Redirect Callable, Forward Ajax, ResponseBody Async, ResponseBody Callable). When running in Jetty 9.1.0_RC2, all cases are OK. I created this issue as suggested by Mark [1]. To reproduce the issue: - unzip attached test-V3.zip - mvn tomcat7:run - open http://localhost:8080/ -> 4 buttons do not work and have empty responses, with javamelody - mvn jetty:run - open http://localhost:8080/ -> all buttons work, with javamelody - comment javamelody in pom.xml - mvn tomcat7:run - open http://localhost:8080/ -> all buttons work, without javamelody Note: the last change [2], added before flushing the response, does not fix the issue. If the httpResponse is not wrapped in a CounterServletResponseWrapper by the MonitoringFilter [3] or if Jetty is used instead of Tomcat, there is no more issue but I do not know why. This issue is also 338 in Javamelody: https://code.google.com/p/javamelody/issues/detail?id=338#c6 [1] http://mail-archives.apache.org/mod_mbox/tomcat-users/201506.mbox/%3c557da84b.9010...@apache.org%3E [2] https://code.google.com/p/javamelody/source/detail?r=4090 [3] https://code.google.com/p/javamelody/source/browse/trunk/javamelody-core/src/main/java/net/bull/javamelody/MonitoringFilter.java#181 -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org