Re: Client did not send n bytes as expected happening following a retry
After some more investigation I think that the problem is linked to the way Internet Explorer implements the XMLHttpRequest javascript object. This object is used by GWT to send the request. The link below explains the details of the issue. http://www.vistaheads.com/forums/microsoft-public-internetexplorer-general/479422-xmlhttprequest-post-sometimes-fails-when-server-using-keep-aliv.html I'm thinking of implementing a workaround with a custom RequestBuilder. RequestBuilder.send() would start a Timer timing out after 300ms. On timeout it would abort the request and send a new request. Hopefully this will cancel IE's behaviour of resending the request with a missing body. Please don't hesitate to contribute if you've an idea or think this won't work. 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.
Client did not send n bytes as expected happening following a retry
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.
Re: Client did not send n bytes as expected
We got same error. It turned out to be the problem of firebug. When we turned on the firebug with Firefox, we see such error. Looks like firebug try to send another get request when the RPC post got call. It is just annoying, but it does not affect function. We do not have such problem in IE6. On Jan 22, 1:34 am, Joe Cole profilercorporat...@gmail.com wrote: Take a look at this and the comment thread:http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-gl... There are some unresolved issues with gwt and glassfish/apache, which I think is what the cause of this error is. (We see it rarely, but sometimes see errors with error code 0 or 19020/19021 on the client side). We fixed it by patching the ProxyCreator class and making it automatically retry requests with a strange error code, the other approach is detailed in the link above. On Jan 21, 10:03 am, Vishal ranavis...@gmail.com wrote: We get this error: [#|2009-08-12T11:38:31.803-0700|SEVERE|sun-appserver9.1| javax.enterprise.system.container.web| http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-gl..._ThreadID=16;_ThreadName=httpSSLWorkerThread-38080-3;_RequestID=8b3571bb-3c 36-43f1-9e38-6947ca376436;| WebModule[]Exception while dispatching incoming RPC call javax.servlet.ServletException: Client did not send 142 bytes as expected at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8 (RPCServletUtils.java:148) at com.google.gwt.user.server.rpc.RemoteServiceServlet.readContent (RemoteServiceServlet.java:335) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost (RemoteServiceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) very rarely and it is not reproducible. I have seen posts earlier but none of them justify the reason for it. Appreciate if I can get some information: 1. Is it with the this version of GWT or related software, will upgrading help? 2. How often you get this error? 3. Any more workaround? Environment: Client: ie 6 Server: GlassFish 2, GWT 1.5.3. Java 5 -- 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.
Re: Client did not send n bytes as expected
git http://git-scm.com/ On Sat, Jan 23, 2010 at 5:53 PM, Michael W mwang_2...@yahoo.com wrote: We got same error. It turned out to be the problem of firebug. When we turned on the firebug with Firefox, we see such error. Looks like firebug try to send another get request when the RPC post got call. It is just annoying, but it does not affect function. We do not have such problem in IE6. On Jan 22, 1:34 am, Joe Cole profilercorporat...@gmail.com wrote: Take a look at this and the comment thread: http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-gl... There are some unresolved issues with gwt and glassfish/apache, which I think is what the cause of this error is. (We see it rarely, but sometimes see errors with error code 0 or 19020/19021 on the client side). We fixed it by patching the ProxyCreator class and making it automatically retry requests with a strange error code, the other approach is detailed in the link above. On Jan 21, 10:03 am, Vishal ranavis...@gmail.com wrote: We get this error: [#|2009-08-12T11:38:31.803-0700|SEVERE|sun-appserver9.1| javax.enterprise.system.container.web| http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-gl..._ThreadID=16;_ThreadName=httpSSLWorkerThread-38080-3;_RequestID=8b3571bb-3c36-43f1-9e38-6947ca376436;| WebModule[]Exception while dispatching incoming RPC call javax.servlet.ServletException: Client did not send 142 bytes as expected at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8 (RPCServletUtils.java:148) at com.google.gwt.user.server.rpc.RemoteServiceServlet.readContent (RemoteServiceServlet.java:335) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost (RemoteServiceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) very rarely and it is not reproducible. I have seen posts earlier but none of them justify the reason for it. Appreciate if I can get some information: 1. Is it with the this version of GWT or related software, will upgrading help? 2. How often you get this error? 3. Any more workaround? Environment: Client: ie 6 Server: GlassFish 2, GWT 1.5.3. Java 5 -- 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.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
Client did not send n bytes as expected
We get this error: [#|2009-08-12T11:38:31.803-0700|SEVERE|sun-appserver9.1| javax.enterprise.system.container.web| _ThreadID=16;_ThreadName=httpSSLWorkerThread-38080-3;_RequestID=8b3571bb-3c36-43f1-9e38-6947ca376436;| WebModule[]Exception while dispatching incoming RPC call javax.servlet.ServletException: Client did not send 142 bytes as expected at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8 (RPCServletUtils.java:148) at com.google.gwt.user.server.rpc.RemoteServiceServlet.readContent (RemoteServiceServlet.java:335) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost (RemoteServiceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) very rarely and it is not reproducible. I have seen posts earlier but none of them justify the reason for it. Appreciate if I can get some information: 1. Is it with the this version of GWT or related software, will upgrading help? 2. How often you get this error? 3. Any more workaround? Environment: Client: ie 6 Server: GlassFish 2, GWT 1.5.3. Java 5 -- 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.
Re: Client did not send n bytes as expected
Take a look at this and the comment thread: http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-glassfish-502-proxy-or-500-internal-errors-fix/ There are some unresolved issues with gwt and glassfish/apache, which I think is what the cause of this error is. (We see it rarely, but sometimes see errors with error code 0 or 19020/19021 on the client side). We fixed it by patching the ProxyCreator class and making it automatically retry requests with a strange error code, the other approach is detailed in the link above. On Jan 21, 10:03 am, Vishal ranavis...@gmail.com wrote: We get this error: [#|2009-08-12T11:38:31.803-0700|SEVERE|sun-appserver9.1| javax.enterprise.system.container.web| http://dobesland.wordpress.com/2008/08/22/gwt-to-lighttpdapache-to-glassfish-502-proxy-or-500-internal-errors-fix/ _ThreadID=16;_ThreadName=httpSSLWorkerThread-38080-3;_RequestID=8b3571bb-3c 36-43f1-9e38-6947ca376436;| WebModule[]Exception while dispatching incoming RPC call javax.servlet.ServletException: Client did not send 142 bytes as expected at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8 (RPCServletUtils.java:148) at com.google.gwt.user.server.rpc.RemoteServiceServlet.readContent (RemoteServiceServlet.java:335) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost (RemoteServiceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) very rarely and it is not reproducible. I have seen posts earlier but none of them justify the reason for it. Appreciate if I can get some information: 1. Is it with the this version of GWT or related software, will upgrading help? 2. How often you get this error? 3. Any more workaround? Environment: Client: ie 6 Server: GlassFish 2, GWT 1.5.3. Java 5 -- 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.
