org.eclipse.core.runtime.CoreException

Could not load the Tomcat server configuration at /Servers/SpringSource tc Server Developer Edition v2.1-config. The configuration may be corrupt or incomplete.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web987

  • via SpringSource Issue Tracker by Kris De Volder (c), 1 year ago
    Could not load the Tomcat server configuration at /Servers/SpringSource tc Server Developer Edition v2.1-config. The configuration may be corrupt or incomplete.
  • via SpringSource Issue Tracker by Kris De Volder (c), 1 year ago
    Could not load the Tomcat server configuration at /Servers/SpringSource tc Server Developer Edition v2.1-config. The configuration may be corrupt or incomplete.
  • via Stack Overflow by amphibient
    , 1 year ago
    Could not load the Tomcat server configuration at \Servers\localhost-config. The configuration may be corrupt or incomplete.
  • Stack trace

    • org.eclipse.core.runtime.CoreException: Could not load the Tomcat server configuration at /Servers/SpringSource tc Server Developer Edition v2.1-config. The configuration may be corrupt or incomplete. at org.eclipse.jst.server.tomcat.core.internal.Tomcat60Configuration.load(Tomcat60Configuration.java:313) at com.springsource.sts.internal.server.tc.core.TcServerConfiguration.load(TcServerConfiguration.java:227) at com.springsource.sts.internal.server.tc.core.TcServer.getTomcatConfiguration(TcServer.java:207) at com.springsource.sts.internal.server.tc.core.TcServer.getTomcatConfiguration(TcServer.java:1) at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.getTomcatConfiguration(TomcatServerBehaviour.java:80) at com.springsource.sts.internal.server.tc.core.TcServerBehaviour.getTomcatConfiguration(TcServerBehaviour.java:100) at com.springsource.sts.internal.server.tc.core.TcServerBehaviour.getTomcatConfiguration(TcServerBehaviour.java:1) at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.setupLaunch(TomcatServerBehaviour.java:495) at com.springsource.sts.internal.server.tc.core.TcServerBehaviour.setupLaunch(TcServerBehaviour.java:115) at org.eclipse.jst.server.tomcat.core.internal.TomcatLaunchConfigurationDelegate.launch(TomcatLaunchConfigurationDelegate.java:96) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:695) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3209) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3159) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:359) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.