I am new to EC2 (and Tomcat, for that matter), and I am trying to deploy a vanilla Tomcat 7 server to an Ubuntu 12.04.1 EC2 instance and access the default test site over HTTP.
My EC2 instance is running, and the Security Group includes port 80:
My /etc/tomcat7/server.xml config has been edited to listen for HTTP requests on port 80:
0
I have restarted my Tomcat 7 server via sudo service
On a Amazon EC2 instance we have nginx and tomcat running. Nginx is proxying all requests to tomcat on port 8080 running on the same instance.
This worked fine for a day, but then started seeing a lot of "upstream timed out (110: Connection timed out)" errors in the nginx logs and the site was inaccessible. Now tomcat is accessible all right at port 8080.
Am using JDK 1.6, tomcat 7.0.32, and Red Hat Linux.
(Plesk 10.4 centos 5.8 linux apache2 server, with Tomcat5 on port 8080 and Apache Solr)
I get "The connection has timed out" on requesting domain.com:8080 or www.domain.com:8080 or ip.ad.dr.ess:8080
Every reason I can find why this might be seems not to be the case:
Plesk thinks Tomcat is running fine and lists it as an active
service.
The firewall currently has an accept all rule on port 8080
Hi,
I have my apache running good and my tomcat with my OpenBluedragon CFML Engine running. My problem is i need to point a domain to use the port 8080, but not show the 8080. I think i have to proxy it, but no idea how. Im running webmin to manage the websites, and have install tomcat .
I read somewhere i need to edit the .conf for the website.
I have a t1.micro Amazon Linux AMI instance running.
I've got a single Tomcat 6 server that hosts a JSP app. We just spun up a new IIS 7.5 web farm to host our other internal apps. Currently the machine that hosts Tomcat is also running IIS 7 with the ISAPI filter loaded to provide front-end handling for the JSP app.
I am running several instance of Node and all of them run on different ports.
I need a way to be able to kill a particular instance of Node based on the port it is running (kill node instance binded to port n).
From my terminal I can easily do a "fuser -k xxxx/tcp" xxxx being the port.
The thing is, that is because I have the authorisation to do so.
I've a webapp deployed on tomcat server A, which is dependent on a couple of wars deployed on a different tomcat server B.