Changes between Initial Version and Version 1 of Ticket #1728


Ignore:
Timestamp:
Apr 13, 2018, 4:26:20 PM (7 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1728

    • Property Summary Petascope_If Petascope cannot connect to rasserver at start, it should ignore this error → Petascope_Cannot load GDAL JNI on Centos 7 with SELinux enabled

  • Ticket #1728 – Description

    initial v1  
    1 On Centos 7 VM with SELinux enabled, Petascope cannot connect to rasserver. However, it seems because of this error, then, Petascope doesn't continue with try to create new petascopedb when it doesn't exist and it leads to the error with Hibernate.
     1On Centos 7 VM with SELinux enabled, Petascope cannot connect to rasserver and '''cannot load GDAL Java JNI'''. Because of this error, then, Petascope doesn't continue with try to create new petascopedb when it doesn't exist and it leads to the error with Hibernate.
    22
    3 Full stack trace:
     3Real problem comes from the check for loading GDAL Java JNI after loading it in Petascope. However, because of SELinux, it returns this error
     4
     5
     6{{{
     7Caused by: java.lang.UnsatisfiedLinkError: org.gdal.osr.osrJNI.new_SpatialReference__SWIG_1()J
     8        at org.gdal.osr.osrJNI.new_SpatialReference__SWIG_1(Native Method)
     9        at org.gdal.osr.SpatialReference.<init>(SpatialReference.java:117)
     10        at petascope.util.CrsProjectionUtil.transform(CrsProjectionUtil.java:126)
     11}}}
     12
     13
     14
     15Full stack trace (old):
    416
    517