Hi Bob, sorry for my last post, I made a mistake in my project.
With this patch, the RPC call works properly! Thanks for your help, Mark On 3 Nov., 11:25, Mark Goerdes <mgoer...@googlemail.com> wrote: > Hi Bob, > thanks for your answer. With the patch on the current GWT 2 trunk I > get an out of memory error with my example. I tested with 256M and > 512M. Any ideas? > > Regards, > Mark > > java.lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2882) > at java.lang.AbstractStringBuilder.expandCapacity > (AbstractStringBuilder.java:100) > at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java: > 390) > at java.lang.StringBuffer.append(StringBuffer.java:224) > at > com.google.gwt.dev.util.log.AbstractTreeLogger.getStackTraceAsString > (AbstractTreeLogger.java:71) > at com.google.gwt.dev.shell.log.SwingTreeLogger$LogEvent.<init> > (SwingTreeLogger.java:87) > at com.google.gwt.dev.shell.log.SwingTreeLogger.doLog > (SwingTreeLogger.java:253) > at com.google.gwt.dev.util.log.AbstractTreeLogger.log > (AbstractTreeLogger.java:208) > at com.google.gwt.core.ext.TreeLogger.log(TreeLogger.java:273) > at com.google.gwt.dev.shell.ModuleSpace.log(ModuleSpace.java:317) > at com.google.gwt.dev.shell.GWTBridgeImpl.log(GWTBridgeImpl.java:65) > at com.google.gwt.core.client.GWT.log(GWT.java:202) > at com.bearingpoint.davinci.frontend.gwt.test.client.SerializationTest > $1.onFailure(SerializationTest.java:20) > at > com.google.gwt.rpc.client.impl.RpcCallbackAdapter.onResponseReceived > (RpcCallbackAdapter.java:107) > at com.google.gwt.http.client.Request.fireOnResponseReceived > (Request.java:287) > at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange > (RequestBuilder.java:396) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:146) > at > com.google.gwt.dev.shell.BrowserChannel.reactToMessagesWhileWaitingForReturn > (BrowserChannel.java:1706) > at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript > (BrowserChannelServer.java:144) > at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke > (ModuleSpaceOOPHM.java:120) > at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java: > 518) > at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject > (ModuleSpace.java:275) > 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:188) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > On 3 Nov., 02:38, BobV <b...@google.com> wrote: > > > Please test the patch athttp://gwt-code-reviews.appspot.com/89815and > > let me know if that fails to resolve the problem. > > > -- > > Bob Vawter > > Google Web Toolkit Team --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
