Got it - had to change 8443 to 443.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Looks like something else is listening on port 80. Is IIS running?
Larry
On 4/25/07, John Pedersen [EMAIL PROTECTED] wrote:
Hi,
I have an app running fine on port 8080, but nothing works when I
switch to port 80 -
in server.xml, changing:
Connector port=8080 protocol=HTTP/1.1
The reason might be related with administration rights. Not every user has the
right to run an application which listens to requests on port 80.
since 8080 1024, so you don't live any problem.
I couldn't get the whole picture in my head actually. I just wanted to remind
this.
Regards
hs
likely IIS by default! The WWW publishing service.
-Original Message-
From: John Pedersen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 9:55 AM
To: users@tomcat.apache.org
Subject: problem switching to port 80
Hi,
I have an app running fine on port 8080, but nothing works
Also check if something is using the other ports that Tomcat uses -
the shutdown port, SSL port, other connectors (e.g. AJP), clustering
ports. They're all found in server.xml (but some are probably
commented out).
--
Len
On 4/25/07, John Pedersen [EMAIL PROTECTED] wrote:
Hi,
I have an app
From: John Pedersen [mailto:[EMAIL PROTECTED]
Subject: problem switching to port 80
I guess there must be something else using port 80? but I can't see it
( tried netstat).
Use netstat -an; plain netstat without options may not show
everything.
The problem may not be port 80, since Tomcat
netstat -an with Tomcat stopped:
Proto Local Address Foreign AddressState
TCP0.0.0.0:1350.0.0.0:0 LISTENING
TCP0.0.0.0:4450.0.0.0:0 LISTENING
TCP0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP
Not sure what happened - but it is working now. Now I just have to try
to find out if it was something I switched off, or someone else
changing the networks settings.
Thanks for the fast response guys.
If I get a definite answer to what went wrong, I will post it for
future reference.
John
My personal preference for ferreting out port problems in Windows is
TCPView
(http://www.microsoft.com/technet/sysinternals/Networking/TcpView.mspx).
It'll offer up a fair amount of info on the process that has the
conflicting port.
--David
John Pedersen wrote:
Hi,
I have an app running
Type netstat -noa
It will give you the PID...
Then Ctrl Alt Delete - Process's and View - Select Tab PID
Then you can match up the application on port 80 exactly
Bet its SKYPE... ;)
- Original Message -
From: John Pedersen [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent:
10 matches
Mail list logo