Re: [Wrapper-user] Error occured when JNI code is executed

[Leif M. <le...@ta...>]

Yasir,

> I downloaded Java Service Wrapper today and now trying to run my 
> application using method 1 on windows 2000. My application interact 
> with some of NT native functionality using JNI. Now problem is that 
> when I start my application on clicking on the MyApp.bat file my 
> application starts executing and execution fails when it tries to 
> load a DLL with following exception (please note that I have 
> not installed the service yet for my application)
>  
> jvm 1    | System tray DLL error
> jvm 1    | System tray ICON error
> jvm 1    | java.lang.UnsatisfiedLinkError: nativeMoveToFront
> jvm 1    |      at 
> com.gc.systray.SystemTrayIconManager.nativeMoveToFront(Native Method)
> jvm 1    |      at 
> com.gc.systray.SystemTrayIconManager.<init>(SystemTrayIconManager.java:69)
> jvm 1    |      at 
> com.gc.systray.DefaultSystemTray.<init>(DefaultSystemTray.java:48)
> jvm 1    |      at ASC_SplashScreen$2.run(ASC_SplashScreen.java:98)
> jvm 1    |      at java.lang.Thread.run(Unknown Source)
>  
> Any ideas why JNI is not working properly?

When your application was running without theWrapper, it was using a 
native library.
Java locates its native libraries using a special library path.   This 
was either specified
on the command line or as an environment variable.  When you locate it, 
you will
need to add an additional line to the wrapper.conf file to tell the 
wrapper where to
locate the additional native libraries.  It will look something like this:
wrapper.java.library.path.1=../lib
wrapper.java.library.path.2=c:/AdditionalJNILibraries/lib  

> Also I want to know that as my application is running under a 
> wrapper, performance of my application will be affected, what u people 
> say about performance issue?

I have never noticed any performance differences when using the 
Wrapper.  It is
designed to be very light weight.  The exception is when you dump very large
quantities of output to the console.   Then there is a slight 
performance decrease
but it is small and can be worked around in a number of ways using java 
site logging
tools.

Cheers,
Leif