Re: war file incompletely deployed
Am 08.11.2016 um 10:01 schrieb André Warnier (tomcat): On 08.11.2016 09:47, Christoph P.U. Kukulies wrote: Am 07.11.2016 um 19:09 schrieb Caldarale, Charles R: From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] Subject: Re: war file incompletely deployed This makes sense somehow, but wouldn't a local move or copy from within the server's filesystem have the same complications? No, a local mv or rename in a modern file system simply changes the directory structure; no copy is performed. A copy does stand a chance of being caught in the middle, but the timing window is much, much smaller. Best to use mv/rename whenever possible. - Chuck So 'touch' a .LCK file in a place outside webapps, copy over the file, when copy done remove the .LCK file. On the server a background process is running watching for the .LCK file. when it's gone, it does the 'mv'. (a mv can imply a copy though when it goes across filesystems on different drives). Would it not be simpler to just rename the .war file, to .war.lck, then copy it to the destination, then rename it (in place) to .war when the copy is finished ? Tomcat should not even consider .war.lck files, right ? Ah, yes, forgot about that, that Tomcat wouldn't eat anything that's being thrown at it :) -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: war file incompletely deployed
On 08.11.2016 09:47, Christoph P.U. Kukulies wrote: Am 07.11.2016 um 19:09 schrieb Caldarale, Charles R: From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] Subject: Re: war file incompletely deployed This makes sense somehow, but wouldn't a local move or copy from within the server's filesystem have the same complications? No, a local mv or rename in a modern file system simply changes the directory structure; no copy is performed. A copy does stand a chance of being caught in the middle, but the timing window is much, much smaller. Best to use mv/rename whenever possible. - Chuck So 'touch' a .LCK file in a place outside webapps, copy over the file, when copy done remove the .LCK file. On the server a background process is running watching for the .LCK file. when it's gone, it does the 'mv'. (a mv can imply a copy though when it goes across filesystems on different drives). Would it not be simpler to just rename the .war file, to .war.lck, then copy it to the destination, then rename it (in place) to .war when the copy is finished ? Tomcat should not even consider .war.lck files, right ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: war file incompletely deployed
Am 07.11.2016 um 19:09 schrieb Caldarale, Charles R: From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] Subject: Re: war file incompletely deployed This makes sense somehow, but wouldn't a local move or copy from within the server's filesystem have the same complications? No, a local mv or rename in a modern file system simply changes the directory structure; no copy is performed. A copy does stand a chance of being caught in the middle, but the timing window is much, much smaller. Best to use mv/rename whenever possible. - Chuck So 'touch' a .LCK file in a place outside webapps, copy over the file, when copy done remove the .LCK file. On the server a background process is running watching for the .LCK file. when it's gone, it does the 'mv'. (a mv can imply a copy though when it goes across filesystems on different drives). -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: war file incompletely deployed
> From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] > Subject: Re: war file incompletely deployed > This makes sense somehow, but wouldn't a local move or copy from within > the server's filesystem have the same complications? No, a local mv or rename in a modern file system simply changes the directory structure; no copy is performed. A copy does stand a chance of being caught in the middle, but the timing window is much, much smaller. Best to use mv/rename whenever possible. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: war file incompletely deployed
This makes sense somehow, but wouldn't a local move or copy from within the server's filesystem have the same complications? In other words: would a tomcat stop/start be required in any situation to be on the safe side? -- Christoph Am 07.11.2016 um 18:31 schrieb Caldarale, Charles R: From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] Subject: war file incompletely deployed I started developing a webapp (Windows 7, tomcat 7/x64). I generate a WAR file using eclipse/maven. Once built I copy over the war file to a network share on the tomcat server. The share is the tomcat webapps directory. Once done tomcat autodeploys the .war file into the webapps subdirectory with the name of the war file (without extension). Copying over a network link to the final deployment location can be problematic. Tomcat's auto-deployment may see a partially written file and initiate deployment prematurely. Best if you can copy the file to a temporary location on the target server and then mv or rename it to the desired spot. - Chuck - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: war file incompletely deployed
> From: Christoph P.U. Kukulies [mailto:k...@kukulies.org] > Subject: war file incompletely deployed > I started developing a webapp (Windows 7, tomcat 7/x64). I generate a > WAR file using eclipse/maven. Once built I copy over the war file > to a network share on the tomcat server. The share is the tomcat webapps > directory. > Once done tomcat autodeploys the .war file into the webapps subdirectory > with the name of the war file (without extension). Copying over a network link to the final deployment location can be problematic. Tomcat's auto-deployment may see a partially written file and initiate deployment prematurely. Best if you can copy the file to a temporary location on the target server and then mv or rename it to the desired spot. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
