|
From: Leif M. <le...@ta...> - 2008-07-30 01:49:13
|
Marcelo, There have been a lot of issues resolved with 3.3.0. Have you had a chance to try that version? * There were some shell script status problems in 3.2.3 when the full path to the location of the wrapper binary was long. That may be the problem you are encountering. * The error you are getting about not being able to load the JNI library is most likely because you are using a 32-bit version of the Wrapper with a 64-bit JVM. Cheers, Leif On Mon, Jul 28, 2008 at 9:51 PM, Datacom - Marcelo <ma...@da...> wrote: > Hi, we are having a problem sometimes when we start a service in Java > wrapper and verify with 'status' parameter it says the service is > stopped but in fact it is running (it was indeed started by java wrapper > but somehow java wrapper had lost contact with it). We cannot stop the > service (java wrapper think it is stopped and refuses to stop it). We > tried to kill the service but java wrapper restarts it. The only way we > can stop it is restarting the machine. > In fact we are using an amd 64 version of java wrapper in Solaris 10, > version is 3.2.3 and we are getting this error in every service we started: > > STATUS | wrapper | 2008/07/25 15:06:04 | --> Wrapper Started as Daemon > STATUS | wrapper | 2008/07/25 15:06:04 | Launching a JVM... > INFO | jvm 1 | 2008/07/25 15:06:05 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 1 | 2008/07/25 15:06:05 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 1 | 2008/07/25 15:06:05 | > INFO | jvm 1 | 2008/07/25 15:06:05 | > INFO | jvm 1 | 2008/07/25 15:06:05 | WARNING - Unable to load the > Wrapper's native library 'libwrapper.so'. > INFO | jvm 1 | 2008/07/25 15:06:05 | The file is located > on the path at the following location but > INFO | jvm 1 | 2008/07/25 15:06:05 | could not be loaded: > INFO | jvm 1 | 2008/07/25 15:06:05 | /xxx/./libwrapper.so > INFO | jvm 1 | 2008/07/25 15:06:05 | Please verify that > the file is readable by the current user > INFO | jvm 1 | 2008/07/25 15:06:05 | and that the file > has not been corrupted in any way. > INFO | jvm 1 | 2008/07/25 15:06:05 | One common cause of > this problem is running a 32-bit version > INFO | jvm 1 | 2008/07/25 15:06:05 | of the Wrapper with > a 64-bit version of Java, or vica versa. > INFO | jvm 1 | 2008/07/25 15:06:05 | This is a 64-bit JVM. > INFO | jvm 1 | 2008/07/25 15:06:05 | Reported cause: > INFO | jvm 1 | 2008/07/25 15:06:05 | > /xxx/./libwrapper.so: ld.so.1: java: fatal: relocation error: > R_AMD64_PC32: file /xxx/./libwrapper.so: symbol main: value > 0x2802b5c0484 does not fit > INFO | jvm 1 | 2008/07/25 15:06:05 | System signals will > not be handled correctly. > > In most of the time this works well but when it goes crazy theres > nothing we can do to stop the service. We need to know if is there a way > to kill this service (preventing java wrapper to restart it) or if it is > related to this error above how can we fix it. We tried to compile from > source , download a pre-compiled version but the result is allways the same. > > Thanks in adavance. > > -- > MARCELO Ribeiro > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |