wrapper-user Mailing List for Java Service Wrapper (Page 69)

Brought to you by: maxime-tsl, mortenson, samanta-yoshida

wrapper-user — User issues for Wrapper. (Support questions, etc.)

You can subscribe to this list here.

2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (5)	Oct (13)	Nov (16)	Dec (29)
2003	Jan (38)	Feb (51)	Mar (51)	Apr (115)	May (82)	Jun (30)	Jul (50)	Aug (68)	Sep (57)	Oct (160)	Nov (80)	Dec (78)
2004	Jan (71)	Feb (75)	Mar (108)	Apr (87)	May (79)	Jun (70)	Jul (69)	Aug (39)	Sep (52)	Oct (47)	Nov (50)	Dec (32)
2005	Jan (22)	Feb (122)	Mar (46)	Apr (76)	May (31)	Jun (51)	Jul (61)	Aug (70)	Sep (37)	Oct (46)	Nov (57)	Dec (83)
2006	Jan (55)	Feb (81)	Mar (51)	Apr (67)	May (77)	Jun (43)	Jul (106)	Aug (64)	Sep (47)	Oct (64)	Nov (60)	Dec (12)
2007	Jan (50)	Feb (93)	Mar (49)	Apr (56)	May (40)	Jun (63)	Jul (40)	Aug (47)	Sep (54)	Oct (37)	Nov (54)	Dec (37)
2008	Jan (35)	Feb (39)	Mar (26)	Apr (14)	May (23)	Jun (51)	Jul (43)	Aug (26)	Sep (29)	Oct (31)	Nov (24)	Dec (16)
2009	Jan (21)	Feb (30)	Mar (74)	Apr (26)	May (26)	Jun (43)	Jul (23)	Aug (23)	Sep (15)	Oct (27)	Nov (37)	Dec (10)
2010	Jan (16)	Feb (28)	Mar (16)	Apr (45)	May (8)	Jun (68)	Jul (45)	Aug (44)	Sep (51)	Oct (7)	Nov (20)	Dec (21)
2011	Jan (14)	Feb (17)	Mar (7)	Apr (7)	May (48)	Jun (23)	Jul (5)	Aug (33)	Sep (22)	Oct (14)	Nov (14)	Dec (5)
2012	Jan	Feb (10)	Mar (12)	Apr (51)	May (10)	Jun (8)	Jul (14)	Aug (22)	Sep (9)	Oct (24)	Nov (14)	Dec (13)
2013	Jan (12)	Feb (4)	Mar (14)	Apr (19)	May (2)	Jun (5)	Jul (13)	Aug (10)	Sep (4)	Oct (11)	Nov (13)	Dec (2)
2014	Jan (3)	Feb (14)	Mar (5)	Apr (10)	May (10)	Jun (11)	Jul (10)	Aug (3)	Sep (13)	Oct (22)	Nov (14)	Dec (32)
2015	Jan (8)	Feb (2)	Mar (17)	Apr (1)	May (24)	Jun	Jul (4)	Aug	Sep (9)	Oct (9)	Nov (5)	Dec (2)
2016	Jan (8)	Feb (6)	Mar (6)	Apr (9)	May (3)	Jun (2)	Jul (7)	Aug (6)	Sep	Oct	Nov (1)	Dec (6)
2017	Jan (9)	Feb (8)	Mar (6)	Apr	May	Jun (3)	Jul (13)	Aug (10)	Sep (8)	Oct	Nov (6)	Dec
2018	Jan	Feb (5)	Mar (7)	Apr (2)	May	Jun	Jul (3)	Aug (2)	Sep (9)	Oct (1)	Nov (1)	Dec (1)
2019	Jan (9)	Feb	Mar	Apr (10)	May (3)	Jun	Jul (7)	Aug (1)	Sep	Oct (2)	Nov	Dec
2020	Jan (1)	Feb (1)	Mar (1)	Apr	May	Jun (3)	Jul	Aug	Sep	Oct	Nov (1)	Dec
2021	Jan (1)	Feb (2)	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec (3)
2022	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2023	Jan (3)	Feb	Mar (1)	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2024	Jan	Feb (1)	Mar	Apr	May (1)	Jun (1)	Jul (1)	Aug	Sep (1)	Oct	Nov (1)	Dec
2025	Jan	Feb	Mar	Apr (1)	May (1)	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec (1)
2026	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 67 68 69 70 71 .. 225 > >> (Page 69 of 225)

