Ioana Danes <[EMAIL PROTECTED]> writes: > We have a process that stops sequoia at 3 o'clock in > the night for a backup and after the backup is > finished it starts back sequoia. >>From the log below it looks like sequoia stopped > properly but at startup we've got the FATAL ERROR > "Cannot bind controller to requested IP xxx.xx.xx.xxx > because of (Address already in use)".
Such a message is usually caused by a TIME_WAIT state <http://www.developerweb.net/forum/showthread.php?t=2941> Last time I looked into this issue, I found out that Sun's 1.4 JDK was fond of SO_REUSEADDR (setting it on by default) which is supposed to avoid this <http://www.unixguide.net/network/socketfaq/4.5.shtml> <http://java.sun.com/j2se/1.4.2/docs/api/java/net/ServerSocket.html#setReuseAddress(boolean)> Buy maybe I dreamed. Which JDK are you running on? Anyway the TIME_WAIT state should not be longer than a couple of minutes. _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
