v2.0 beta0 has even a bigger problem in that it calls the database using odk_unit username instead of odk_user, and odk_db instead of odk_prod database i.e. I don't understand how such a bug got into the final build. Redeploy the ODKAggregate.war into /opt/tomcat/webapps Which will place the newly created war file one directory up, in order not to include the mod directory in the root of the web application. Repackage the repaired ODKAggregate.war file by going back to.
> mv ODKAggregate-settings-2.jar ODKAggregate-settings.jar mod/WEB-INF/lib and delete the broken ODKAggregate-settings.jar file and rename the one we just made Jdbc.driverClassName= jar -cvf ,/ODKAggregate-settings-2.jar * This is the file from v1.7.0 and v1.7.1 is similar: So the I did some troubleshooting and noticed that there were missing lines in the jdbc.properties definition file!! WARNING: Exception encountered during context initialization - cancelling refresh attempt: .BeanDefinitionStoreException: Invalid bean definition with name 'dataSource' defined in class path resource : Could not resolve placeholder 'jdbc.driverClassName' in string value " $"Īt .(PlaceholderConfigurerSupport.java:223) Then I checked the Tomcat log files /opt/tomcat/logs/Catalina.out I kept getting the redirect to a 404 Not Found when going to. Then I repeated the exact same steps to go from v1.7.1 to v2.0.0 and everything broke. Ran the RUN file, generated the WAR and plopped it into my /opt/tomcat/webapps folder and restarted, everything worked beautifully. My server was running ODK v1.7.0 on Ubuntu Server 18 previously and I used the ODK-Aggregate-v1.7.1-Linux-圆4.run.zip for my next hop. I have just busted by head trying to debug ODK-Aggregate-v2.0.0-Linux-圆4.run.zip.
0 kommentar(er)