[Wrapper-user] Remote debug enhancement request

From: Hayes, P. <Pet...@fm...> - 2008-08-01 13:38:12

It would be very convenient if the list actions that are supported by
the script be augmented to include debug.  The configuration could then
support a new value called wrapper.debug.arguments which would be used
to launch the jvm in debug mode.  I think this would be pretty
straightforward to add and be much easier on the end user than having to
modify the configuration file to enable JVM debugging.

Thoughts?

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

[Wrapper-user] How to disable automatic restart with manual restart still possible?

From: Isenberg, H. <ise...@e-...> - 2008-07-31 13:45:57

Is it possible to disable the automatic restart on VM-crashes while letting the manual restart function via wrapper.on_exit.N enabled?

For Desktop applications the automatic restart might be a good thing, but it is not for backend server which require manual intervention after a crash of the Java-VM to prevent data corruption or inconsistency. At the same time, the manual restart is especially nice for server systems where the user has no access to the system console.

Re: [Wrapper-user] Command line arguments to wrapper script

From: Leif M. <le...@ta...> - 2008-07-30 17:04:12

Peter,
It is possible, but the default shell script will have to be modified.

Basically, you have to modify the command line to launch the Wrapper
process within the script.   Any Wrapper configuration property can be
specified from the command line so you would have modify that command
line to include the necessary wrapper.java.additional.n properties.
http://wrapper.tanukisoftware.org/doc/english/props-command-line.html
http://wrapper.tanukisoftware.org/doc/english/prop-java-additional-n.html

Granted this would be complicated if the number of possible command
line parameters is variable.  If you thought you could have up to 10
for example, you would have to give those 10 properties default values
like:
wrapper.java.additional.1=-Dfoo1=foo
wrapper.java.additional.2=-Dfoo2=foo
wrapper.java.additional.3=-Dfoo3=foo

I will try to think of a cleaner way of allowing this in a future version.

Cheers,
Leif

On Thu, Jul 31, 2008 at 1:53 AM, Hayes, Peter <Pet...@fm...> wrote:
> Is it possible to start a wrapper application specifying additional vm
> parameters and application arguments to the process on the command line?
>
> I'd like to do something like this :
>
> app -Dlog.level=DEBUG start -file path/to/file.txt
>
> The syntax would be :
>
> <script> [jvm argument]... (start|console) [argument]...
>
> Thanks,
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
>
> -------------------------------------------------------------------------
> 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
>

[Wrapper-user] Command line arguments to wrapper script

From: Hayes, P. <Pet...@fm...> - 2008-07-30 16:53:49

Is it possible to start a wrapper application specifying additional vm
parameters and application arguments to the process on the command line?

I'd like to do something like this :

app -Dlog.level=DEBUG start -file path/to/file.txt

The syntax would be :

<script> [jvm argument]... (start|console) [argument]...

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

[Wrapper-user] AUTO: Neeraja Kollu is out of the office. (returning 07/08/2008)

From: Neeraja K. <nee...@in...> - 2008-07-30 10:35:54

I am out of the office until 07/08/2008.

I am in a training,  available from 6AM to 9AM IST till 6th August 2008.


Note: This is an automated response to your message  "Re: [Wrapper-user]
Wrong DIST_ARCH value on Mandriva 2008" sent on 30/7/08 12:44:34.

This is the only notification you will receive while this person is away.

