If you're using tomcat that comes with the server, I think it's by default running on the background. I'm not really sure about tomcat that you download manually. I think if you run the tomcat script and it's not returning the initial shell prompt, that means the tomcat will die if you close the terminal. I personally never use tomcat that I download by myself.
On Fri, Sep 30, 2011 at 11:14 AM, Rob Borland <[email protected]> wrote: > Does this also apply if the connection to the shell which started tomcat > after dropping the new war file into place gets dropped? > > Regards, > Rob > > On 9/30/2011 8:39 AM, Mhawila wrote: >> >> This is very fantastic feature. >> On 09/29/2011 12:40 PM, Ben Wolfe wrote: >>> >>> Correct, it will run in the background. >>> >>> With 1.8, if you return to the maintenance page later it says that its >>> in progress and you need to be patient. >>> >>> With 1.9 it will show you the progress. >>> >>> Ben >>> >>> On Wed, Sep 28, 2011 at 11:15 AM, Nyoman Ribeka <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Rob, >>> >>> If you drop the connection during the upgrade process, the upgrade >>> process will not be stopped. It will still running in the background. >>> >>> But I think you shouldn't open the webpage again until it's done >>> because it will take the maintenance page and asking you to upgrade >>> again (cmiiw). You can check the log file to see if the upgrade >>> process is done or not :) >>> >>> On Wed, Sep 28, 2011 at 10:20 AM, Rob Borland >>> <[email protected] <mailto:[email protected]>> wrote: >>> > We need to upgrade OpenMRS on remote Linux servers with very poor >>> > connectivity. >>> > >>> > Currently we are opening a console using "screen", dropping the >>> new war file >>> > into the tomcat work directory then detaching the console to try >>> to avoid >>> > the process dying when we inevitably lose the connection. Maybe >>> there's a >>> > better way? >>> > >>> > Does dropping the http connection to the web app affect the >>> upgrade in >>> > progress? >>> > >>> > Regards, >>> > Rob >>> > >>> > _________________________________________ >>> > >>> > To unsubscribe from OpenMRS Implementers' mailing list, send an >>> e-mail to >>> > [email protected] <mailto:[email protected]> >>> with "SIGNOFF openmrs-implement-l" in the body >>> > (not the subject) of your e-mail. >>> > >>> > [mailto:[email protected] >>> >>> <mailto:[email protected]>?body=SIGNOFF%20openmrs-implement-l] >>> > >>> >>> >>> >>> -- >>> Thanks, >>> >>> Nyoman Ribeka >>> >>> _________________________________________ >>> >>> To unsubscribe from OpenMRS Implementers' mailing list, send an >>> e-mail to [email protected] >>> <mailto:[email protected]> with "SIGNOFF >>> openmrs-implement-l" in the body (not the subject) of your e-mail. >>> >>> [mailto:[email protected] >>> >>> <mailto:[email protected]>?body=SIGNOFF%20openmrs-implement-l] >>> >>> >>> ------------------------------------------------------------------------ >>> Click here to unsubscribe >>> <mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l> >>> from >>> OpenMRS Implementers' mailing list >> >> >> _________________ University Computing Centre - 'Professionalism, >> Customer Care and Technological foresight' >> ------------------------------------------------------------------------ >> Click here to unsubscribe >> <mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l> >> from OpenMRS Implementers' mailing list > > _________________________________________ > > To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-implement-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l] > -- Thanks, Nyoman Ribeka _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
