Issue 80383 - NativeLibraryLoader.loadLibrary, native methods, multiple classloaders
Summary: NativeLibraryLoader.loadLibrary, native methods, multiple classloaders
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 680m224
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-08-06 15:51 UTC by Stephan Bergmann
Modified: 2017-05-20 11:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2007-08-06 15:51:56 UTC
<> revealed the
following problem:

Assume jurt.jar (including is loaded
by the application classloader (e.g., because jurt.jar is added the the JVM
classpath) and java_uno.jar (including
is loaded by (the normal situation;
within OOo UnoClassLoader has some URLClassLoader as parent which in turn has
the application class loader as parent). 
bridges/source/jni_uno/java/com/sun/star/bridges/jni_uno/ l.
50 calls NativeLibraryLoader.loadLibrary to load the java_uno dynamic library
needed by the dispatch_call native method.  NativeLibraryLoader.loadLibrary uses
System.load or System.loadLibrary to load the library.  Later, calling
JNI_proxy.dispatch_call leads to an UnsatisfiedLinkError.  Obviously, the JVM
does not allow code loaded with the UnoClassLoader to resolve native methods
against libraries loaded through code loaded with the application classloader.
Comment 1 Stephan Bergmann 2007-08-06 15:54:22 UTC
Comment 2 Stephan Bergmann 2007-08-07 15:13:05 UTC
Comment 3 Martin Hollmichel 2007-12-07 13:00:18 UTC
set target to 3.x according to
Comment 4 Marcus 2017-05-20 11:31:42 UTC
Reset assigne to the default "".