Re: [Wrapper-user] Wrong DIST_ARCH value on Mandriva 2008

From: papinade <pap...@gm...> - 2008-07-30 07:53:55

On Ubuntu 8.04 :
1) uname -a => Linux ubuntu64 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46
UTC 2008 x86_64 GNU/Linux
2) uname -p => unknown
3) uname -m => x86_64
4) uname -i => unknown
5) uname -o => GNU/Linux

On Mandriva 2008 :
1) uname -a => Linux localhost 2.6.24.4-desktop586-1mnb #1 SMP Thu Mar 27
14:20:33 CET 2008 i686 Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
GNU/Linux
2) uname -p => Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
3) uname -m => i686
4) uname -i => unknown
5) uname -o => GNU/Linux



Leif Mortenson-2 wrote:
> 
> What happens if you execute each of the following on your system?
> 
> 1) uname -a
> 2) uname -p
> Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> 3) uname -m
> 4) uname -i
> 5) uname -o
> 
> The script as is tries `uname -p`.  If it is not unknown then it tries
> `uname -m`.   If your `uname -m` returns a useful value then I may
> need to skip `uname -p` values containing spaces.
> 
> Cheers,
> Leif
> 

-- 
View this message in context: http://www.nabble.com/Wrong-DIST_ARCH-value-on-Mandriva-2008-tp18713173p18727853.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] Wrong DIST_ARCH value on Mandriva 2008

From: Leif M. <le...@ta...> - 2008-07-30 07:14:38

What happens if you execute each of the following on your system?

1) uname -a
2) uname -p
Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
3) uname -m
4) uname -i
5) uname -o

The script as is tries `uname -p`.  If it is not unknown then it tries
`uname -m`.   If your `uname -m` returns a useful value then I may
need to skip `uname -p` values containing spaces.

Cheers,
Leif

On Tue, Jul 29, 2008 at 11:16 PM, papinade <pap...@gm...> wrote:
>
> Hi,
>
> I have a issue with the var DIST_ARCH returning a value untreated in the
> script.sh
>
> OS : Linux Mandriva 2008 i586
>
> DIST_ARCH=`uname -p 2>/dev/null | tr [:upper:] [:lower:] | tr -d [:blank:]`
> returns : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
>
> This value does not match with no one 'if' or 'case' in the script. So, i
> have the following error :
> Unable to locate any of the following binaries:
> /toto/bin/./wrapper-linux-intel(r)core(tm)2duocpue6750@2.66ghz-32
> /toto/bin/./wrapper-linux-intel(r)core(tm)2duocpue6750@2.66ghz-64
> /toto/bin/./wrapper
>
> I tested with Ubuntu 8.04 and i have not this issue.
>
> Is a patch planned for this ?
> --
> View this message in context: http://www.nabble.com/Wrong-DIST_ARCH-value-on-Mandriva-2008-tp18713173p18713173.html
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> 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
>

Re: [Wrapper-user] Service lost in solaris AMD64

From: Leif M. <le...@ta...> - 2008-07-30 01:59:53

Marcelo,
Also in the mean time, if you kill -9 the Java process, the Wrapper
will think it crashed and will thus restart it.   If you kill the
Wrapper with a standard 'kill', then it will shut down cleanly and
shutdown the JVM normally.

If you have the ignore signals setting on however then the Wrapper
will ignore the SIGTERM signal.  The Wrapper should be monitoring the
existence of an anchor file however.  If you delete that then the
Wrapper should shutdown.

As a last result, if you "kill -9" the Wrapper process, the JVM will
left running.  The Java side of the Wrapper however has some code in
it to shut itself down after a default of 30 seconds if it ever loses
contact with the Wrapper.   You could also kill-9 the JVM as well
after the Wrapper to force it to shutdown immediately as well.

This is of course all work around ideas to avoid rebooting the system.
 3.3.0 should have fixed your original problem.   If not, let me know
