Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] How to overcome partial deployment

Unfortunately no,

The whole point of quickstarting is to avoid unpacking, scanning the entire webapp.  If we had to scan a directory to check that it was the same contents of the war, then we may as well unpack it.

If you want that behaviour, just always delete the folder before starting.   Better yet, don't deploy a war file - instead deploy unpacked directories and avoid the whole issue of partially unpacked wars.


On Thu, 8 Aug 2019 at 17:51, deepak dhandapani <deepakd020395@xxxxxxxxx> wrote:
Hello Team Jetty,

I'm facing an situation whereby a partial deployment is happening when using QuickStartWebApp in the machine where we installed Jetty and deployed multiple web application (WAR) file. During the extraction of the WAR contents, Jetty deployment is interrupted due to external factors, say I'm doing machine power OFF. Here, jetty does partial deployment and after the restart of the machine, jetty doesn't extract the WAR contents since there will already be a folder extracted but partially.

My question is, is there an mechanism/configuration available in Jetty to figure out the partial deployment and redeploy the WAR using QuickStartWebApp even if we have folder already extracted from the WAR file? If Yes, can I have references on how to do it?

Thanks in advance!
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top