|
From: Leif M. <le...@ta...> - 2005-04-27 01:03:32
|
Andrew,
DLLs that are loaded directly as JNI libraries are specified on the
java.library.path
using the wrapper.java.library.path.n properties. But if that JNI DLL
itself requires
other DLLs to be loaded then those other DLLs are located using the
system PATH.
I am not sure if this is your problem, but if so, try the following:
set.PATH=..%WRAPPER_FILE_SEPARATOR%lib%WRAPPER_PATH_SEPARATOR%%PATH%
wrapper.java.library.path.1=../lib
The above assumes that all of the DLLs are located in the ../lib
directory. The
long WRAPPER_* environment variables are created by the wrapper to make it
possible to make the setting platform independent. You can also just type:
set.PATH=../lib;%PATH%
Cheers,
Leif
Andrew Dickson wrote:
>I have a Java application which runs fine on 2003 Server (JRE 1.4.2_04).
>However, when I use the Java Service Wrapper
>(http://wrapper.tanukisoftware.org/doc/english/introduction.html) to run the
>application as a service, I get a linking error. The error is definately within
>my application (nlsxbe.dll), and not the wrapper. The runtime path is exactly
>the same in both instances (set by wrapper.java.library.path and confirmed by
>java.library.path), and there is obviously no missing DLL, otherwise the
>application would not run at all. I do not have this problem on either NT or
>2000. What should I do to investigate this issue?
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Tell us your software development plans!
>Take this survey and enter to win a one-year sub to SourceForge.net
>Plus IDC's 2005 look-ahead and a copy of this survey
>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|