3.3.1 is just around the corner.

Cheers,
Leif

On Wed, Jul 30, 2008 at 10:49 AM, Leif Mortenson
<le...@ta...> wrote:
> 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
>>
>

Re: [Wrapper-user] Service lost in solaris AMD64

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
>

[Wrapper-user] Wrapper 32 bits used on 64 bits platform

From: papinade <pap...@gm...> - 2008-07-29 14:28:43

Hi,

In the script.sh : 
# If a 32-bit wrapper binary exists then it will work on 32 or 64 bit
#  platforms, if the 64-bit binary exists then the distribution most
#  likely wants to use long names.  Otherwise, look for the default.


I don't understand why the 32-bit wrapper binary is used even if we are on a
64-bit platform with a wrapper 64-bit available (Precision : 32 and 64 bits
wrapper are available in my source code but 32 bits wrapper is always
used...).

I tested my application today on ubuntu 64 bits and an error occured due to
the use of 32 bit wrapper.
If i forced the use of 64 bits wrapped, it works...

Why there is not a test on 32/64 bits platform to use the appropriate
wrapper ?

Thanks.
-- 
View this message in context: http://www.nabble.com/Wrapper-32-bits-used-on-64-bits-platform-tp18713449p18713449.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

[Wrapper-user] Wrong DIST_ARCH value on Mandriva 2008

From: papinade <pap...@gm...> - 2008-07-29 14:16:49

Hi,

I have a issue with the var DIST_ARCH returning a value untreated in the
script.sh

OS : Linux Mandriva 2008 i586

DIST_ARCH=`uname -p 2>/dev/null | tr [:upper:] [:lower:] | tr -d [:blank:]`
returns : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz

This value does not match with no one 'if' or 'case' in the script. So, i
have the following error : 
Unable to locate any of the following binaries:
/toto/bin/./wrapper-linux-intel(r)core(tm)2duocpue6750@2.66ghz-32
/toto/bin/./wrapper-linux-intel(r)core(tm)2duocpue6750@2.66ghz-64
/toto/bin/./wrapper

I tested with Ubuntu 8.04 and i have not this issue.

Is a patch planned for this ?
-- 
View this message in context: http://www.nabble.com/Wrong-DIST_ARCH-value-on-Mandriva-2008-tp18713173p18713173.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

[Wrapper-user] Service lost in solaris AMD64

From: Datacom - M. <ma...@da...> - 2008-07-28 13:19:46

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

[Wrapper-user] Web Start Application + JSW

From: Erik D. <eri...@gm...> - 2008-07-25 07:02:15

Hello!
I'm trying to set up deployment for a couple of applications with Java
Webstart. Additionally, the system administrators want service scripts.
Searching the web I found this post
http://www.mail-archive.com/lop...@li.../msg00008.html

It refers to http://www.seajug.org/vqwiki/jsp/Wiki?JavaWebStartTips. but
that link seems to be dead. Can this recipe be found someplace else?

Or can someone give me some pointers as to how to set this up?

Thanks in advance. :)



-- 
Best regards,

Erik Drolshammer

Re: [Wrapper-user] Trouble connecting with Java app over RMI

From: Leif M. <le...@ta...> - 2008-07-25 01:52:48

Michael,
What is the problem that you are encountering?  As I recall, RMI
requires that a security manager be configured.   When running under
the Wrapper, the wrapper is in effect calling your application code so
it must be included in the security chain.  The following FAQ gives an
example of this.
http://wrapper.tanukisoftware.org/doc/english/faq.html#5

Cheers,
Leif

On Fri, Jul 25, 2008 at 10:38 AM, Michael McFarland
<mic...@ja...> wrote:
>
> We have a Java application that uses RMI to connect to our session façade EJBs (remote interfaces) running in our middle tier on JBoss.
>
> This works fine when we run JBoss on the server via the run.bat  script but does not work when we run as a service using Wrapper.
> Web pages work either way.
>
> Has anyone else seen this? Am I missing a "Java Additional Parameter" ?
>
>
> Michael McFarland
> Manager, The Applications Group, Computational Sciences The Jackson Laboratory 600 Main St.
> Bar Harbor, Maine 04609
> 207.288.6796
>

