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.
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
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.
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
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
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
