> From: CommonGround Softworks/Phil McNamara > [mailto:[EMAIL PROTECTED] > Subject: RE: How to change the SSL port > > It would seem to me that this demonstrates that I am editing > the correct server.xml instance.
Agreed. Sounds like something else has grabbed or disabled 443, especially since the Tomcat log shows a bind failure. > Possible that apache or a ssl module has already > done a "bind" internally to 443? Highly likely. Why are you running httpd? Unless the vast majority of your response pages are pure static content, Tomcat by itself will probably be faster (and certainly simpler to set up standalone). > Ran Netstat and nothing obvious jumped out at me. What platform are you running on? For Windows, try netstat -a -n -o and see if there's anything listening on 443, and if there is, use Task Manager to relate the pid to a running program (might be a service). I don't have access to a modern *nix system at the moment, so I can't suggest much for that environment, other than checking iptables. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
