Spring STS (New Server Wizard)

Question

The following is being experienced within Spring STS: In the process of Defining a New Server, the Server name is not populating for me to be able to click 'Next'. Previous to this, I selected Tomcat v7.0 Server, while desiring to get the most recent Tomcat server. This may have inadvertently been deleted rather than deselected in the process of learning how to overcome an error such as this:

"Could not load the Tomcat server configuration at /// the configuration may be corrupt or incomplete ~/conf/catalina.policy".

Attempted resolve: When I click on Tomcat v6.0 Server, the Server name field populates with 'Tomcat v6.0 Server at localhost'. I attempted to manually type an entry of 'Tomcat v7.0 at localhost' yesterday, but does not work. It seems it has nothing close to it to find, not even default. I would like to understand how I can re-establish what I originally had. Although I will still need to overcome the error message that I encountered which may have led to me inadvertently deleting a pointing mechanism to what was Tomcat 7.

I am installing this on Linux. It is difficult to find definitive resolve.

What is a remedy that makes sense - for being able to then get apache-tomcat-7.0.xx (most recent) to be recognized?

Answer 1

Well, it looks like Tomcat server 7 wasn't set up properly. Have you followed these instructions?

http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/InstallTomcat/InstallTomcat.html

Answer 2

try this: go to window->preferences->server->runtime environments->click remove apache tomcat. then reinstall your tomat

Answer 3

I had a similar problem with Linux Mint 17.3 and Spring Tools Suite. I would create a new server and click "run on server" for my dynamic web project. It would work one time and then I would get the same error you are getting this caused a great deal of frustration at work.

I have now SOLVED the issue. 1) create a new Pivotal TC Server v3.0-v3.1
2) give your host a name or keep all the defaults
3) create new instance
4) name the instance and use the "base" template
5) the next page is where I had the issue!!
6) Please enter the user account that should start the instance when using the bin/init.d.sh script. by default "tcserver" is in there and I had always just clicked next. Do NOT do that. erase tcserver and put your username that you log into when you start your computer.

now my server runs without errors. hope this saves some people from the frustration I experienced.