The webapps/openmrs folder is the "unzipped" webapps/openmrs.war file. Removing that forces tomcat to do a fresh unzip of the openmrs.war file, so all of your files would be back to what is contained in the war file and not your custom change.
If you remove webapps/something folder, then tomcat restarts the "something" webapp for you. Doing it on a running or stopped tomcat shouldn't matter. Ben On Mon, Sep 19, 2011 at 3:46 PM, Rob Borland <[email protected]> wrote: > Thanks for the good advice. I removed webapps/openmrs and all is well now. > > By the way, this time I removed the directory while tomcat was running. > Previously I always stopped tomcat before removing it. Was this the > problem perhaps? > > Regards, > Rob > > > On 9/19/2011 12:47 PM, Ben Wolfe wrote: > >> Its probably a cached jsp issue now. When openmrs starts it copies that >> file into the webapp/openmrs directory files. When you restart tomcat >> it doesn't remove the changes. I'm not sure why it fixed the main >> screen but not the others. >> >> You can clear your tomcat cache by removing the "work" directory and >> restarting. >> >> Ben >> >> On Mon, Sep 19, 2011 at 1:22 PM, Rob Borland <[email protected] >> <mailto:[email protected]**>> wrote: >> >> Thanks for the suggestion, Ben. >> >> The runtime properties file was indeed referencing a custom splash >> screen. I moved that runtime properties file away and let the >> initialization routine build the runtime properties file. >> >> After the initialization routine completes OpenMRS 1.6.3 opens >> correctly but I get the same error on any admin function, like >> Manage Modules, and also on logging out: >> >> >> An error has occurred! >> The following error happened somewhere on this page: >> javax.servlet.jsp.__**JspException: >> java.lang.__**IllegalArgumentException: You must specify a >> fromAttribute when using the patientSet portlet >> >> I couldn't retrieve the error log as the connection to the server >> went down. Maybe you can work out what's going wrong without this >> log? By the way, I have successfully upgraded several of our >> servers from 1.4.6 to 1.6.3 using their existing runtime properties >> file. >> >> Regards, >> Rob >> >> >> >> On 9/15/2011 1:19 PM, Ben Wolfe wrote: >> >> Why is PatientSet still being called? Do you have a custom header >> that you are referencing in your runtime properties? You need to >> re-sync that to the openmrs header for 1.6.x >> >> Ben >> >> On Thu, Sep 15, 2011 at 2:03 PM, Rob >> Borland<[email protected] >> <mailto:[email protected]**>__> wrote: >> >> >> Upgrading 1.4.6 to 1.6.3 I get the following error: >> >> * Unable to update the database. See >> server error logs >> for the full stacktrace. >> * There was an error while updating the >> database to the >> latest. file: liquibase-update-to-latest.__**xml. Error: >> Migration failed for >> change set >> liquibase-update-to-latest.__**xml::200912151032::n.nehete: >> * Reason: >> * SQL Precondition failed. Expected 'All >> encounters have >> a non-null encounter type.' got 'There are rows in the >> encounter table with >> an empty encounter type. Encounter type is a required field >> and must be >> populated. These encounters need to be fixed manually by >> setting an >> appropriate encounter type.' >> * : >> * Caused By: Preconditions Failed >> >> >> I manually set the 3,922 null values to an unused encounter >> type value. >> >> The upgrade completed but when I open any Admin function I >> get the following >> error: >> >> An error has occurred! >> The following error happened somewhere on >> this page: >> javax.servlet.jsp.__**JspException: >> java.lang.__**IllegalArgumentException: You must specify a >> fromAttribute when >> using the patientSet portlet >> >> The full log trace is attached. >> >> Regards, >> Rob >> >> ______________________________**_____________ >> >> To unsubscribe from OpenMRS Implementers' mailing list, send >> an e-mail to >> [email protected] >> >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU<[email protected]>> >> with "SIGNOFF >> >> openmrs-implement-l" in the body >> (not the subject) of your e-mail. >> >> [mailto:LISTSERV@LISTSERV.__IU**PUI.EDU <http://IUPUI.EDU> >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU<[email protected]> >> >?body=SIGNOFF%__**20openmrs-implement-l] >> >> >> ______________________________**_____________ >> >> To unsubscribe from OpenMRS Implementers' mailing list, send an >> e-mail to [email protected] >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU<[email protected]>> >> with "SIGNOFF >> >> openmrs-implement-l" in the body (not the subject) of your e-mail. >> >> [mailto:LISTSERV@LISTSERV.__IU**PUI.EDU <http://IUPUI.EDU> >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU<[email protected]> >> >?body=SIGNOFF%__**20openmrs-implement-l] >> >> >> ______________________________**_____________ >> >> To unsubscribe from OpenMRS Implementers' mailing list, send an >> e-mail to [email protected] >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU <[email protected]>> >> with "SIGNOFF >> >> openmrs-implement-l" in the body (not the subject) of your e-mail. >> >> [mailto:LISTSERV@LISTSERV.__IU**PUI.EDU <http://IUPUI.EDU> >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU <[email protected]> >> >?body=SIGNOFF%__**20openmrs-implement-l] >> >> >> ------------------------------**------------------------------** >> ------------ >> Click here to unsubscribe >> >> <mailto:LISTSERV@LISTSERV.**IUPUI.EDU <[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:LISTSERV@LISTSERV.**IUPUI.EDU <[email protected]> > ?body=SIGNOFF%**20openmrs-implement-l] > _________________________________________ 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]
