I know this is not an uncommon issue and I recall it relates to a configuration problem if I’m not mistaken, but for the life of me I cannot fathom why two machines I am working with seem to exhibit this behaviour consistently. I have a couple of Windows test servers set up to facilitate an offline upgrade from 2.16 but I’m unable to resolve this on these two machines. I’ve seen this on Linux as well so assume it’s not OS related.
In a nutshell, the system appears to start up fine, I am able to login and access the system, create data elements, create users, etc. but when Tomcat is shut down, the database is cleared except for the aggregate tables (all other tables are dropped):
When Tomcat is started again, obviously the data is no longer there. As long as it’s running, all appears well in the tables:
I have attached a copy of the logs as well as my hibernate.properties file (dummy password) and my system variables. I’ve also attached a screenshot of the ‘about DHIS2’ page for reference.
As far as I can see, the only issues / errors on startup include:
A bunch of ERROR for database constraint drop scripts on startup – because the database does not yet exist – I assume these are benign.
Some WARN messages:
“[127.0.0.1]:5701 [dev] [3.2.1] No join method is enabled! Starting standalone. (HazelcastInstanceImpl.java [localhost-startStop-1])”
“RP discovery / realm validation disabled; (RealmVerifier.java [localhost-startStop-1])”
“Did not find any ViewResolvers to delegate to; please configure them using the ‘viewResolvers’ property on the ContentNegotiatingViewResolver (ContentNegotiatingViewResolver.java [localhost-startStop-1])”
Any idea what could be causing this?
Environment Variables.txt (4.68 KB)
hibernate.properties (506 Bytes)
Shutdown log.txt (1.62 KB)
Startup log.txt (153 KB)