Change bundled OpenSSL SONAME for Linux Platforms #988
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
JDK-bundled libcrypto-semeru.so and libssl-semeru.so used to have the same SONAME as the operating system libcrypto.so and libssl.so. When the dynamic linker tries to resolve a libssl.so’s dependency on libcrypto.so.3, it will match the already-loaded $JAVA_HOME/lib/libcrypto-semeru.so (whose SONAME was also libcrypto.so.3). These two libcrypto.so.3 come from different distributions and their symbol versions are incompatible, this will hit an exception.