Re: [Wrapper-user] RMI client not able to connect.

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

Nash,
    Usually NoSuchMethod problems are caused by jar version problems...  
If a jar
couldn't be found then you would get a class not found exception.

    Assuming your wrapper configuration is correct then my first guess 
is that you are
not running the JVM that you think you are.  If the wrapper is finding 
an old JVM then
you could get such problems.

    Try setting the wrapper.debug=true property (or 
wrapper.java.command.loglevel=INFO
if your version is at least 3.1.2).   This will show you the exact 
command used to launch the
JVM.
    If your wrapper.java.command is simply "java", then the Wrapper will 
be locating the
JVM on the system path.   Windows always prepends the Windows and
Windows\system32 directories to that path when looking for files.

    I always do this to avoid these problems:
wrapper.java.command=%JAVA_HOME%/bin/java
    That way I know exactly what is being run no matter where the 
application gets
installed.

    If that is not the problem then I would need to see the debug 
output, wrapper.conf file
and more information on the error you are seeing.

Cheers,
Leif

Nash Maruvada wrote:

>Hello,
>
>I have a rmi client server stup and it runs fine with I start up in
>the batch mode. It also starts my rmi registry when i start with JSW
>but when the client talks to the server the request goes to server i
>get an error saying NoSuchMethod exception. I was using gervany on the
>previous systems but its failing to startup on a windows 2003 system
>the service throws an error. Thats the reason i swithched to JSW and 
>was impressed with the amount of customization you can do with JSW.
>
>Thanks any Help is greatly appricated.
>Nash
>  
>