[Wrapper-user] automated response

From: Dittmar G. <gr...@if...> - 2008-07-25 01:41:08

Dittmar Gross ist wegen Urlaub bis 25-Jul-2008
nicht per eMail zu erreichen.

Bitte wenden Sie sich in dringenden Faellen an
Telefon +49 (69) 7680 50, Telefax +49 (69) 7680 5333
oder eMail fi...@if...

Dittmar Gross is not available via eMail until 
Jul-25-2008 because of vacation.

In urgent cases please contact us directly by
Telephone +49 (69) 7680 50, Fax +49 (69) 7680 5333
or eMail fi...@if...

----------------------------------------------------------------------------
i:FAO Group
Clemensstrasse 9, 60487 Frankfurt am Main, Germany Tel +49 (69) 7680-50,
Fax +49 (69) 7680-5100, eMail information at ifao.net, www.cytric.info 

i:FAO Group GmbH
Sitz in Frankfurt am Main
Eingetragen beim Amtsgericht Frankfurt am Main, HRB 73600
Geschaeftsfuehrer: Louis Arnitz, Karin Froese 

To view the disclaimer text, click here:
www.ifao.net/disclaimer

[Wrapper-user] Trouble connecting with Java app over RMI

From: Michael M. <mic...@ja...> - 2008-07-25 01:40:41

We have a Java application that uses RMI to connect to our session façade EJBs (remote interfaces) running in our middle tier on JBoss.

This works fine when we run JBoss on the server via the run.bat  script but does not work when we run as a service using Wrapper. 
Web pages work either way.

Has anyone else seen this? Am I missing a "Java Additional Parameter" ?


Michael McFarland
Manager, The Applications Group, Computational Sciences The Jackson Laboratory 600 Main St.
Bar Harbor, Maine 04609
207.288.6796

[Wrapper-user] JVM exited unexpectedly while stopping the application

From: Bob B. <bob...@gm...> - 2008-07-23 21:27:10

Trying out the Java Service Wrapper (e.g. 3.3.0 - Community Edition)  
and have been noticing a warning in the logs anytime I shut down the  
application (e.g. "JVM exited unexpectedly while stopping the  
application").

I did notice the comments about bug #945072 for a previous release  
(e.g. http://sourceforge.net/tracker/?func=detail&aid=945976&group_id=39428&atid=425187) 
, but I am not calling System.exit() (e.g. that I'm aware of) and this  
is just a test application (e.g. not doing much at this point, stops  
really quick).  I am using method #3 as an integration method.  Only  
thing I can think of that may be particular about my test application  
is that I am using an interrupt to stop the application (e.g. break  
out of a Selector loop).

Anyways, just wondering if I should worry about this or just ignore it  
and move on.  Thanks, Bob

----

The following log snippet comes from running under OSX.  Same thing  
happens under Windows XP, although the noted warning message happens  
at a latter time under XP (e.g. right before the "Wrapper Stopped"  
STATUS message).

.........
DEBUG  | wrapperp | 2008/07/23 15:04:35 | read a packet PING : ping
DEBUG  | wrapperp | 2008/07/23 15:04:39 | send a packet PING : ping
INFO   | jvm 1    | 2008/07/23 15:04:39 | WrapperManager Debug:  
Received a packet PING : ping
INFO   | jvm 1    | 2008/07/23 15:04:39 | WrapperManager Debug: Send a  
packet PING : ping
DEBUG  | wrapperp | 2008/07/23 15:04:39 | read a packet PING : ping
DEBUG  | wrapper  | 2008/07/23 15:04:43 | Signal trapped.  Details:
DEBUG  | wrapper  | 2008/07/23 15:04:43 |   signal number=15  
(SIGTERM), source="unknown"
STATUS | wrapper  | 2008/07/23 15:04:43 | TERM trapped.  Shutting down.
DEBUG  | wrapper  | 2008/07/23 15:04:43 | wrapperStopProcess(0) called.
DEBUG  | wrapper  | 2008/07/23 15:04:43 | Sending stop signal to JVM
DEBUG  | wrapperp | 2008/07/23 15:04:43 | send a packet STOP : NULL
DEBUG  | wrapper  | 2008/07/23 15:04:43 | Signal trapped.  Details:
DEBUG  | wrapper  | 2008/07/23 15:04:43 |   signal number=20  
(SIGCHLD), source="unknown"
DEBUG  | wrapper  | 2008/07/23 15:04:43 | Received SIGCHLD, checking  
JVM process status.
DEBUG  | wrapper  | 2008/07/23 15:04:43 | JVM process exited with a  
code of 0, leaving the wrapper exit code set to 0.
WARN   | wrapper  | 2008/07/23 15:04:43 | JVM exited unexpectedly  
while stopping the application.
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
Received a packet STOP :
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
Thread, Wrapper-Connection, handling the shutdown process.
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
calling listener.stop()
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
Waiting for WrapperListener.stop runner thread to complete.
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
WrapperListener.stop runner thread started.
INFO   | jvm 1    | 2008/07/23 15:04:43 | 2008-07-23 15:04:43,074  
68314 [WrapperListener_stop_runner] INFO   
com.rdb.servertest.ServerTest  - Stopping.........0
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug: Send a  
packet STOP_PENDING : 60000
INFO   | jvm 1    | 2008/07/23 15:04:43 | 2008-07-23 15:04:43,074  
68314 [Thread-1] INFO  com.rdb.servertest.ServerTest  - Selector woke  
up.........
INFO   | jvm 1    | 2008/07/23 15:04:43 | 2008-07-23 15:04:43,074  
68314 [Thread-1] INFO  com.rdb.servertest.ServerTest  - Shutting down.
INFO   | jvm 1    | 2008/07/23 15:04:43 | 2008-07-23 15:04:43,075  
68315 [WrapperListener_stop_runner] INFO   
com.rdb.servertest.ServerTest  - Stopped.........
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
WrapperListener.stop runner thread stopped.
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
returned from listener.stop() -> 0
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug:  
shutdownJVM(0) Thread:Wrapper-Connection
INFO   | jvm 1    | 2008/07/23 15:04:43 | WrapperManager Debug: Send a  
packet STOPPED : 0
STATUS | wrapper  | 2008/07/23 15:04:43 | <-- Wrapper Stopped

As far as my stop/start methods on my WrapperListener.

     public int stop( int exitCode )
     {
         ServerTest.getLogger().log( Level.INFO, "Stopping........." +  
exitCode );
         appThread.interrupt();
         WrapperManager.signalStopping( 60000 );

         try
         {
             appThread.join( 60000 );
         }
         catch (InterruptedException ex)
         {
             ServerTest.getLogger().log( Level.INFO, "FYI, interrupt  
caught." );
         }

         ServerTest.getLogger().log( Level.INFO, "Stopped........." );

         return exitCode;
     }

As far as what my application is doing at the time of shutting down  
(again, not much).

     public void doMain()
     {
        ... A bunch of initialization code ....

        while (!Thread.currentThread().isInterrupted())
         {
             try
             {
                 selector.select();
             }
             catch (IOException ioe)
             {
                 getLogger().log( Level.ERROR, "Exception caught in  
select statement", ioe );
                 break;
             }
             getLogger().log( Level.INFO, "Selector woke up........." );

	    ....Check what selector is ready and do something which is  
nothing at this point...

         }

         getLogger().log( Level.INFO, "Shutting down.");

     }