I give my poor opinion on this. I think this is logically incorrect,
because Java is potentially platform independent.
Setting some parameters on the platform I'm going to violate this kind
of contract, so why don't use C++ ?
And sorry I don't understand a GUI implementation to stop a server...I
want to do a unix service, I want to start, stop or
restart my service with the classic init.d concept...
Then why when I start a simple SocketServer and accept connections with
that, I can start, restart or stop it as usual ?
What is the big difference ? Why I don't have to modify platform
parameters for a SocketServer ?
Another thing is that in the way you suggested I have to put all
necessary informations to modify parameters on all Unix platforms !
In Mac Os X I don't have a sysctl.conf !
Let me know,
best regards, Alex.
Emmanuel Lecharny wrote:
Alessandro Torrisi a écrit :
I downloaded today the SVN trunk of Mina, I think it is always the
same error you write about from many days.
When I start the server and I stop it and immediately start again I
can see this:
Do you use kill to stop the server ? In this case, you will find that,
depending on your TCP parameters, the socket will still be open.
You may want to modify some parameters in /etc/sysctl.conf, like
tcp_fin_timeout, to set it to a lower value.
net.ipv4.tcp_fin_timeout = 15 // Set the timeout to 15 seconds,
instead of the default 60 secs. (don't forget to restart your network
interface !)
But we need to work on a better way to stop the server (A GUI will
probably be developped sooner or later)
-- Emmanuel Lécharny
