Re: [Wrapper-user] long classpath gives strange behavior??

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

Brian,
The problem is that when you are running with the batch file, a specific 
library path is
most likely not being defined. In such cases, Java defaults to using the 
value of the
PATH environment variable for the library path.

In the case of the Wrapper, a library path is usually specified to help 
the wrapper's
java component locate the wrapper.dll.

You can solve this is one of two ways.

1) The best way is to locate the dlls that are required and make sure 
that they are
located on the library path by adding appropriate entries:
http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-n.html

2) It is also possible to tell to the wrapper to add the full PATH to 
the library
path. This will give you back the default behavior.
http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html

I suggest using 1) as this will work cleanly on all systems. 2) has the 
problem that
you may accidentally find the incorrect dll if other applications are 
also adding dlls or
modifying the PATH.

Cheers,
Leif

Pieslak, Brian wrote:
>
> Hi,
>
> I am attempting to run a java product, openwfe (http://www.openwfe.org 
> <http://www.openwfe.org/>) on Windows 2000 Server, and I am having 
> trouble using the Java Service Wrapper.
>
> A colleague and I have found that the product has a very long 
> classpath, and that we are currently running the application from “C:\ab\”
>
> If I run the application using the batch files that ship with the 
> product, it works great.
>
> If I install the services using Java Wrapper, and I launch the 
> services, I see the following behavior:
>
> 1.) the services will start
>
> 2.) I can login to the product
>
> 3.) When I try to do anything within the product, I consistently 
> receive “LibraryNotFound” Exceptions
>
> I observed the same behavior when I ran the application from 
> “C:\abcdefg\”, and so I /believe/ that it has something to do with the 
> length of the file path and the java classpath.
>
> Can anyone provide any insight into the Java Wrapper on how to get 
> past this?
>
> Thanks!
>
> Brian
>