Tooling: Starting server (sometimes) doesn't work

[Beta User]

Hi !

sometimes after starting Eclipse I'm not able to start the dm server using the Server Tooling. When I try to start the server using the "Servers" view, STS shows "Starting SpringSource dm server" but it doesn't really start the server; it seems to hang. There is no process launched and no output in the Console is shown. It's also not possible to cancel the job using Eclipse "Progress" view. I even cannot shutdown Eclipse since eclipse is waiting (forever) for the start job to complete.

In such situations there are some ClassCastExceptions like this in Eclipse' Error Log:

java.lang.ClassCastException: org.eclipse.jdt.internal.core.JavaModelManager$Per sistedClasspathContainer cannot be cast to org.eclipse.jdt.internal.launching.JREContainer
at com.springsource.server.ide.runtime.core.ServerUti ls.getJavaVersion(ServerUtils.java:223)
at com.springsource.server.ide.runtime.core.ServerUti ls.createDependencyLocator(ServerUtils.java:133)
at com.springsource.server.ide.jdt.internal.core.clas spath.ServerClasspathContainer.createDependencyLoc ator(ServerClasspathContainer.java:398)
at com.springsource.server.ide.jdt.internal.core.clas spath.ServerClasspathContainer.refreshClasspathEnt ries(ServerClasspathContainer.java:229)
at com.springsource.server.ide.jdt.internal.core.clas spath.ServerClasspathContainer.getClasspathEntries (ServerClasspathContainer.java:165)
at org.eclipse.jdt.internal.core.JavaModelManager.con tainerPutIfInitializingWithSameEntries(JavaModelMa nager.java:563)
at org.eclipse.jdt.internal.core.SetContainerOperatio n.executeOperation(SetContainerOperation.java:49)
at org.eclipse.jdt.internal.core.JavaModelOperation.r un(JavaModelOperation.java:709)
at org.eclipse.core.internal.resources.Workspace.run( Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelOperation.r unOperation(JavaModelOperation.java:775)
at org.eclipse.jdt.core.JavaCore.setClasspathContaine r(JavaCore.java:4703)
at com.springsource.server.ide.jdt.internal.core.clas spath.ServerClasspathContainerInitializer.initiali ze(ServerClasspathContainerInitializer.java:56)
at org.eclipse.jdt.internal.core.JavaModelManager.ini tializeContainer(JavaModelManager.java:2371)
at org.eclipse.jdt.internal.core.JavaModelManager$13. run(JavaModelManager.java:2301)
at org.eclipse.core.internal.resources.Workspace.run( Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.ini tializeAllContainers(JavaModelManager.java:2317)
at org.eclipse.jdt.internal.core.JavaModelManager.get ClasspathContainer(JavaModelManager.java:1679)
at org.eclipse.jdt.core.JavaCore.getClasspathContaine r(JavaCore.java:2554)
at com.springsource.server.ide.jdt.internal.core.util .ClasspathUtils.getClasspathContainer(ClasspathUti ls.java:81)
at com.springsource.server.ide.jdt.internal.core.util .ClasspathUtils.updateClasspathContainer(Classpath Utils.java:138)
at com.springsource.server.ide.jdt.internal.core.clas spath.ServerClasspathContainerUpdateJob.runInWorks pace(ServerClasspathContainerUpdateJob.java:70)
at org.eclipse.core.internal.resources.InternalWorksp aceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.j ava:55)

To "fix" the problem I kill and re-start eclipse and clean all projects to force a full re-build. After that the server can be started.

I'm using Eclipse 3.4 (I20080617-2000), Spring IDE 2.1.0.v200808011800 and 1.1.0.v200809100800 of the Server integration. The dm server's version is RC2.

Is this a known problem?

Regards,
Nils

[Christian Dupuis]

Nils,

this problem has been addressed with the GA version of the dm Server tools.

Sorry for the problem that may have caused on your end.

Christian

[Beta User]

Hi Christian,

thanks for your reply. I'll check out the GA release.

Nils