Hi, I wrote this in the issue tracker but I was redirected to here.
Found in GWT Release (2.5.1, 2.5.0.rc1)
Encountered on OS / Browser (Win7, Google Chrome):
Detailed description:
Dear folks,
we have a complex and large gwt app with many rpc calls.
In Google Chrome, there are some rpc call that freezes the browser's thread,
cpu runs at 13%, and the page does not respond anymore, only closing the page
helps. It happens only in Chrome (not in Firefox), and only in production mode
with compiled gwt code (it works well in dev mode). The rpc call initiated
properly, the server responds some data (data from an Oracle db), but neither
of onSuccess nor onFailure is called, but Chrome freezes.
In "Network" tab of Chrome I see the call with status code 200, but the
"Preview" and the "Response" tabs are empty despite of the server sends back
the data (I see it in a log).
Shortest code snippet which demonstrates issue (please indicate whereactual
result differs from expected result):
MxServiceAsync svc = GWT.create(MxService.class); //fine
svc.frameRPC(nb, new AsyncCallback<NucleusBean>() { //fine
public void onFailure(Throwable t) {
t.printStackTrace(); //never called
}
public void onSuccess(NucleusBean result) {
System.out.println(result); //never called
}
});
Workaround if you have one: NONE
In Fiddler network monitor I can see the response (correct data) from the
server (Apache Tomcat).
ANY help or advise is appreciated!
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
