StatusCodeException when navigating away from application

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run hellowgwteventservice
2. after application loads in browser enter an other URL (navigate away) 

What is the expected output? What do you see instead?
The application should not throw any exception. 
Instead a StatusCodeException: 0 occurs (full stack trace reported below).

What version of the product are you using? On what operating system?
JRE 1.7 (x64)
GWT 2.3.0
GwtEventService 1.2.0-20100413.144522-1
Firefox 4.0.1
Mac OS 10.6.7

Please provide any additional information below.

10:53:32.768 [ERROR] 
[de.novanic.gwteventservice.demo.hello.HelloGWTEventService] Client-Error: 
Error on processing event!

com.google.gwt.user.client.rpc.StatusCodeException: 0 
    at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:209)
    at com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:287)
    at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:395)
    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:613)
    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:167)
    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:326)
    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:207)
    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:132)
    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)
    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)
    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:214)
    at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:613)
    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:167)
    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:281)
    at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:531)
    at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:352)
    at java.lang.Thread.run(Thread.java:732)

Original issue reported on code.google.com by ker...@gmail.com on 2 Jun 2011 at 9:02

[GoogleCodeExporter]

This issue is reproducable, but doesn't seem to have negative effects (when 
navigating back everything is still working normally). This problem was already 
reported with Issue32, so this issue will now be merged together with Issue32.

Original comment by sven.strohschein@googlemail.com on 3 Oct 2011 at 10:49

• Changed state: Duplicate

[GoogleCodeExporter]

Fixed via Issue32:

Status code 0 is sent by some browsers when the browser/user navigates to 
another site/application and is actually not an error, but GWT inteprets this 
as a StatusCodeException. In the case of GWT applications it should be an 
unimportant status code because the GWT module is unloaded in that case.

Status code 0 is now handled correctly by GWTEventService and will no longer be 
logged as an error (fixed in the trunk version and in the upcoming 1.2 release 
candidate).

Original comment by sven.strohschein@googlemail.com on 3 Oct 2011 at 4:04