There's already an issue in JIRA for this problem. http://issues.apache.org/jira/browse/DIRMINA-152
Please add your feedback as comments to that issue. Also, you should read through the comments since Julien has already done some tests using the addShutdownHook() approach. He has posted his findings as comments on that issue. /Niklas Alessandro Torrisi wrote: > Thanks for the answers...but I don't think C++ sucks ;-) > > Now I'm going to try the solution proposed by Alex Karasulu and I will > post here feedbacks about it ! > > Runtime.getRuntime().addShutdownHook( Thread hook ) > > Best regards Emmanuel, > Alessandro Torrisi > > > On 07/gen/06, at 17:44, Emmanuel Lecharny wrote: > >> Alessandro Torrisi a écrit : >> >>> I give my poor opinion on this. I think this is logically incorrect, >> >> >> It's logically incorrect, I just tried to give you a workaround... >> >>> 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++ ? >> >> >> >> Because C++ sucks, when you have tried Java ;-) >> >>> 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... >> >> >> The GUI will work the same way than a service. What we need, here, >> and you are right, is a way to shutdown correctly the server. We >> don't have it currently, but we will work on it for sure ! (Any help >> appreciated ;) >> >>> >>> 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 ! >> >> >> yeah. My bad. We will dig this issue deeper and try to find a better >> solution than this ugly workaround ;) >> >> Sorry for the inconvenience... >> >> -- Emmanuel Lécharny >> >
