Hello, I'm currently working on a GWT 1.7 project for an Intranet application deployed on Oracle SOA Suite 10.1.3.4.0 and have stumbled onto the "Client did not send n bytes as expected" exception.
It turns out to be quite difficult to reproduce as we need about 7 or 8 users concurrently accessing the application for nearly 2 hours to get the exception to occur. Moreover, the clients have to be in our customer's network as we have never been able to reproduce the exception in our own network. The cost involved in reproducing the issue unfortunately limits our options. One direct consequence of this is that tests have only been run using IE7 which is the only browser supported by our customer. In my investigation, I made sure all users would run an HTTP Monitoring software that would log every request/response for that client. I found out that the request is first sent correctly with its associated data. However, for unknown reasons (possibly network failure) the request is sent a second time about 500-600 ms later with the same request header but omitting the associated data. At that point, the J2EE application server reads the request and rightfully complains about missing data. Note that the second request header still set a greater than 0 content-length (actually the exact same as in the first request). I believe this means one GWT, IE7 or a lower level transport layer implements a retry mechanism that omits to resend the data in spite of resending the exact same header. Does anyone know whether GWT implements such a retry mechanism? Thanks, Matthieu -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
