[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Does Nio connector allow seamless redeploy of new server process ?
|
The behavior you are describing we have only seen on Microsoft Windows.
On all flavors of Unix and OSX it will throw a binding exception on the second instance.
--
Developer advice, services and support
from the Jetty & CometD experts
On Wed, Mar 20, 2013 at 4:32 AM, Kristian Rosenvold
<kristian.rosenvold@xxxxxxxxx> wrote:
Somewhat accidentally I learned that SelectChannelConnector allows a
second jetty to be started that will basically take over the port once
the first jetty process terminates.
I somehow assume this feature is intentional; I couldn't find any docs
about it in jetty. Are there any docs I can read about this feature
anywhere ?
What kind of behaviour can I expect from this mechanism, is there any
way to gracefully make the old instance finish requests to achieve
near zero downtime ?
Regards,
Kristian Rosenvold
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
