Paul,
Sorry for the slow reply. I copied the Full Java commands out of your
good and
bad wrapper.logs and did a comparison. It looks like like it is working
for you when
running in a console, but failing when running as a service.
I as able to narrow the problem down to the library class path.
When running as a console it is:
-Djava.library.path="../lib;<clip>;C:\Program Files\Resource
Kit\;C:\PROGRA~1\Eicon\Eicon Shared\System;Z:.;Y:.;X:.;W:.;V:."
But when running as a service it is:
-Djava.library.path="../lib;<clip>;C:\Program Files\Resource Kit\"
The problem seems to be that final backslash. I am not sure exactly why
but it is
affecting Java's ability to parse the command line. If I change it to
-Djava.library.path="../lib;<clip>;C:\Program Files\Resource Kit\;" then
everything
works correctly.
I am going to need to do some investigating to figure out exactly why
this is
happening however. But this will be easy enough to work around within the
Wrapper. If the path ends in a \ then I add an extra ; I want to understand
exactly where this is causing problems. I would need a different fix if
it is also
going to be a problem for other system property definitions for example.
For now, can you try going in and modifying your PATH environment
variable so
it does not end in a \?
Cheers,
Leif
Paul Guilmette wrote:
>Here is a debug good and bad wrapper log and my wrapper.conf
>
>the lines look the same
>
>
|
