Project, the need to use C library, through the JNI calls, C library package file name called: libecgqrs. DLL, libecgqrs. So.

I tested under local Windows, Java loaded. DLL and. So documents are no problem,

The local loading method is: the System. The load (" D:/libecgqrs. DLL "); Or System. The load (" D:/libecgqrs. So "); They are both checked, no problem,

In the ECS loading ways: ali cloud System. The load ("/home/ecglibfile/libecgqrs. So "); Or System. The load ("/home/ecglibfile/libecgqrs. DLL "); Loading way is same, only the absolute path is different, they are both loading failure, error message is as follows:

The Java HotSpot (TM) 64 - Bit Server VM warning: You have The loaded library/home/ecglibfile/libecgqrs. So which took have disabled stack guard. The VM will try to fix The stack guard now.
It 's highly It that fix the library with' execstack - c & lt; Libfile> ', or the link it with 'z noexecstack'.
Org. Springframework. Web. Util. NestedServletException: Handler dispatch failed; Nested exception is Java. Lang. UnsatisfiedLinkError:/home/ecglibfile/libecgqrs. So:/home/ecglibfile/libecgqrs. So: invalid ELF header (Possible cause: endianness mismatch)

Under Caused by: Java. Lang. UnsatisfiedLinkError:/home/ecglibfile/libecgqrs. So:/home/ecglibfile/libecgqrs. So: invalid ELF header (Possible cause: endianness mismatch)
The at Java. Lang. This $NativeLibrary. Load (Native Method)
The at Java. Lang. This. LoadLibrary0 (1941). This Java:
The at Java. Lang. This. LoadLibrary (1824). This Java:
The at Java. Lang. Runtime. Load0 (809). The Runtime Java:
The at Java. Lang. System. The load (System. Java: 1086)

This aspect of the brothers, know this is why not? Online solution ~ ~ ~ ~