Sounds like classic infinite recursion to me. I can't see the code, but if your service call simply calls itself again on failure, and you don't track a failure count anywhere, I could see that spinning around infinitely and blowing up.
-Ben On Jan 20, 1:24 pm, mike b <[email protected]> wrote: > gwt 2.1.0 > winxp > ie7 > > I was tracing a completely different StatusCodeException (500) because of > server socket errors were are having. > (seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4723) > > Then strangely, I got this error on the client side. Basically, I created > an RpcHelper<aSerivce,T> which wraps the inner AsyncCallback<T> in another > AsyncCallback<T>. If I get the above mention 500 status code error, then I > re-execute the service without calling the inner onFailure. Re-execution > takes place w/ Scheduler.get().scheduleDefered( ...aService call.... ); > > Based on my client logs, the "Out of stack space" occurred in the Scheduler > part. > > com.blah.MyUncaughtExceptionHandler: onUncaughtException: > java.lang.Throwable: (Error): Out of stack space > number: -2146828260 > description: Out of stack space > I have a service that ships logs to the server and that still executed > successfully. > > Any ideas? I searched this forum and the gwt issues but did not find > anything remotely similar. > > Thanks, > Mike B -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
