No technical expert advice can be found here ;)
Weblog by Erik Scholtz
org.mortbay.thread.Timeout. exception bei neuer GWT webapplication mit instantiations gwt designer oder windowbuilder pro
Wenn man eine neue WebApplication mit der GWT SDK 2.0.3 und der App Engine SDK 1.3.3 in eclipse erstellt und dabei den Instantiations WindowBuilder Pro oder den GWT Designer verwendet, dann taucht der folgende Fehler auf, wenn man versucht die “GWT application” (google nennt dies “Development Mode”) zu starten.
Exception in thread “main” java.lang.NoSuchMethodError: org.mortbay.thread.Timeout.<init>(Ljava/lang/Object;)V
at org.mortbay.io.nio.SelectorManager$SelectSet.<init>(SelectorManager.java:306)
at org.mortbay.io.nio.SelectorManager.doStart(SelectorManager.java:223)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:303)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.Server.doStart(Server.java:233)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:543)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:421)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1035)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:783)
at com.google.gwt.dev.DevMode.main(DevMode.java:275)
Leider konnte ich bisher nicht herausfinden warum dies passiert, aber ich habe einen Workaround gefunden, mit dem man das Problem verhindern und umgehen kann:
Statt die App Engine SDK 1.3.3 beim Anlegen des neuen Web Application Projektes zu verwenden, erstellt man das Projekt zunächst unter Verwendung der App Engine SDK 1.3.1. Nachdem das Projekt erstellt ist, kann man mit einem Rechts-Klick auf das Projektverzeichnis (in eclipse) die Properties des Projektes ändern: Unter Google>App Engine kann man nun von der App Engine 1.3.1 die Einstellung auf die App Engine 1.3.3 ändern; das Projekt läuft dann ohne Probleme unter der neuen Engine.
select new appengine in the properties
If you enjoyed this post, make sure you subscribe to my RSS feed!
15 Antworten auf org.mortbay.thread.Timeout. exception bei neuer GWT webapplication mit instantiations gwt designer oder windowbuilder pro
Hinterlasse eine Antwort
Get in contact:
Hi,
This happen because when you created the project you checked for to use the Google App Engine. I have created a new project without this option e the project run perfectly.
Thank you for to your help!
I think the problem is an incompatibility between the Jetty in the GWT jars and the AppEngine jars.
I solved it by going into Properties->”Java Build Path”->”Order and Export” and then used “Up” to move the “GWT SDK” up above the “App Engine SDK”.
KIM ! Do you have *ANY* idea how huge this is?
There a thousands and thousands of developers getting aggravated with how GAE is imposing all these restrictions, as if everyone is going to actually deploy to a google service on the web. What about all the intranet apps that run on JBoss, Glassfish, etc… !
One could “unplug” the app engine in Eclipse, but then it won’t start any more !
After hours and hours (all day, really) of searching and searching, not one single solution, until yours !
Moving that GWT jar up so that it is found before those damn app engine jars.
Finally a solution ! Good bloody grief !
@Kim Hansen
Thank you. Was going to have a headache when i chanced upon this.
Thanks Kim! You just save me a lot of time.
I will add my expression of gratitude as well. I had this problem and had no idea what to do, and the “Up” button trick worked beautifully. Thanks, Kim.
Thanks a lot, it works!
Kim, thanks a lot!!
)
I just disabled app engine and removed those messy jars from build-path.
Spent a few hours on this! And seemed guaranteed to spend more. Thanks!!
Thank you @ Kim Hansen … I really didn’t know where to start troubleshooting this error, rearranging the build path order done the trick. (I am developing a GWT+App Engine application).
Hopefully the Google team will address this in a future release of their SDK.
Thank you!!! It solved my problem too. Now the dent in the desk from my head hitting it won’t be so deep.
Thank you – it saves me a lot of time!
thanks a lot for this post. safed me probably hours of work!
Hey, Im using maven-gae-gwt to develop my application and I got this problem. Solved just changing the order of the libraries in buildpath. Put GWT SDK on top of the 2 items called Maven Dependencies.