This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I have installed Tomcat 7 and java 1.6 on my Ubuntu 12.04 x64 VPS.
I am trying to set up a tomcat 7 server in this way-
domain1.com--> is a vhost with its own deployment directory.
domain2.com--> is a vhost with its own deployment directory.
Now, I have created and installed an SSL Certificate corresponding to domain1.com. I have also installed APR connector for Tomcat and added the config entry for SSL @ port 8443 --> tomcat's server.xml.
I have also left the connector for port 8080 as it is(unchanged).
Now, when I try to access http://<IP_ADDRESS>:8080/manager/html/ it works. And the host manager app also works at the IP address and port=8080. Now I have added 2 VHOSTS--> domain1.com and domain2.com. This also happens successfully.
However the following :
gives a error --
"Webpage is not available-- Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection."
While gives error-
HTTP Status 404 - /manager/html
type Status report
description The requested resource (/manager/html) is not available.
We don't have many rules on the JavaRanch, but one that we are quite serious about is that people use their real names. No "handles", aliases, or company names. If you're not sure about this, see
An IDE is no substitute for an Intelligent Developer.
Arvind Ik Chari
Joined: Feb 16, 2013
I was not aware of that- I have filled in the name change request form.
Tomcat's architecture is such that ports are assigned at a very high level in the server. So you really cannot assign a specific port to a specific app or virtual host.
There's a recent thread in this forum where someone did want, in fact to reserve a special port number to an administrative app and we discussed this sort of thing in detail. You might want to search for that thread and read it.
You can use a front-end routing/proxy program such as Apache HTTPD to route traffic to a selected virtual host/application based on its URL format (including whether it's http or https), but Tomcat can't be set up to listen selectively.