Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Any way to set reuseAddress for the stop port of a Jetty server?
The ShutdownMonitor's ServerSocket doesn't do that currently.
https://github.com/eclipse/jetty.project/blob/master/jetty-server/src/main/java/org/eclipse/jetty/server/ShutdownMonitor.java#L297

Sounds like a feature request.

Please file it at ...

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Fri, Feb 27, 2015 at 12:49 PM, Ramkumar R. Aiyengar <andyetitmoves@xxxxxxxxx> wrote:
Currently, when a jetty server has to be force killed (possibly due to a bad GC day leading to the JVM being completely locked, or the OOM killer script passed to Java stepping in and killing the process), usual service monitoring mechanisms will respond by respawning the process. When this happens, there's a good chance that the stop port would still be in TIME_WAIT state and fails to bind with an 'Address already in use' error.

Java ServerSockets offer a way to avoid this by using the `setReuseAddress` method which sets socket option SO_REUSEADDR, should this be set, or an option be provided for this? Or is there some other way to do this I am missing?


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Back to the top