The next most common problem then would be that the PipeConnection class
does not find the lipjpipe.so JNI library at all. It tries to load it
at the end of a static block, near the start of
jurt/com/sun/star/lib/connections/pipe/PipeConnection.java. First thing
is that it catches and ignores all Throwables, printing stack traces
there might give you a clue. Second, the mechanism to find the library,
NativeLibraryLoader, is also implemented in jurt; maybe debugging into
it helps. (Other approaches might be to use things like strace or
LD_DEBUG on the JVM process, to find out what gets loaded.)
Hope this helps,
-Stephan
On 03/17/10 22:51, K S wrote:
Dear Stephan!
I have checked this variant with the flag you noted, but the problem still
exists. Interesting moment is that when I create a bootstrap application
with OpenOffice plugin for NetBeans, its code successfully works...
-Kirill
2010/3/15 Stephan Bergmann <[email protected]>
On 03/12/10 21:13, K S wrote:
Caused by: java.lang.UnsatisfiedLinkError:
com.sun.star.lib.connections.pipe.PipeConnection.createJNI(Ljava/lang/String;)I
That class tries to load libjpipe.so JNI library. The most typical problem
with that nowadays is that either your OOo (and hence libjpipe.so) is 32 bit
and the Java process you start is 64 bit, or vice versa. At least with
recent Sun JVMs, you can control whether the Java process is 32 or 64 bit
via -d32 resp. -d64 command line switches.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
