Re: [Wrapper-user] Wrapper classpath on Windows 2000

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

John,

Volkar, John wrote:
>> Just a thought here - what does your directory structure look 
>> like and where are you running it from?
>>     
> Good thought, thanks, but...
>   
The Wrapper is good about forcing the current directory to be the 
location of the
Wrapper.exe.   That will not be the case when you run the batch file I 
had you
create so you will want to run that from within the correct directory.
>> However, this wouldn't account for your Win2000 - 
>> WinXP difference, but...it might be worth looking into.
>>     
> Yeah, it's the same exact directory layout on the boxes.  
>
> I'm a bit hampered in testing/playing on this the only Win2000 box I
> have available to me is only  accessible to me via remote access, when
> the QA team isn't working on it.
>
> What's driving me nuts is that the invocation line works when all the
> -Dwrapper stuff is stripped and I invoke my main class directly, but
> thru the wrapper it doesn't...
>
> I'm wondering if my use of a static inner class for Start and Stop isn't
> the problem somehow...
>   
That is the only thing that I can think of as well...   The 
WrapperStartStopApp class
has code in the getMainMethod method which is attempting to load your
com.mckessonaps.fp2k.FP2KServiceWrapper$Start class manually.  That is
failing for some reason.

A couple more things for you to try:
1) Add the -verbose:class parameter to the batch file and see whether or 
not the
class is being loaded.

2) Change the main class from com.mckessonaps.fp2k.FP2KServiceWrapper$Start
to com.mckessonaps.fp2k.FP2KServiceWrapper and see what happens.  You will
still get an error that the main method can't be found, but that is 
after the class has
been successfully loaded.   Do this with the -verbose:class parameter 
set as well.

I can't think what could be causing this that would be OS specific, 
given that it
also happens with the batch file...  If it were a file permission 
problem then it
would also happen when the wrapper parameters were removed.

Have you installed any non-default security policy files in that JVM?  
There is
nothing specified from the command line, but it is possible to edit the 
security
files of the JVM itself.

I'll post again if I think of anything else.
Leif