[Monotone-devel] Updated Issue 136 - Unhandled runtime error when second server instance starts on occupied port in TIME_WAIT status (monotone)

[code]

Hello,

The following issue has been updated:

136 - Unhandled runtime error when second server instance starts on occupied 
port in TIME_WAIT status
Project: monotone
Status: New
Reported by: Thomas Keller
URL: https://code.monotone.ca/p/monotone/issues/136/
Labels:
 Type:Incorrect Behavior
 Priority:Medium

Comments (last first):

# By Thomas Keller, Jan 30, 2011:



 Summary: Unhandled runtime error when second server instance starts on 
occupied port in TIME_WAIT status

# By Thomas Keller, Jan 22, 2011:

This was reported by Hugo Cornelis on a Linux machine; I could not reproduce 
that on Mac OS X, so this is just for the record right now.

Steps to reproduce the problem:
-------------------------------

1) Start a server
2) Connect to this server with a client and close the connection
3) Check that the socket is still in TIME_WAIT status
   (netstat -an | grep 4691)
4) Try to start another server on the same port

Expected result:
----------------

mtn: network error: bind(2) error: Address already in use

Actual results:
---------------

mtn: fatal: std::runtime_error: network error: listen(2) error: Address already 
in use
mtn: this is almost certainly a bug in monotone.
...

Output of `mtn version --full`:
-------------------------------

0.99.1

Attachments:
- strace.out.bz2 - 5.01 kB
  https://code.monotone.ca/p/monotone/issues/view/attachment/19/strace.out.bz2
- ltrace.out.bz2 - 299.69 kB
  https://code.monotone.ca/p/monotone/issues/view/attachment/20/ltrace.out.bz2




--
Issue: https://code.monotone.ca/p/monotone/issues/136/