Showing posts with label port. Show all posts
Showing posts with label port. Show all posts

Tuesday, June 24, 2014

java.net.SocketException: Connection reset by peer


The server is reporting "connection reset by peer" in the middle of a request. That means one of the following things:

  • The browser started a request and the user pressed STOP.

  • The browser started an request in one frame and JavaScript on another frame told it to go somewhere else (which has the same effect as a user pressing STOP).

  • You have a meta refresh reload someplace that is firing so fast that the previous request hasn't had a chance to complete yet. The five second periodicity makes me pretty suspicious of this.

  • You have some network component in between (a router or proxy) that is misbehaving.

  • You have some completely separate connection attempts going on that are disobeying the HTTP protocol (such as doing a telnet connection to port 8080 and then disconnecting).

Friday, May 23, 2014

HTTP Server Error Message 'make_sock could not bind to address'

Error Message:
Only one usage of each socket address is normally permitted.  : make_sock could not bind to address 0.0.0.0:80 no listening sockets available, shutting down
Unable to open logs

Problem:

Port 80 is listening by some process.

Solution:

Find which one uses the 0.0.0.0:80 port. Just stop it and keep it free. Then start up apache.

1) 'netstat -noa' will give you the PID of the process that reserves your precious port.

2) 'Ctrl-Alt-Del' and your Windows task manager, if you choose View >Select Colums and check PID, will show you which PID is stealing your port. Stop it.

3) Start HTTP server