I have followed the installation guide available here: http://www.excelsior-usa.com/articles/tomcat-amazon-ec2-basic.html
I am running an AWS EC2 instance with the Amazon Linux AMI (Amazon Machine Image): Amazon Linux AMI 2014.03.2 (HVM) - ami-d13845e1
I have installed Java 7 on the machine:
${JAVA_HOME}/bin/java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (amzn-2.5.1.2.43.amzn1-x86_64 u65-b17)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
And I've installed Tomcat7. When I started up the server and try to connect to my machine's address on port 8080, I get a blank page or the request simply hangs. I have installed all of the Tomcat7 packages (see step #5 in the article linked at start of this post) and so I should be seeing the default Tomcat home page (I'd even be happy with a 400 response code!)
I can confirm that my security group is correct (I've previously run Jetty from port 8080 with this same security group). I also followed the guide's command to check if tomcat7 is running and listening to port 8080:
$ sudo fuser -v -n tcp 8080
USER PID ACCESS COMMAND
8080/tcp: tomcat 1669 F.... java
When I attempted to run the version command, I got a very strange response:
$ sudo service tomcat7 version
/usr/sbin/tomcat7: line 21: .: /etc/sysconfig/: is a directory
/usr/sbin/tomcat7: line 25: cd: HOME not set
Error: Could not find or load main class org.apache.catalina.util.ServerInfo
I've tried to Google around for solutions and I tried stuff like this but nothing has resulted in success. I'm not sure if the above message I'm receiving from version is related to why my tomcat7 isn't working but it is the only thing I can think of to try and troubleshoot.
Has anyone experiences similar? Does anyone have ideas of what might be wrong? Anyone else sad when they follow a wonderful guide to do something 'easy' and it still doesn't work? :-P
As a side note, I have installed Tomcat7 successfully on my local Windows7 machine via the .exe file and it works beautifully. I'm trying to develop locally and then push to my Amazon Web Service but it seems like I have to solve this problem first.