Robert, Are you sure that the rsync has finished by the time you touch the xml file?
Upgrading is generally a good idea :), but I can't think of anything specifically that would affect the hot redeployment (other than the war file not being fully copied). Might be able to comment more if you could post an example of the log messages. cheers Jan On 14 March 2014 02:33, Robert Nikander <[email protected]> wrote: > Hi, > > (I posted on stackoverflow first [1] but no answers, so I'll try here.) > > I have the usual web app deployer as described in the docs [2] and defined in > etc/jetty-deploy.xml. I use an xml file to define my web app context, so when > I push new code to my production server, I upload a new myapp.war file using > `rsync` and then touch that myapp.xml file. This works pretty well, but there > are few seconds where the app throws a NullPointerException or other > weirdness, and some users appear to be getting corrupt statically served > files (.js files from the war), so that they have to flush their browser's > cache for the app to work again. > > Is this supposed to work perfectly, or do you expect a brief dead period like > this? Is there a recommended way to deploy new code without the 2-second > snafu? > > Jetty is behind nginx with simple proxy configuration, if that matters. I'm > running 9.0.5, but could upgrade. > > thanks, > Rob > > > [1] > http://stackoverflow.com/questions/22357690/can-jetty-hot-redeployment-work-without-service-interruption > [2] http://www.eclipse.org/jetty/documentation/current/hot-deployment.html > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel <[email protected]> www.webtide.com 'Expert Jetty/CometD developer,production,operations advice' _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
