UnsatisfiedLinkError with gdal-java

[Dimitar Misev]

I'm not sure if these changes have anything to do about it, but on CentOS 7 now petascope throws this error on any projection request:

Caused by: java.lang.UnsatisfiedLinkError: org.gdal.gdalconst.gdalconstJNI.GDT_Unknown_get()I
	at org.gdal.gdalconst.gdalconstJNI.GDT_Unknown_get(Native Method)
	at org.gdal.gdalconst.gdalconstConstants.<clinit>(gdalconstConstants.java:12)
	at petascope.util.CrsProjectionUtil.getGeoTransformInTargetCRS(CrsProjectionUtil.java:147)
	at petascope.wms.handlers.service.WMSGetMapService.createBBoxGridSpatialDomainsForScaling(WMSGetMapService.java:836)
	at petascope.wms.handlers.service.WMSGetMapService.createGetMapResponse(WMSGetMapService.java:508)
	at petascope.wms.handlers.service.WMSGetMapService$$FastClassBySpringCGLIB$$d98998a3.invoke(<generated>)

I cleaned the /tmp/rasdaman_petascope, restarted tomcat, but doesn't have any effect for the error. Not sure what else to try.

[Dimitar Misev]

*these changes: ​http://rasdaman.org/changeset/703dc4d38aa4e5ca71be42c5b59102a827c1f60f#file0

[Dimitar Misev]

The gdal jar file is version 1.10.1:

/var/lib/tomcat/webapps/rasdaman/WEB-INF/lib/gdal-1.10.1.jar

while the gdal-java package is 1.11.4.

Could this be any issue? Although not sure why now while it worked fine before.

[Bang Pham Huu]

Did you try java -jar /var/lib/tomcat/ưebapps/rasdaman.war? Just want to make sure no problem because of tomcat external.

The error is not what I saw ony my system after the patch which only did clean /tmp/rasdaman_petascope/gdal_java/ folder and has bo effect to load JNI to tomcat.

[Dimitar Misev]

I think my patch for #1946 fixes this as well. It cleans the contents of /tmp/rasdaman_petascope/gdal_java/ on startup (instead of removing the whole /tmp/rasdaman_petascope/gdal_java/ after loading the native lib)