Got it Konstantin, Thank you... But stopping and starting would mean that
we spend time in between and wont be able to instance switch?.
Thanks
Suresh
On Fri, Nov 8, 2013 at 3:06 AM, Konstantin Kolinko
<knst.koli...@gmail.com>wrote:
> 2013/11/8 Suresh Mathew <suresh....@gmail.com>:
> > All,
> > Can we add a new state to bind the port after the startup is completed.
> >
> > Right now start will start the app after binding to the port. We can
> delay
> > the binf after connector is started using bindOnInit. But this is a
> little
> > different.
> >
> > StartOnly - Starts The Server and the apps.
> > Bind - Then Binds it to the Port and the server starts listening
> > Unbind - Unbinds the port, but keep the server running not listening
> > Stop- Will Stop(and unbind if bound) the server.
> >
> > The usecase for this is instant rollback (which can also be achieved with
> > parallel deployment, but within the same process), Two servers will be
> > running but one will be bound, and if there is a need to rollback to the
> > old version, we can unbind this and bind the other.
> >
> > This will also help make the best use of the PORT_REUSE of the latest
> 3.9.0
> > linux kernel feature.
> >
> > Does that make any sense?
> >
> >
>
> Bind it to a random port ("0"), then stop & reconfigure & start it via JMX?
>
> Note that it would not work if you run Tomcat via jsvc and want to
> bind it to a privileged port (80). JSVC drops privileges once the init
> completes.
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>
