I couldn't hold back investigating a bit more. Like described in my last post, the timeout" always" occurred/started in a GWTTestCase class that contained two test cases that involve RPC calls.
I did split up these test cases such that they have their own GWTTestCase class, and the timeout appearantly disappeared as I have seen it now for a week. All tests run fine now. Any idea how/why this is ? After all the debugging/work I get the feeling that there exists some "deep hidden bug" causing this timeout. .. Ed On Oct 13, 2:40 pm, Ed <[email protected]> wrote: > I give up for now :(... > This issue is getting me against the roof... :( > Even with remote debugging it all go well > But let's not forget that the error only occurs sometimes: about 50% > of the time and mostly during the day when I run the build manually > when the server is more busy. During the night when the build server > isn't doing much, most of the time thetimeoutexception doesn't > occur. > > Almost always the exception occurs in atestclass (extending > GWTTestCase) that contains more then onetest. As far as I can see, > it "never" happens intestclasses with only onetestmethod... So it > seems that more tests in one GWTTestCase class take more time and in > someway triggers thetimeoutexception... > > Also, in case thetimeoutexception occurs, the logging indicates that > the GWT servlet GWTShellServlet is correctly informed, but still the > exception occurs... > > For now, I disabled these GWTtestcase that need the backend (through > RPC) as I can't work with this unpredictable behavior. > > On Oct 5, 4:56 pm, Ed <[email protected]> wrote: > > > > > > running thetestin your continuous build environment with remote debugging > > > enabled and attaching to it with a debugger to see what is going on. > > > Thanks again. John > > I did that already but will do it again now that I have a better > > understanding of the GWT Junit code. > > (I only have to use some tricks to attach the remote debugger > > correctly ...) > > > On Oct 5, 4:24 pm, John Tamplin <[email protected]> wrote: > > > > On Tue, Oct 5, 2010 at 10:12 AM, Ed <[email protected]> wrote: > > > > I found the servlet you meant: JUnitHostImpl > > > > I see that the url that touches this servlet is correctly forwarded by > > > > the proxy and received by this servlet when debugging in Eclipse: > > > > The url that touches it: / > > > > com.bv.gwt.profile.intern.ProfileGwtTest.JUnit/junithost (also appears > > > > in the logging below) > > > > > However, when it's running during the nightly build and fails, I's > > > > hard to find out what went wrong as the this servlet doesn't contain > > > > debug/trace logging. It would be nice to see the path of execution in > > > > the logging such that I can see why the servlet isn't touched. > > > > > Any idea's how to solve this? > > > > Or any idea about what would be going wrong ? > > > > If it works when you run it directly, yet fails in the continuous build, > > > then something is different between the two that matters. I would suggest > > > running thetestin your continuous build environment with remote debugging > > > enabled and attaching to it with a debugger to see what is going on. > > > > -- > > > John A. Tamplin > > > Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
