| 351 | === Petascope fails to start with `UnsatisfiedLinkError` |
| 352 | |
| 353 | Sometimes you may see an exception like the following in the tomcat log: |
| 354 | {{{ |
| 355 | ERROR [14:03:40] SpringApplication@815: Application startup failed |
| 356 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'applicationMain': Invocation of init method failed; nested exception is java.lang.UnsatisfiedLinkError: 'void |
| 357 | org.gdal.gdal.gdalJNI.AllRegister()' |
| 358 | ... |
| 359 | Caused by: java.lang.UnsatisfiedLinkError: 'void org.gdal.gdal.gdalJNI.AllRegister()' |
| 360 | ... |
| 361 | }}} |
| 362 | This happens when you redeploy petascope, i.e. copy an updated version of rasdaman.war to Tomcat's webapps directory, but do not restart Tomcat subsequently. |
| 363 | |
| 364 | '''Solution:''' when redeploying rasdaman, make sure to ''restart Tomcat''. This is required because petascope uses a native library from GDAL; further information in the [https://cwiki.apache.org/confluence/display/tomcat/HowTo#HowTo-I'mencounteringclassloaderproblemswhenusingJNIunderTomcat Tomcat docs]. |
| 365 | |