You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/04/03 21:53:50 UTC
DO NOT REPLY [Bug 12287] -
No Available Listening Sockets
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12287>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12287
No Available Listening Sockets
wrowe@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From wrowe@apache.org 2003-04-03 19:53 -------
Folks, this is yet another flavor of broken Win32 software. We are afraid
we can't do a whole lot to help you.
Roshan Joseph ... you likely have Tomcat configured to be an HTTP (port 80)
server as well as a backend java engine. That's not valid.
Learn the command netstat -an which shows you every port some program
or the kernel is listening on. You will either find a listener documented
on port 80, or you have firewall or antivirus software installed that causes
Apache some grief. Or some module you installed has actually changed the
version of the Win32 socket DLLs. There is no way we can help with user
configuration problems on this forum... it's strictly for tracking bugs
within the Apache software itself.
Final suggestion - try 2.0.45 (no special APR patch required) for a few
new fixes to apr and httpd that might impact your success.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org