Am assuming that after upgrading to Java 8, you also changed tomcat to point to it. What is the exact version of tomcat that you are using?
LOL yes, tomcat is updated to use java 8, I made this mistake first!
7.0.26 tomcat, java 1.8.0_111, JRE only, headless.
@cintiadr is this in any way related to? Apache Tomcat/7.0.26 fails to run OpenMRS Platform 2.0 with the legacyui module
Maybe… is it ok to uninstall it for demo? If so, how can I do without causing drama, just deleting a couple of files?
If that’s the case, it would explain why some other environments work on the same tomcat version
I think its ok to uninstall it for demo.
@taremwatadeo since 2.5 is already released, when you did run the release again, you ended up by releasing reference application version 2.6, which should not be, and hence these failures: https://ci.openmrs.org/browse/RA-RA-2353. So i have deleted the 2.6 tag, which was a result of this, and changed from 2.7-SNAPSHOT back to 2.6-SNAPSHOT at https://github.com/openmrs/openmrs-distro-referenceapplication/commit/f7bbdad023a8230bd58974769a6dc7ef661c26ac
Well, apparently every other machine had a tomcat > 7.0.50, some of them appear to have it installed manually.
What is the recommended version of tomcat?
Anything above 7.0.26
By the way, i now see that demo.openmrs.org is getting exactly what i reported at Apache Tomcat/7.0.26 fails to run OpenMRS Platform 2.0 with the legacyui module
I did some sort of tomcat surgery on that machine (which I’m not particularly proud), and it’s up and running. We absolutely need to revisit this later.
How could I know upfront which version of JDK and tomcat a certain version of openmrs ref-app distro requires?
Revisiting this… can I get links to the current platform release as well as the file size summary so I can update this section too?
Yap! But it looks like I already updated the download page to 2.0.1 , so I’m not sure what @taremwatadeo is referring to now… Oh well, guess it’s fine!
lol, yeah… sorry I’m behind on this!
@pascal did a follow up on that, but apparently we were trying to reset the demo using old demo data.
That’s still disabled, so I assume he didn’t have the time to do it yet.