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

Re: [Wrapper-user] Wrapper start problems on Linux

[Lars S. <Lar...@if...>]

Hi Leif
I was a bit fast. It works fine on Windows XP (32-bit) and Red Hat 5 
(64-bit) but on Ubuntu 9.10 (32-bit) it kills the JVM after the 30 
seconds. I have no idea why it works on Red Hat and Windows XP.
I will try you suggestion on Ubuntu.

Lars

Leif Mortenson wrote:
> Lars,
> If the WrapperManager is not initialized, then the Wrapper will kill
> the JVM by default after 30 seconds or so.  Have you disabled any of
> the default timeouts?  If so, all of the freeze detection code will
> not be working.
>
> Have you tried using Integration method #1?  It lets you do codeless
> integration.  If your special.start.class is designed to run as a
> normal standalone Java main class then following will work:
>
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.app.parameter.1=special.start.class
> wrapper.app.parameter.2=-"parameter to special start class"
> wrapper.app.parameter.3=myStartClass
>
> See the following documentation for more details:
> http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html
>
> Cheers,
> Leif
>
> On Fri, Nov 6, 2009 at 11:37 PM, Lars Schnoor <Lar...@if...> wrote:
>   
>> Hi Leif
>> Thanks for the quick reply. I changed the wrapper parameters like you
>> suggested and now it works.
>> The special.start.class does not implement WrapperListener or initialize the
>> WrapperManager, but it works anyway.
>> I did not make the special.start.class myself, so I can't make implement the
>> WrapperListener.
>>
>> Lars
>>
>> Leif Mortenson wrote:
>>
>> Lars,
>> All versions of the Wrapper actually expect that you correctly break
>> the parameters into individual parameters.  On Windows they are all
>> reconstructed into a single line so it works, but on UNIX, the command
>> is broken up into the individual components and passed to the system
>> as an array.
>>
>> You need to do the following and it will work on all platforms:
>>
>> wrapper.java.mainclass=special.start.class
>> wrapper.app.parameter.1=-"parameter to special start class"
>> wrapper.app.parameter.1=myStartClass
>>
>> The class you specify for the wrapper.java.mainclass must implement
>> the WrapperListener and initialize the WrapperManager class directly
>> or indirectly.  You are using what we call Integration Method #3.
>> Please read over the following page and let me know if you have any
>> additional questions.
>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html
>>
>> Cheers,
>> Leif
>>
>>
>> On Fri, Nov 6, 2009 at 10:18 PM, Lars Schnoor <Lar...@if...> wrote:
>>
>>
>> Hi
>> I have a Java application that is started in a special way. I have a main
>> class in my application that implements the WrapperListener interface.
>> from the command prompt I can start my application with:
>> java -cp myApplication.jar special.start.class -"parameter to special start
>> class" myStartClass
>> I can start my application by the above line on both Windows and Linux.
>>
>> On Windows I put the following line in my wrapper.conf:
>> wrapper.java.mainclass=special.start.class -"parameter to special start
>> class" myStartClass
>> And it works fine.
>>
>> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting the
>> same line in the wrapper.conf:
>> wrapper.java.mainclass=special.start.class -"parameter to special start
>> class" myStartClass
>> Here it does not work, I get an ClassNotFoundException for the class:
>> special.start.class -"parameter to special start class" myStartClass
>> For me it seems as if the wrapper on Linux sees special.start.class
>> -"parameter to special start class" myStartClass as one class, where the
>> wrapper on Windows starts the special.start.class with -"parameter to
>> special start class" myStartClass as parameters.
>> I tried putting:
>> wrapper.java.mainclass=special.start.class
>> wrapper.app.parameter.1=-"parameter to special start class" myStartClass
>> in the wrapper.conf and with this the wrapper starts, but since the
>> special.start.class does not implement the WrapperListener interface, the
>> wrapper shuts down after five tries.
>> Any idea how I can get it to work on Linux, I am using version 3.2.3 of the
>> wrapper?
>> Thanks in advance!
>>
>> Lars
>>     
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] Wrapper start problems on Linux

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

Lars,
If the WrapperManager is not initialized, then the Wrapper will kill
the JVM by default after 30 seconds or so.  Have you disabled any of
the default timeouts?  If so, all of the freeze detection code will
not be working.

Have you tried using Integration method #1?  It lets you do codeless
integration.  If your special.start.class is designed to run as a
normal standalone Java main class then following will work:

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=special.start.class
wrapper.app.parameter.2=-"parameter to special start class"
wrapper.app.parameter.3=myStartClass

See the following documentation for more details:
http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html

Cheers,
Leif

On Fri, Nov 6, 2009 at 11:37 PM, Lars Schnoor <Lar...@if...> wrote:
> Hi Leif
> Thanks for the quick reply. I changed the wrapper parameters like you
> suggested and now it works.
> The special.start.class does not implement WrapperListener or initialize the
> WrapperManager, but it works anyway.
> I did not make the special.start.class myself, so I can't make implement the
> WrapperListener.
>
> Lars
>
> Leif Mortenson wrote:
>
> Lars,
> All versions of the Wrapper actually expect that you correctly break
> the parameters into individual parameters.  On Windows they are all
> reconstructed into a single line so it works, but on UNIX, the command
> is broken up into the individual components and passed to the system
> as an array.
>
> You need to do the following and it will work on all platforms:
>
> wrapper.java.mainclass=special.start.class
> wrapper.app.parameter.1=-"parameter to special start class"
> wrapper.app.parameter.1=myStartClass
>
> The class you specify for the wrapper.java.mainclass must implement
> the WrapperListener and initialize the WrapperManager class directly
> or indirectly.  You are using what we call Integration Method #3.
> Please read over the following page and let me know if you have any
> additional questions.
> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html
>
> Cheers,
> Leif
>
>
> On Fri, Nov 6, 2009 at 10:18 PM, Lars Schnoor <Lar...@if...> wrote:
>
>
> Hi
> I have a Java application that is started in a special way. I have a main
> class in my application that implements the WrapperListener interface.
> from the command prompt I can start my application with:
> java -cp myApplication.jar special.start.class -"parameter to special start
> class" myStartClass
> I can start my application by the above line on both Windows and Linux.
>
> On Windows I put the following line in my wrapper.conf:
> wrapper.java.mainclass=special.start.class -"parameter to special start
> class" myStartClass
> And it works fine.
>
> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting the
> same line in the wrapper.conf:
> wrapper.java.mainclass=special.start.class -"parameter to special start
> class" myStartClass
> Here it does not work, I get an ClassNotFoundException for the class:
> special.start.class -"parameter to special start class" myStartClass
> For me it seems as if the wrapper on Linux sees special.start.class
> -"parameter to special start class" myStartClass as one class, where the
> wrapper on Windows starts the special.start.class with -"parameter to
> special start class" myStartClass as parameters.
> I tried putting:
> wrapper.java.mainclass=special.start.class
> wrapper.app.parameter.1=-"parameter to special start class" myStartClass
> in the wrapper.conf and with this the wrapper starts, but since the
> special.start.class does not implement the WrapperListener interface, the
> wrapper shuts down after five tries.
> Any idea how I can get it to work on Linux, I am using version 3.2.3 of the
> wrapper?
> Thanks in advance!
>
> Lars

[Wrapper-user] Auto-updating JREs corrupting themselves

[<Jas...@sc...>]

Hi,

This isn't solely related to wrapper processes, but I've had a lot of 
hassle with Sun's auto-updating mechanism trashing the installed JRE on 
Windows.

You end up with:

C:\>java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object

It seems to be the fact that I am using the Invocation API 
(http://java.sun.com/j2se/1.4.2/docs/guide/jni/spec/invocation.html), 
mostly so that users see "MyProgram.exe"  rather than "java.exe" in the 
task manager. The wrapper calls my executable which parses all arguments 
similarly to java.exe but creates its own VM. Unfortunately the installer 
doesn't notice that my program is running and merrily installs, trashing 
itself in the process.

Anyone else suffered similarly? Any known workarounds?

Jason Chown
Sony Computer Entertainment Europe Limited
http://eu.playstation.com


**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify pos...@sc...
This footnote also confirms that this email message has been checked for all known viruses.
Sony Computer Entertainment Europe Limited
Registered Office: 10 Great Marlborough Street, London W1F 7LP, United Kingdom
Registered in England: 3277793
**********************************************************************

Re: [Wrapper-user] Wrapper start problems on Linux

[Lars S. <Lar...@if...>]

Hi Leif
Thanks for the quick reply. I changed the wrapper parameters like you 
suggested and now it works.
The special.start.class does not implement WrapperListener or initialize 
the WrapperManager, but it works anyway.
I did not make the special.start.class myself, so I can't make implement 
the WrapperListener.

Lars

Leif Mortenson wrote:
> Lars,
> All versions of the Wrapper actually expect that you correctly break
> the parameters into individual parameters.  On Windows they are all
> reconstructed into a single line so it works, but on UNIX, the command
> is broken up into the individual components and passed to the system
> as an array.
>
> You need to do the following and it will work on all platforms:
>
> wrapper.java.mainclass=special.start.class
> wrapper.app.parameter.1=-"parameter to special start class"
> wrapper.app.parameter.1=myStartClass
>
> The class you specify for the wrapper.java.mainclass must implement
> the WrapperListener and initialize the WrapperManager class directly
> or indirectly.  You are using what we call Integration Method #3.
> Please read over the following page and let me know if you have any
> additional questions.
> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html
>
> Cheers,
> Leif
>
>
> On Fri, Nov 6, 2009 at 10:18 PM, Lars Schnoor <Lar...@if...> wrote:
>   
>> Hi
>> I have a Java application that is started in a special way. I have a main
>> class in my application that implements the WrapperListener interface.
>> from the command prompt I can start my application with:
>> java -cp myApplication.jar special.start.class -"parameter to special start
>> class" myStartClass
>> I can start my application by the above line on both Windows and Linux.
>>
>> On Windows I put the following line in my wrapper.conf:
>> wrapper.java.mainclass=special.start.class -"parameter to special start
>> class" myStartClass
>> And it works fine.
>>
>> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting the
>> same line in the wrapper.conf:
>> wrapper.java.mainclass=special.start.class -"parameter to special start
>> class" myStartClass
>> Here it does not work, I get an ClassNotFoundException for the class:
>> special.start.class -"parameter to special start class" myStartClass
>> For me it seems as if the wrapper on Linux sees special.start.class
>> -"parameter to special start class" myStartClass as one class, where the
>> wrapper on Windows starts the special.start.class with -"parameter to
>> special start class" myStartClass as parameters.
>> I tried putting:
>> wrapper.java.mainclass=special.start.class
>> wrapper.app.parameter.1=-"parameter to special start class" myStartClass
>> in the wrapper.conf and with this the wrapper starts, but since the
>> special.start.class does not implement the WrapperListener interface, the
>> wrapper shuts down after five tries.
>> Any idea how I can get it to work on Linux, I am using version 3.2.3 of the
>> wrapper?
>> Thanks in advance!
>>
>> Lars
>>     
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] Wrapper start problems on Linux

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

Lars,
All versions of the Wrapper actually expect that you correctly break
the parameters into individual parameters.  On Windows they are all
reconstructed into a single line so it works, but on UNIX, the command
is broken up into the individual components and passed to the system
as an array.

You need to do the following and it will work on all platforms:

wrapper.java.mainclass=special.start.class
wrapper.app.parameter.1=-"parameter to special start class"
wrapper.app.parameter.1=myStartClass

The class you specify for the wrapper.java.mainclass must implement
the WrapperListener and initialize the WrapperManager class directly
or indirectly.  You are using what we call Integration Method #3.
Please read over the following page and let me know if you have any
additional questions.
http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html

Cheers,
Leif


On Fri, Nov 6, 2009 at 10:18 PM, Lars Schnoor <Lar...@if...> wrote:
> Hi
> I have a Java application that is started in a special way. I have a main
> class in my application that implements the WrapperListener interface.
> from the command prompt I can start my application with:
> java -cp myApplication.jar special.start.class -"parameter to special start
> class" myStartClass
> I can start my application by the above line on both Windows and Linux.
>
> On Windows I put the following line in my wrapper.conf:
> wrapper.java.mainclass=special.start.class -"parameter to special start
> class" myStartClass
> And it works fine.
>
> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting the
> same line in the wrapper.conf:
> wrapper.java.mainclass=special.start.class -"parameter to special start
> class" myStartClass
> Here it does not work, I get an ClassNotFoundException for the class:
> special.start.class -"parameter to special start class" myStartClass
> For me it seems as if the wrapper on Linux sees special.start.class
> -"parameter to special start class" myStartClass as one class, where the
> wrapper on Windows starts the special.start.class with -"parameter to
> special start class" myStartClass as parameters.
> I tried putting:
> wrapper.java.mainclass=special.start.class
> wrapper.app.parameter.1=-"parameter to special start class" myStartClass
> in the wrapper.conf and with this the wrapper starts, but since the
> special.start.class does not implement the WrapperListener interface, the
> wrapper shuts down after five tries.
> Any idea how I can get it to work on Linux, I am using version 3.2.3 of the
> wrapper?
> Thanks in advance!
>
> Lars

Re: [Wrapper-user] Wrapper start problems on Linux

[Lars S. <Lar...@if...>]

One more thing, if I copy the command the wrapper gives to Java in a 
terminal window my application runs without problems, I mean the output 
I get from:
wrapper.java.command.loglevel=INFO

Lars

Lars Schnoor wrote:
> Hi
> I have a Java application that is started in a special way. I have a 
> main class in my application that implements the WrapperListener 
> interface.
> from the command prompt I can start my application with:
> java -cp /myApplication/.jar /special.start.class/ -/"parameter to 
> special start class"/ /myStartClass/
> I can start my application by the above line on both Windows and Linux.
>
> On Windows I put the following line in my wrapper.conf:
> *wrapper.java.mainclass=special.start.class -"parameter to special 
> start class" myStartClass*
> And it works fine.
>
> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting 
> the same line in the wrapper.conf:
> *wrapper.java.mainclass=special.start.class -"parameter to special 
> start class" myStartClass*
> Here it does not work, I get an ClassNotFoundException for the class: 
> *special.start.class -"parameter to special start class" myStartClass
> *For me it seems as if the wrapper on Linux sees *special.start.class 
> -"parameter to special start class" myStartClass* as one class, where 
> the wrapper on Windows starts the /special.start.class/ with 
> /-"parameter to special start class" myStartClass/ as parameters.
> I tried putting:
> *wrapper.java.mainclass=special.start.class
> wrapper.app.parameter.1=-"parameter to special start class" myStartClass*
> in the wrapper.conf and with this the wrapper starts, but since the 
> /special.start.class/ does not implement the WrapperListener 
> interface, the wrapper shuts down after five tries.
> Any idea how I can get it to work on Linux, I am using version 3.2.3 
> of the wrapper?
> Thanks in advance!
>
> Lars
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

[Wrapper-user] Wrapper start problems on Linux

[Lars S. <Lar...@if...>]

Hi
I have a Java application that is started in a special way. I have a 
main class in my application that implements the WrapperListener interface.
from the command prompt I can start my application with:
java -cp /myApplication/.jar /special.start.class/ -/"parameter to 
special start class"/ /myStartClass/
I can start my application by the above line on both Windows and Linux.

On Windows I put the following line in my wrapper.conf:
*wrapper.java.mainclass=special.start.class -"parameter to special start 
class" myStartClass*
And it works fine.

On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting 
the same line in the wrapper.conf:
*wrapper.java.mainclass=special.start.class -"parameter to special start 
class" myStartClass*
Here it does not work, I get an ClassNotFoundException for the class: 
*special.start.class -"parameter to special start class" myStartClass
*For me it seems as if the wrapper on Linux sees *special.start.class 
-"parameter to special start class" myStartClass* as one class, where 
the wrapper on Windows starts the /special.start.class/ with 
/-"parameter to special start class" myStartClass/ as parameters.
I tried putting:
*wrapper.java.mainclass=special.start.class
wrapper.app.parameter.1=-"parameter to special start class" myStartClass*
in the wrapper.conf and with this the wrapper starts, but since the 
/special.start.class/ does not implement the WrapperListener interface, 
the wrapper shuts down after five tries.
Any idea how I can get it to work on Linux, I am using version 3.2.3 of 
the wrapper?
Thanks in advance!

Lars

[Wrapper-user] Java Service Wrapper 3.3.7 Alert

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

Hello all,
It has come to our attention, that there is a fairly serious bug in
all UNIX platforms of 3.3.7.
The Wrapper works fine in console mode, but when started as a daemon
process, the
Wrapper becomes confused and writes the wrong PID into its pid file.

It will continue to run without problems, but you will not be able to
stop the Wrapper using
the shell scripts because the script sees the wrong PID and thinks
that the Wrapper is
already stopped.  You can stop the Wrapper by looking up its pid and
call 'kill {pid}' manually.

This was a bug added last week in 3.3.7.   3.3.6 works perfectly, and
we are very close to
a 3.3.8 release with the fix.

In the mean time, please use the 3.3.6 release found here:
http://wrapper.tanukisoftware.org/downloads

Please let me know if you have any questions about this problem.

Sincerely,
Leif Mortenson,
Tanuki Software, Ltd.

Re: [Wrapper-user] wrapper.ntservice.starttype

[Lars S. <Lar...@if...>]

Hi Leif

I am aware of the problems with Windows Vista and Windows 7 with regards 
to Windows Services and users/user levels, it is a real pain.

Lars

Leif Mortenson wrote:
> Lars,
> We will look into it.  One problem I see however is the fact that
> changing service configurations requires Administrator level
> privileges.  When the Wrapper is running as a service, it is running
> as the SYSTEM user which does not.
>
> In Windows Vista, 2008 and 7, this requires an Elevated Administrator
> account,  we have already been doing some research on how these
> accounts work for other purposes.  It may be necessary to actually run
> the service as an elevated user.
>
> Cheers,
> Leif
>
> On Wed, Nov 4, 2009 at 11:23 PM, Lars Schnoor <Lar...@if...> wrote:
>   
>> Hi Leif
>> You mean on Windows XP from Control Panel->Administrative Tools->Services?
>>
>> I have a control panel for my application that allows the user to set some
>> parameters and there I would like to allow the user to set whether the
>> service should start automatically on system startup or if he/she has to
>> start the service manually. When the user saves the settings I restart the
>> service using WrapperManager.restart(), so it would be nice if the change
>> would take affect at that point. I mean the service should restart, but if
>> the user afterwards restarts the computer the change should have taken
>> affect.
>>
>> I have no specific timing in mind, I just think it would be nice to be able
>> to do it. Since my control panel only comes up when the service is running
>> it would be sufficient to be able to do it while the service is running, but
>> being able to do it when the service is simply installed would probably not
>> hurt.
>>
>> Lars
>>
>> Leif Mortenson wrote:
>>
>> Lars,
>> Not currently, no.  You can do so from within the Service Control
>> Panel manually however.  Does that work for you?
>>
>> If not, what is the timing that you would like to see it changed?
>> While the service is running, or simply installed.
>>
>> Cheers,
>> Leif
>>
>> On Wed, Nov 4, 2009 at 8:44 PM, Lars Schnoor <Lar...@if...> wrote:
>>
>>
>> Hi
>> Is there a way to control the wrapper.ntservice.starttype parameter for
>> a service that is installed?
>> When I change the value for the wrapper.ntservice.starttype in
>> wrapper.conf it does not take affect before uninstalling the service and
>> then installing it again. I would like to be able to switch between
>> AUTO_START and DEMAND_START without reinstalling the service. I am using
>> version 3.2.3.
>> Thanks in advance!
>>
>> Lars
>>     
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] wrapper.ntservice.starttype

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

Lars,
We will look into it.  One problem I see however is the fact that
changing service configurations requires Administrator level
privileges.  When the Wrapper is running as a service, it is running
as the SYSTEM user which does not.

In Windows Vista, 2008 and 7, this requires an Elevated Administrator
account,  we have already been doing some research on how these
accounts work for other purposes.  It may be necessary to actually run
the service as an elevated user.

Cheers,
Leif

On Wed, Nov 4, 2009 at 11:23 PM, Lars Schnoor <Lar...@if...> wrote:
> Hi Leif
> You mean on Windows XP from Control Panel->Administrative Tools->Services?
>
> I have a control panel for my application that allows the user to set some
> parameters and there I would like to allow the user to set whether the
> service should start automatically on system startup or if he/she has to
> start the service manually. When the user saves the settings I restart the
> service using WrapperManager.restart(), so it would be nice if the change
> would take affect at that point. I mean the service should restart, but if
> the user afterwards restarts the computer the change should have taken
> affect.
>
> I have no specific timing in mind, I just think it would be nice to be able
> to do it. Since my control panel only comes up when the service is running
> it would be sufficient to be able to do it while the service is running, but
> being able to do it when the service is simply installed would probably not
> hurt.
>
> Lars
>
> Leif Mortenson wrote:
>
> Lars,
> Not currently, no.  You can do so from within the Service Control
> Panel manually however.  Does that work for you?
>
> If not, what is the timing that you would like to see it changed?
> While the service is running, or simply installed.
>
> Cheers,
> Leif
>
> On Wed, Nov 4, 2009 at 8:44 PM, Lars Schnoor <Lar...@if...> wrote:
>
>
> Hi
> Is there a way to control the wrapper.ntservice.starttype parameter for
> a service that is installed?
> When I change the value for the wrapper.ntservice.starttype in
> wrapper.conf it does not take affect before uninstalling the service and
> then installing it again. I would like to be able to switch between
> AUTO_START and DEMAND_START without reinstalling the service. I am using
> version 3.2.3.
> Thanks in advance!
>
> Lars

Re: [Wrapper-user] wrapper.ntservice.starttype

[Lars S. <Lar...@if...>]

Hi Leif
You mean on Windows XP from Control Panel->Administrative Tools->Services?

I have a control panel for my application that allows the user to set 
some parameters and there I would like to allow the user to set whether 
the service should start automatically on system startup or if he/she 
has to start the service manually. When the user saves the settings I 
restart the service using WrapperManager.restart(), so it would be nice 
if the change would take affect at that point. I mean the service should 
restart, but if the user afterwards restarts the computer the change 
should have taken affect.

I have no specific timing in mind, I just think it would be nice to be 
able to do it. Since my control panel only comes up when the service is 
running it would be sufficient to be able to do it while the service is 
running, but being able to do it when the service is simply installed 
would probably not hurt.

Lars

Leif Mortenson wrote:
> Lars,
> Not currently, no.  You can do so from within the Service Control
> Panel manually however.  Does that work for you?
>
> If not, what is the timing that you would like to see it changed?
> While the service is running, or simply installed.
>
> Cheers,
> Leif
>
> On Wed, Nov 4, 2009 at 8:44 PM, Lars Schnoor <Lar...@if...> wrote:
>   
>> Hi
>> Is there a way to control the wrapper.ntservice.starttype parameter for
>> a service that is installed?
>> When I change the value for the wrapper.ntservice.starttype in
>> wrapper.conf it does not take affect before uninstalling the service and
>> then installing it again. I would like to be able to switch between
>> AUTO_START and DEMAND_START without reinstalling the service. I am using
>> version 3.2.3.
>> Thanks in advance!
>>
>> Lars
>>     
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] wrapper.ntservice.starttype

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

Lars,
Not currently, no.  You can do so from within the Service Control
Panel manually however.  Does that work for you?

If not, what is the timing that you would like to see it changed?
While the service is running, or simply installed.

Cheers,
Leif

On Wed, Nov 4, 2009 at 8:44 PM, Lars Schnoor <Lar...@if...> wrote:
> Hi
> Is there a way to control the wrapper.ntservice.starttype parameter for
> a service that is installed?
> When I change the value for the wrapper.ntservice.starttype in
> wrapper.conf it does not take affect before uninstalling the service and
> then installing it again. I would like to be able to switch between
> AUTO_START and DEMAND_START without reinstalling the service. I am using
> version 3.2.3.
> Thanks in advance!
>
> Lars

[Wrapper-user] wrapper.ntservice.starttype

[Lars S. <Lar...@if...>]

Hi
Is there a way to control the wrapper.ntservice.starttype parameter for 
a service that is installed?
When I change the value for the wrapper.ntservice.starttype in 
wrapper.conf it does not take affect before uninstalling the service and 
then installing it again. I would like to be able to switch between 
AUTO_START and DEMAND_START without reinstalling the service. I am using 
version 3.2.3.
Thanks in advance!

Lars

Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

[JBrain S. <jbr...@ya...>]

Hi Leif,

Thank you for the update. That was a quick fix!

Regards,
JBrain

--- On Mon, 11/2/09, Leif Mortenson <lei...@ta...> wrote:

From: Leif Mortenson <lei...@ta...>
Subject: Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)
To: wra...@li...
Date: Monday, November 2, 2009, 9:59 AM

JBrain,
We got our PPC system back up and running and were able to reproduce the problem.   It is a bug that has existed since 3.3.1.  It was caused by an overflow error which has different behavior on PPC and x86 architectures..  The bug was actually in all Community edition platforms, but only appears to cause any problems on the MacOSX PPC platform.


This has been fixed and tested locally and will be in the 3.3.8 patch release we have scheduled for release this week.

Cheers,
Leif

On Sun, Nov 1, 2009 at 7:31 PM, JBrain Software <jbr...@ya...> wrote:


Hi Leif,

Thank you!! I'm now able to successfully launch the Java Service Wrapper on our Mac PPC based machine using the 3.2.3 version. Phew!

I hope this issue would be addressed in the forth coming releases ;)


Thank you again,
JBrain

--- On Sat, 10/31/09, Leif Mortenson <lei...@ta...> wrote:


From: Leif Mortenson <lei...@ta...>

Subject: Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)
To: wra...@li...

Date: Saturday, October 31, 2009, 5:01 PM

JBrain,
Our development and testing has been done on x86 systems for the past year.   The OSX binaries are built
 cross platform for PPC compatibility.   There have not been any other reports of problems with PPC systems however.


We do have a PPC Mac Mini that went haywire last year.  We will try and get it working again to do some testing this week.

In the mean time, have you tried any older versions of the Wrapper?  It might be helpful to know if it was working in an older version.  Old versions can be downloaded here:


http://wrapper.tanukisoftware.org/downloads

3.2.3 was the last version released with a true PPC binary:
http://wrapper.tanukisoftware.org/downloads/3.2.3/



I will post back as soon as we have more information.

Cheers,
Leif

On Fri, Oct 30, 2009 at 4:48 PM, JBrain Software <jbr...@ya...> wrote:




Hi all,

We are using the Java Service Wrapper for one of our applications.
Here are the brief details of the machines we are testing the wrapper application.

1. Mac OSX 10.5.8 (PowerPC G4 processor)
2. Mac OSX 10.5.8 (Core Duo Intel processor)


-  Java version on both the machines is 1.5.0_20

The wrapper works fine on the Core Duo processor machine but fails on the PowerPC processor machine with a segmentation fault. Unfortunately there is not much detailed information about the problem.


FYI, we are running the wrapper from a console.

Here is the log on the console:

Running ActivityLogger Application...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6


wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All
 Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
../ActivityLogger: line 492:  2652 Segmentation fault      "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper" "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf" wrapper.syslog.ident="ActivityLogger" wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid" wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger Application"





Here is the conf file of our wrapper for your perusal.

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************


# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug
#include
 ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

#********************************************************************
# Wrapper Java Properties
#********************************************************************


# Java Application
wrapper.java.command=java

# Tell the Wrapper to log the full generated Java command line.
#wrapper.java.command.loglevel=INFO
wrapper.java.command.loglevel=DEBUG

# Java Main class.  This class must implement the WrapperListener interface


#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp


wrapper.app.parameter.1=com.activitylogger.ActivityLogger

# Java Classpath (include wrapper.jar)  Add class
 path elements as
#  needed starting from 1
wrapper.java.classpath.1=../executables/lib/wrapper.jar
wrapper.java.classpath.2=../executables/ActivityLogger.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)


wrapper.java..library.path.1=../lib

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit mode.
#Âwrapper.java.additional.auto_bits=TRUE

# Java Additional Parameters
wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE


wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog



# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application
 parameters.  Add parameters as needed starting from 1
#wrapper.app.parameter.1=

#********************************************************************
# Wrapper Logging Properties
#********************************************************************


# Enables Debug output from the Wrapper.
  wrapper.debug=TRUE

# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)


wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM



# Log Level for log file output.  (See docs for log levels)
#wrapper.logfile.loglevel=INFO
wrapper.logfile.loglevel=DEBUG

# Maximum size that the log file will be allowed to grow to
 before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.


wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output.  (See docs for log levels)


wrapper.syslog.loglevel=NONE

wrapper.adviser=TRUE

#********************************************************************
# Wrapper General Properties
#********************************************************************


# Allow for the use of non-contiguous numbered properties
wrapper.ignore_sequence_gaps=TRUE

# Title to use when running as a console
wrapper.console.title=ActivityLogger Application
 (console mode)

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************


# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.



# Name of the service
wrapper.name=ActivityLogger

# Display name of the service
wrapper.displayname=ActivityLogger Application

# Description of the service


wrapper.description=Logs the system activity

# Service dependencies.  Add dependencies as needed starting from 1
#wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START


wrapper.ntservice.starttype=AUTO_START

#
 Allow the service to interact with the desktop.
wrapper.ntservice.interactive=true


We have also re-installed the OS to see if it fixes the problem, but it's still the same.
Having invested a huge amount of time in figuring out the issue and still not finding the solution,


we have decided to post a question in this forum.

May I ask if any one had this problem, and if yes what is the solution?

Many thanks,
JBrain




-----Inline Attachment Follows-----

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
-----Inline Attachment Follows-----

_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



      

Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

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

JBrain,
We got our PPC system back up and running and were able to reproduce the
problem.   It is a bug that has existed since 3.3.1.  It was caused by an
overflow error which has different behavior on PPC and x86 architectures.
The bug was actually in all Community edition platforms, but only appears to
cause any problems on the MacOSX PPC platform.

This has been fixed and tested locally and will be in the 3.3.8 patch
release we have scheduled for release this week.

Cheers,
Leif

On Sun, Nov 1, 2009 at 7:31 PM, JBrain Software <jbr...@ya...>wrote:

> Hi Leif,
>
> Thank you!! I'm now able to successfully launch the Java Service Wrapper on
> our Mac PPC based machine using the 3.2.3 version. Phew!
>
> I hope this issue would be addressed in the forth coming releases ;)
>
> Thank you again,
> JBrain
>
>
> --- On *Sat, 10/31/09, Leif Mortenson <lei...@ta...>*wrote:
>
>
> From: Leif Mortenson <lei...@ta...>
> Subject: Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC
> G4 processor)
> To: wra...@li...
> Date: Saturday, October 31, 2009, 5:01 PM
>
>
> JBrain,
> Our development and testing has been done on x86 systems for the past
> year.   The OSX binaries are built cross platform for PPC compatibility.
> There have not been any other reports of problems with PPC systems however.
>
> We do have a PPC Mac Mini that went haywire last year.  We will try and get
> it working again to do some testing this week.
>
> In the mean time, have you tried any older versions of the Wrapper?  It
> might be helpful to know if it was working in an older version.  Old
> versions can be downloaded here:
> http://wrapper.tanukisoftware.org/downloads
>
> 3.2.3 was the last version released with a true PPC binary:
> http://wrapper.tanukisoftware.org/downloads/3.2.3/
>
> I will post back as soon as we have more information.
>
> Cheers,
> Leif
>
> On Fri, Oct 30, 2009 at 4:48 PM, JBrain Software <jbr...@ya...<http://mc/compose?to=...@ya...>
> > wrote:
>
>> Hi all,
>>
>> We are using the Java Service Wrapper for one of our applications.
>> Here are the brief details of the machines we are testing the wrapper
>> application.
>>
>> 1. Mac OSX 10.5.8 (PowerPC G4 processor)
>> 2. Mac OSX 10.5.8 (Core Duo Intel processor)
>> -  Java version on both the machines is 1.5.0_20
>>
>> The wrapper works fine on the Core Duo processor machine but fails on the
>> PowerPC processor machine with a segmentation fault. Unfortunately there is
>> not much detailed information about the problem.
>> FYI, we are running the wrapper from a console.
>>
>> Here is the log on the console:
>>
>> Running ActivityLogger Application...
>> wrapper  | --> Wrapper Started as Console
>> wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6
>> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights
>> Reserved.
>> wrapper  |     http://wrapper.tanukisoftware.org
>> ./ActivityLogger: line 492:  2652 Segmentation fault
>> "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper"
>> "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf"
>> wrapper.syslog.ident="ActivityLogger"
>> wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid"
>> wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger
>> Application"
>>
>>
>>
>> Here is the conf file of our wrapper for your perusal.
>>
>> #********************************************************************
>> # Wrapper License Properties (Ignored by Community Edition)
>> #********************************************************************
>> # Include file problems can be debugged by removing the first '#'
>> #  from the following line:
>> ##include.debug
>> #include ../conf/wrapper-license.conf
>> #include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf
>>
>> #********************************************************************
>> # Wrapper Java Properties
>> #********************************************************************
>> # Java Application
>> wrapper.java.command=java
>>
>> # Tell the Wrapper to log the full generated Java command line.
>> #wrapper.java.command.loglevel=INFO
>> wrapper.java.command.loglevel=DEBUG
>>
>> # Java Main class.  This class must implement the WrapperListener
>> interface
>> #  or guarantee that the WrapperManager class is initialized.  Helper
>> #  classes are provided to do this for you.  See the Integration section
>> #  of the documentation for details.
>> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>> wrapper.app.parameter.1=com.activitylogger.ActivityLogger
>>
>> # Java Classpath (include wrapper.jar)  Add class path elements as
>> #  needed starting from 1
>> wrapper.java.classpath.1=../executables/lib/wrapper.jar
>> wrapper.java.classpath.2=../executables/ActivityLogger.jar
>>
>> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
>> wrapper.java..library.path.1=../lib
>>
>> # Java Bits.  On applicable platforms, tells the JVM to run in 32 or
>> 64-bit mode.
>> #Âwrapper.java.additional.auto_bits=TRUE
>>
>> # Java Additional Parameters
>>
>> wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE
>>
>> wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
>> wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
>>
>> wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog
>>
>> # Initial Java Heap Size (in MB)
>> #wrapper.java.initmemory=3
>>
>> # Maximum Java Heap Size (in MB)
>> #wrapper.java.maxmemory=64
>>
>> # Application parameters.  Add parameters as needed starting from 1
>> #wrapper.app.parameter.1=
>>
>> #********************************************************************
>> # Wrapper Logging Properties
>> #********************************************************************
>> # Enables Debug output from the Wrapper.
>>   wrapper.debug=TRUE
>>
>> # Format of output for the console.  (See docs for formats)
>> wrapper.console.format=PM
>>
>> # Log Level for console output.  (See docs for log levels)
>> wrapper.console.loglevel=INFO
>>
>> # Log file to use for wrapper output logging.
>> wrapper.logfile=../logs/wrapper.log
>>
>> # Format of output for the log file.  (See docs for formats)
>> wrapper.logfile.format=LPTM
>>
>> # Log Level for log file output.  (See docs for log levels)
>> #wrapper.logfile.loglevel=INFO
>> wrapper.logfile.loglevel=DEBUG
>>
>> # Maximum size that the log file will be allowed to grow to before
>> #  the log is rolled. Size is specified in bytes.  The default value
>> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
>> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
>> wrapper.logfile.maxsize=0
>>
>> # Maximum number of rolled log files which will be allowed before old
>> #  files are deleted.  The default value of 0 implies no limit.
>> wrapper.logfile.maxfiles=0
>>
>> # Log Level for sys/event log output.  (See docs for log levels)
>> wrapper.syslog.loglevel=NONE
>>
>> wrapper.adviser=TRUE
>>
>> #********************************************************************
>> # Wrapper General Properties
>> #********************************************************************
>> # Allow for the use of non-contiguous numbered properties
>> wrapper.ignore_sequence_gaps=TRUE
>>
>> # Title to use when running as a console
>> wrapper.console.title=ActivityLogger Application (console mode)
>>
>> #********************************************************************
>> # Wrapper Windows NT/2000/XP Service Properties
>> #********************************************************************
>> # WARNING - Do not modify any of these properties when an application
>> #  using this configuration file has been installed as a service.
>> #  Please uninstall the service before modifying this section.  The
>> #  service can then be reinstalled.
>>
>> # Name of the service
>> wrapper.name=ActivityLogger
>>
>> # Display name of the service
>> wrapper.displayname=ActivityLogger Application
>>
>> # Description of the service
>> wrapper.description=Logs the system activity
>>
>> # Service dependencies.  Add dependencies as needed starting from 1
>> #wrapper.ntservice.dependency.1=
>>
>> # Mode in which the service is installed.  AUTO_START or DEMAND_START
>> wrapper.ntservice.starttype=AUTO_START
>>
>> # Allow the service to interact with the desktop.
>> wrapper.ntservice.interactive=true
>>
>>
>> We have also re-installed the OS to see if it fixes the problem, but it's
>> still the same.
>> Having invested a huge amount of time in figuring out the issue and still
>> not finding the solution,
>> we have decided to post a question in this forum.
>>
>> May I ask if any one had this problem, and if yes what is the solution?
>>
>> Many thanks,
>> JBrain
>>
>>

Re: [Wrapper-user] Java Service Wrapper Port error

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

(I'll try posting this here as the SF email address of the original sender
bounces :-P.  It was a question work getting into the archives.)

Paul,
Glad to hear that you have been finding the Wrapper useful.

The "action server" is a simple telnet class which lets you control
the Wrapper using Telnet.  In the TestWrapper app, it will attempt to
bind to port 9999.  If it fails to bind however, the TestWrapper app
should continue to start up.  The Wrapper's port settings are for the
Wrapper itself and will not affect this 9999 port.

Most likely, another application on your system is making use of port
9999.  Are you seeing other problems with the TestWrapper?  Or just
that single message?

I would be happy to take a quick look at your wrapper.log file to
confirm things are working correctly.

About the "Windows NT" support, I will take a look at the
documentation and try to clarify it.    Windows XP, 2000, 2008, Vista,
7, etc are all "NT" versions of Windows.    Windows 95, 98, ME are all
"DOS" versions of Windows.  You are correct that this is not very
clear.   Just to make sure I make everything clear, which page(s) were
you reading that you found confusing?

Cheers,
Leif

On Mon, Nov 2, 2009 at 9:45 AM, Paul wrote:
>
> Message body follows:
>
> Leif,
> Thanks for a great application.
>
> I cannot however get the Test wrapper to run.
>
> I have set debug and given safe ports in the conf file but I still get the
> message:
>
> Unable to open the action server socket
>
> I am running it on XP and I see the message will only run on NT
> systems but am not sure if XP will accept NT services or not.
>
> If this is the problem, sorry if I am wasting you time. If not would
> appreciate your help.
>
> Regards
>
> Paul

Re: [Wrapper-user] Cannot launch service (using java service wrapper)

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

Uri,
See my notes in line below.

On Sun, Nov 1, 2009 at 4:50 PM, Uri Scheiner <ur...@no...> wrote:
> Unfortunately, there is nothing in the logs.
> However, when I am logged as the original Administrator and trying to
> launch the services via the command line (running the exact command as
> written in the service), I get the following error:
>
> Calling StartServiceCtrlDispatcher...please wait.
>
> StartServiceControlDispatcher failed!

Most likely you did this:  "wrapper.exe -s ..¥conf¥wrapper.conf"
Correct?  The "-s" command tells the Wrapper to launch as a service.
This should only be done by the ServiceManager when installed as a
service and will do exactly what you saw when run from the command
line.  This is normal as the -s command is not meant to be used by
users directly.

I'll add a little better error message to the output to avoid
confusion in the next release.  (3.3.8 is already in code freeze)

> When I am logged as an Administrator I created and running the exact
> command, I get this error:
>
> FATAL  | wrapper  | Unable to access registry to obtain environment
> variables -
> The operation completed successfully. (0x0)

This is an error attempting to access the registry to load the
environment variables and is not a problem I have seen in the past.
Looking at the code, I just noticed that I was not using the correct
API to obtain the error message text in this case so the cause is not
being made available.   I am working on getting this fixed for the
next release.

In the mean time, can you think of anything about your configuration
that might prefent your user from accessing the registry?

Cheers,
Leif

> -----Original Message-----
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: Thursday, October 29, 2009 8:06 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Cannot launch service (using java service
> wrapper)
>
> Uri,
> I have not played with the EC2 machines personally.   Could you please
> post your wrapper.log file?  Most likely it will include some
> information that will help be suggest a solution.
>
> Cheers,
> Leif
>
> On Thu, Oct 29, 2009 at 4:08 PM, Uri Scheiner <ur...@no...> wrote:
>>
>> Hi,
>>
>> I am using Java Service Wrapper and I have the following problem when
> using
>> it on Amazon EC2 machines.
>>
>> When I try to use an administrator user to launch the service, I get the
>> following error:
>>
>> wrapper  | Unable to start the service - The service did not respond to
> the
>> start or control request in a timely fashion. (0x41d)
>>
>> I only happens if I try to use a user that I create myself. However, if
> I
>> use the predefined 'Administrator' user (that comes with the machine),
> it
>> works fine.  I compared the parameters of the admin user I created and
> the
>> predefined one, and they look the same.
>>
>> Can you think what the problem may be? I tried it on several machines in
>> Amazon and got the same problem. When I am trying it on my own lab
> machines,
>> it doesn't happens.
>>
>>
>>
>> Thanks,
>>  Uri

Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

[JBrain S. <jbr...@ya...>]

Hi Leif,

Thank you!! I'm now able to successfully launch the Java Service Wrapper on our Mac PPC based machine using the 3.2.3 version. Phew!

I hope this issue would be addressed in the forth coming releases ;)

Thank you again,
JBrain

--- On Sat, 10/31/09, Leif Mortenson <lei...@ta...> wrote:

From: Leif Mortenson <lei...@ta...>
Subject: Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)
To: wra...@li...
Date: Saturday, October 31, 2009, 5:01 PM

JBrain,
Our development and testing has been done on x86 systems for the past year.   The OSX binaries are built cross platform for PPC compatibility.   There have not been any other reports of problems with PPC systems however.


We do have a PPC Mac Mini that went haywire last year.  We will try and get it working again to do some testing this week.

In the mean time, have you tried any older versions of the Wrapper?  It might be helpful to know if it was working in an older version.  Old versions can be downloaded here:

http://wrapper.tanukisoftware.org/downloads

3.2.3 was the last version released with a true PPC binary:
http://wrapper.tanukisoftware.org/downloads/3.2.3/


I will post back as soon as we have more information.

Cheers,
Leif

On Fri, Oct 30, 2009 at 4:48 PM, JBrain Software <jbr...@ya...> wrote:


Hi all,

We are using the Java Service Wrapper for one of our applications.
Here are the brief details of the machines we are testing the wrapper application.

1. Mac OSX 10.5.8 (PowerPC G4 processor)
2. Mac OSX 10.5.8 (Core Duo Intel processor)

-  Java version on both the machines is 1.5.0_20

The wrapper works fine on the Core Duo processor machine but fails on the PowerPC processor machine with a segmentation fault. Unfortunately there is not much detailed information about the problem.

FYI, we are running the wrapper from a console.

Here is the log on the console:

Running ActivityLogger Application...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6

wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All
 Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
../ActivityLogger: line 492:  2652 Segmentation fault      "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper" "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf" wrapper.syslog.ident="ActivityLogger" wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid" wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger Application"




Here is the conf file of our wrapper for your perusal.

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************

# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug
#include
 ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

#********************************************************************
# Wrapper Java Properties
#********************************************************************

# Java Application
wrapper.java.command=java

# Tell the Wrapper to log the full generated Java command line.
#wrapper.java.command.loglevel=INFO
wrapper.java.command.loglevel=DEBUG

# Java Main class.  This class must implement the WrapperListener interface

#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

wrapper.app.parameter.1=com.activitylogger.ActivityLogger

# Java Classpath (include wrapper.jar)  Add class
 path elements as
#  needed starting from 1
wrapper.java.classpath.1=../executables/lib/wrapper.jar
wrapper.java.classpath.2=../executables/ActivityLogger.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)

wrapper.java.library.path.1=../lib

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit mode.
#Âwrapper.java.additional.auto_bits=TRUE

# Java Additional Parameters
wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE

wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog


# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application
 parameters.  Add parameters as needed starting from 1
#wrapper.app.parameter.1=

#********************************************************************
# Wrapper Logging Properties
#********************************************************************

# Enables Debug output from the Wrapper.
  wrapper.debug=TRUE

# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)

wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM


# Log Level for log file output.  (See docs for log levels)
#wrapper.logfile.loglevel=INFO
wrapper.logfile.loglevel=DEBUG

# Maximum size that the log file will be allowed to grow to
 before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output.  (See docs for log levels)

wrapper.syslog.loglevel=NONE

wrapper.adviser=TRUE

#********************************************************************
# Wrapper General Properties
#********************************************************************

# Allow for the use of non-contiguous numbered properties
wrapper.ignore_sequence_gaps=TRUE

# Title to use when running as a console
wrapper.console.title=ActivityLogger Application
 (console mode)

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************

# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.


# Name of the service
wrapper.name=ActivityLogger

# Display name of the service
wrapper.displayname=ActivityLogger Application

# Description of the service

wrapper.description=Logs the system activity

# Service dependencies.  Add dependencies as needed starting from 1
#wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START

wrapper.ntservice.starttype=AUTO_START

#
 Allow the service to interact with the desktop.
wrapper.ntservice.interactive=true


We have also re-installed the OS to see if it fixes the problem, but it's still the same.
Having invested a huge amount of time in figuring out the issue and still not finding the solution,

we have decided to post a question in this forum.

May I ask if any one had this problem, and if yes what is the solution?

Many thanks,
JBrain




-----Inline Attachment Follows-----

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
-----Inline Attachment Follows-----

_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



      

Re: [Wrapper-user] Cannot launch service (using java service wrapper)

[Uri S. <ur...@no...>]

Hi Lief,

Unfortunately, there is nothing in the logs.
However, when I am logged as the original Administrator and trying to
launch the services via the command line (running the exact command as
written in the service), I get the following error:

Calling StartServiceCtrlDispatcher...please wait.

StartServiceControlDispatcher failed!


When I am logged as an Administrator I created and running the exact
command, I get this error:

FATAL  | wrapper  | Unable to access registry to obtain environment
variables -
The operation completed successfully. (0x0)


Hope it gives any clue..

Uri

-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...]
Sent: Thursday, October 29, 2009 8:06 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Cannot launch service (using java service
wrapper)

Uri,
I have not played with the EC2 machines personally.   Could you please
post your wrapper.log file?  Most likely it will include some
information that will help be suggest a solution.

Cheers,
Leif

On Thu, Oct 29, 2009 at 4:08 PM, Uri Scheiner <ur...@no...> wrote:
>
> Hi,
>
> I am using Java Service Wrapper and I have the following problem when
using
> it on Amazon EC2 machines.
>
> When I try to use an administrator user to launch the service, I get the
> following error:
>
> wrapper  | Unable to start the service - The service did not respond to
the
> start or control request in a timely fashion. (0x41d)
>
> I only happens if I try to use a user that I create myself. However, if
I
> use the predefined 'Administrator' user (that comes with the machine),
it
> works fine.  I compared the parameters of the admin user I created and
the
> predefined one, and they look the same.
>
> Can you think what the problem may be? I tried it on several machines in
> Amazon and got the same problem. When I am trying it on my own lab
machines,
> it doesn't happens.
>
>
>
> Thanks,
>  Uri

--------------------------------------------------------------------------
----
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

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

JBrain,
Our development and testing has been done on x86 systems for the past
year.   The OSX binaries are built cross platform for PPC compatibility.
There have not been any other reports of problems with PPC systems however.

We do have a PPC Mac Mini that went haywire last year.  We will try and get
it working again to do some testing this week.

In the mean time, have you tried any older versions of the Wrapper?  It
might be helpful to know if it was working in an older version.  Old
versions can be downloaded here:
http://wrapper.tanukisoftware.org/downloads

3.2.3 was the last version released with a true PPC binary:
http://wrapper.tanukisoftware.org/downloads/3.2.3/

I will post back as soon as we have more information.

Cheers,
Leif

On Fri, Oct 30, 2009 at 4:48 PM, JBrain Software
<jbr...@ya...>wrote:

> Hi all,
>
> We are using the Java Service Wrapper for one of our applications.
> Here are the brief details of the machines we are testing the wrapper
> application.
>
> 1. Mac OSX 10.5.8 (PowerPC G4 processor)
> 2. Mac OSX 10.5.8 (Core Duo Intel processor)
> -  Java version on both the machines is 1.5.0_20
>
> The wrapper works fine on the Core Duo processor machine but fails on the
> PowerPC processor machine with a segmentation fault. Unfortunately there is
> not much detailed information about the problem.
> FYI, we are running the wrapper from a console.
>
> Here is the log on the console:
>
> Running ActivityLogger Application...
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6
> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights
> Reserved.
> wrapper  |     http://wrapper.tanukisoftware.org
> ./ActivityLogger: line 492:  2652 Segmentation fault
> "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper"
> "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf"
> wrapper.syslog.ident="ActivityLogger"
> wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid"
> wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger
> Application"
>
>
>
> Here is the conf file of our wrapper for your perusal.
>
> #********************************************************************
> # Wrapper License Properties (Ignored by Community Edition)
> #********************************************************************
> # Include file problems can be debugged by removing the first '#'
> #  from the following line:
> ##include.debug
> #include ../conf/wrapper-license.conf
> #include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf
>
> #********************************************************************
> # Wrapper Java Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=java
>
> # Tell the Wrapper to log the full generated Java command line.
> #wrapper.java.command.loglevel=INFO
> wrapper.java.command.loglevel=DEBUG
>
> # Java Main class.  This class must implement the WrapperListener interface
> #  or guarantee that the WrapperManager class is initialized.  Helper
> #  classes are provided to do this for you.  See the Integration section
> #  of the documentation for details.
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.app.parameter.1=com.activitylogger.ActivityLogger
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../executables/lib/wrapper.jar
> wrapper.java.classpath.2=../executables/ActivityLogger.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../lib
>
> # Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit
> mode.
> #Âwrapper.java.additional.auto_bits=TRUE
>
> # Java Additional Parameters
>
> wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE
>
> wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
> wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
>
> wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters.  Add parameters as needed starting from 1
> #wrapper.app.parameter.1=
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Enables Debug output from the Wrapper.
>   wrapper.debug=TRUE
>
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=../logs/wrapper.log
>
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output.  (See docs for log levels)
> #wrapper.logfile.loglevel=INFO
> wrapper.logfile.loglevel=DEBUG
>
> # Maximum size that the log file will be allowed to grow to before
> #  the log is rolled. Size is specified in bytes.  The default value
> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0
>
> # Maximum number of rolled log files which will be allowed before old
> #  files are deleted.  The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0
>
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=NONE
>
> wrapper.adviser=TRUE
>
> #********************************************************************
> # Wrapper General Properties
> #********************************************************************
> # Allow for the use of non-contiguous numbered properties
> wrapper.ignore_sequence_gaps=TRUE
>
> # Title to use when running as a console
> wrapper.console.title=ActivityLogger Application (console mode)
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> #  using this configuration file has been installed as a service.
> #  Please uninstall the service before modifying this section.  The
> #  service can then be reinstalled.
>
> # Name of the service
> wrapper.name=ActivityLogger
>
> # Display name of the service
> wrapper.displayname=ActivityLogger Application
>
> # Description of the service
> wrapper.description=Logs the system activity
>
> # Service dependencies.  Add dependencies as needed starting from 1
> #wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=true
>
>
> We have also re-installed the OS to see if it fixes the problem, but it's
> still the same.
> Having invested a huge amount of time in figuring out the issue and still
> not finding the solution,
> we have decided to post a question in this forum.
>
> May I ask if any one had this problem, and if yes what is the solution?
>
> Many thanks,
> JBrain
>
>

Re: [Wrapper-user] pid file not working???

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

Dean,
This was a bug that was added in 3.3.7.  3.3.6 works perfectly and has
been a very stable release.

I will let you know as soon as 3.3.8 has been tested and is ready for release.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Fri, Oct 30, 2009 at 11:16 PM, Dean Hiller <de...@xs...> wrote:
> cool! and wow! that was quick.
>
> hmmm, I think I was using the wrapper script from 3.2 or something that my
> friend gave me but I was definitely using the wrapper binary from 3.3.7.  Is
> this bug in 3.3.6 or can I try out 3.3.6?
> thanks,
> Dean
>
> On Thu, Oct 29, 2009 at 11:11 PM, Leif Mortenson <le...@ta...>
> wrote:
>>
>> Dean,
>> We have been looking into this and it turns out that this is a bug
>> introduced in version 3.3.7.   We added a new WRAPPER_PID environment
>> variable that can be referenced in the wrapper.conf file for things
>> like log files, etc.   The problem is that the PID was being set
>> before the process was daemonized (forked).
>>
>> This is a bug if you call "wrapper.sh start".  It is working fine as
>> "wrapper.sh console".
>>
>> We view this as 3.3.7 being pretty much broken for UNIX platforms and
>> will be doing a 3.3.8 release with this fix within the next couple
>> days.
>>
>> Sorry for the trouble.
>>
>> Cheers,
>> Leif
>>
>> On Fri, Oct 30, 2009 at 12:50 AM, Leif Mortenson
>> <le...@ta...> wrote:
>> > Dean,
>> > The PID file should be getting written by the shell script that ships
>> > with the Wrapper.  Could you please confirm that you are using our
>> > script?  Most likely you are.
>> >
>> > 1) When you first start out, please confirm that no pid file, wrapper
>> > process, or java process are running.
>> > 2) run the script with the "console" command.   This should launch the
>> > Wrapper, and Java.
>> > 3) There should now be a PID file containing the Wrapper's PID.
>> > Please confirm the id in the PID file, and also print out a "ps
>> > -faux".
>> > 4) Does the PID in the file match that of the Wrapper?   If not,
>> > please send me your shell script and wrapper.conf file as attachments.
>> > Also please send me the name of your OS and version.  I should be able
>> > to find the problem from that.
>> >
>> >> Also, the 4017 command above seems odd
>> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is
>> >> supposed to only pass in the 2 start args and the 3 stop args I would
>> >> think
>> >> into the tomcat bootstrap process?
>> >
>> > This is actually working correctly.  The Wrapper is actually launching
>> > the WrapperStartStopApp class, not the Bootstrap class.  The
>> > WrapperStartStopApp class is responsible for running the startup and
>> > stop classes with their parameters at the appropriate times.  This
>> > looks like you have set it up correctly:
>> > org.tanukisoftware.wrapper.WrapperStartStopApp
>> > org.apache.catalina.startup.Bootstrap 1 start
>> > org.apache.catalina.startup.Bootstrap TRUE 1 stop
>> >
>> > Cheers,
>> > Leif
>> >
>> > On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <de...@xs...>
>> > wrote:
>> >> I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun.  when
>> >> I run
>> >> ./tomcat start  (tomcat was the wrappertest file)
>> >> my tomcat starts fine but then when running
>> >> ./tomcat status
>> >> it says the pid file is stale yet my wrapper and tomcat are running(and
>> >> if I
>> >> kill tomcat, the wrapper restarts it).  ie. my status and stop commands
>> >> completely don't work because of some pid problem.
>> >>
>> >> Here is data from my last run...
>> >>
>> >> pid file 4013
>> >>
>> >> Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no
>> >> 4013
>> >> exists...that must have been the shell file pid or something).
>> >>
>> >> root@builddragon:/opt/tomcat/
>> >> wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat
>> >> root      4015     1  0 22:18 ?        00:00:00
>> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper
>> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf
>> >> wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid
>> >> wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae
>> >> monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status
>> >> wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status
>> >> root      4017  4015  6 22:18 ?        00:00:29 /opt/jdk/bin/java
>> >> -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed
>> >> -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat
>> >> -Djava.io.tmpdir=/opt/tomcat/temp
>> >> -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib
>> >> -classpath
>> >> /opt/
>> >>
>> >> tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar
>> >> -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001
>> >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
>> >> -Dwrapper.pid=4013
>> >> -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s
>> >> ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
>> >> org.tanukisoftware.wrapper.WrapperStartStopApp
>> >> org.apache.catalina.startup.Bootstrap 1 start
>> >> org.apache.catalina.startup.Bootstrap TRUE 1 stop
>> >> root      4296 27756  0 22:26 pts/0    00:00:00 grep tomcat
>> >>
>> >> NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes
>> >> the
>> >> pid file which is wrong.  When I kill tomcat, wrapper still starts it
>> >> up
>> >> fine but the pid file is all wrong.  Also, the 4017 command above seems
>> >> odd
>> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is
>> >> supposed to only pass in the 2 start args and the 3 stop args I would
>> >> think
>> >> into the tomcat bootstrap process?
>> >>
>> >> anyone have any idea what is going on?
>> >> thanks,
>> >> Dean

Re: [Wrapper-user] pid file not working???

[Dean H. <de...@xs...>]

cool! and wow! that was quick.

hmmm, I think I was using the wrapper script from 3.2 or something that my
friend gave me but I was definitely using the wrapper binary from 3.3.7.  Is
this bug in 3.3.6 or can I try out 3.3.6?
thanks,
Dean

On Thu, Oct 29, 2009 at 11:11 PM, Leif Mortenson <le...@ta...>wrote:

> Dean,
> We have been looking into this and it turns out that this is a bug
> introduced in version 3.3.7.   We added a new WRAPPER_PID environment
> variable that can be referenced in the wrapper.conf file for things
> like log files, etc.   The problem is that the PID was being set
> before the process was daemonized (forked).
>
> This is a bug if you call "wrapper.sh start".  It is working fine as
> "wrapper.sh console".
>
> We view this as 3.3.7 being pretty much broken for UNIX platforms and
> will be doing a 3.3.8 release with this fix within the next couple
> days.
>
> Sorry for the trouble.
>
> Cheers,
> Leif
>
> On Fri, Oct 30, 2009 at 12:50 AM, Leif Mortenson
> <le...@ta...> wrote:
> > Dean,
> > The PID file should be getting written by the shell script that ships
> > with the Wrapper.  Could you please confirm that you are using our
> > script?  Most likely you are.
> >
> > 1) When you first start out, please confirm that no pid file, wrapper
> > process, or java process are running.
> > 2) run the script with the "console" command.   This should launch the
> > Wrapper, and Java.
> > 3) There should now be a PID file containing the Wrapper's PID.
> > Please confirm the id in the PID file, and also print out a "ps
> > -faux".
> > 4) Does the PID in the file match that of the Wrapper?   If not,
> > please send me your shell script and wrapper.conf file as attachments.
> > Also please send me the name of your OS and version.  I should be able
> > to find the problem from that.
> >
> >> Also, the 4017 command above seems odd
> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is
> >> supposed to only pass in the 2 start args and the 3 stop args I would
> think
> >> into the tomcat bootstrap process?
> >
> > This is actually working correctly.  The Wrapper is actually launching
> > the WrapperStartStopApp class, not the Bootstrap class.  The
> > WrapperStartStopApp class is responsible for running the startup and
> > stop classes with their parameters at the appropriate times.  This
> > looks like you have set it up correctly:
> > org.tanukisoftware.wrapper.WrapperStartStopApp
> > org.apache.catalina.startup.Bootstrap 1 start
> > org.apache.catalina.startup.Bootstrap TRUE 1 stop
> >
> > Cheers,
> > Leif
> >
> > On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <de...@xs...>
> wrote:
> >> I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun.  when I
> run
> >> ./tomcat start  (tomcat was the wrappertest file)
> >> my tomcat starts fine but then when running
> >> ./tomcat status
> >> it says the pid file is stale yet my wrapper and tomcat are running(and
> if I
> >> kill tomcat, the wrapper restarts it).  ie. my status and stop commands
> >> completely don't work because of some pid problem.
> >>
> >> Here is data from my last run...
> >>
> >> pid file 4013
> >>
> >> Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no
> 4013
> >> exists...that must have been the shell file pid or something).
> >>
> >> root@builddragon:/opt/tomcat/
> >> wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat
> >> root      4015     1  0 22:18 ?        00:00:00
> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper
> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf
> >> wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid
> >> wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae
> >> monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status
> >> wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status
> >> root      4017  4015  6 22:18 ?        00:00:29 /opt/jdk/bin/java
> >> -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed
> >> -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat
> >> -Djava.io.tmpdir=/opt/tomcat/temp
> >> -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib
> -classpath
> >> /opt/
> >>
> tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar
> >> -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001
> >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
> -Dwrapper.pid=4013
> >> -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s
> >> ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
> >> org.tanukisoftware.wrapper.WrapperStartStopApp
> >> org.apache.catalina.startup.Bootstrap 1 start
> >> org.apache.catalina.startup.Bootstrap TRUE 1 stop
> >> root      4296 27756  0 22:26 pts/0    00:00:00 grep tomcat
> >>
> >> NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes
> the
> >> pid file which is wrong.  When I kill tomcat, wrapper still starts it up
> >> fine but the pid file is all wrong.  Also, the 4017 command above seems
> odd
> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is
> >> supposed to only pass in the 2 start args and the 3 stop args I would
> think
> >> into the tomcat bootstrap process?
> >>
> >> anyone have any idea what is going on?
> >> thanks,
> >> Dean
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

[JBrain S. <jbr...@ya...>]

Hi all,

We are using the Java Service Wrapper for one of our applications.
Here are the brief details of the machines we are testing the wrapper application.

1. Mac OSX 10.5.8 (PowerPC G4 processor)
2. Mac OSX 10.5.8 (Core Duo Intel processor)
-  Java version on both the machines is 1.5.0_20

The wrapper works fine on the Core Duo processor machine but fails on the PowerPC processor machine with a segmentation fault. Unfortunately there is not much detailed information about the problem.
FYI, we are running the wrapper from a console.

Here is the log on the console:

Running ActivityLogger Application...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
./ActivityLogger: line 492:  2652 Segmentation fault      "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper" "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf" wrapper.syslog.ident="ActivityLogger" wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid" wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger Application"



Here is the conf file of our wrapper for your perusal.

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************
# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug
#include ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
wrapper.java.command=java

# Tell the Wrapper to log the full generated Java command line.
#wrapper.java.command.loglevel=INFO
wrapper.java.command.loglevel=DEBUG

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=com.activitylogger.ActivityLogger

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../executables/lib/wrapper.jar
wrapper.java.classpath.2=../executables/ActivityLogger.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit mode.
#Âwrapper.java.additional.auto_bits=TRUE

# Java Additional Parameters
wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE
wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog

# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application parameters.  Add parameters as needed starting from 1
#wrapper.app.parameter.1=

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Enables Debug output from the Wrapper.
  wrapper.debug=TRUE

# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)
#wrapper.logfile.loglevel=INFO
wrapper.logfile.loglevel=DEBUG

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=NONE

wrapper.adviser=TRUE

#********************************************************************
# Wrapper General Properties
#********************************************************************
# Allow for the use of non-contiguous numbered properties
wrapper.ignore_sequence_gaps=TRUE

# Title to use when running as a console
wrapper.console.title=ActivityLogger Application (console mode)

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.name=ActivityLogger

# Display name of the service
wrapper.displayname=ActivityLogger Application

# Description of the service
wrapper.description=Logs the system activity

# Service dependencies.  Add dependencies as needed starting from 1
#wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=true


We have also re-installed the OS to see if it fixes the problem, but it's still the same.
Having invested a huge amount of time in figuring out the issue and still not finding the solution,
we have decided to post a question in this forum.

May I ask if any one had this problem, and if yes what is the solution?

Many thanks,
JBrain



      

Re: [Wrapper-user] pid file not working???

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

Dean,
We have been looking into this and it turns out that this is a bug
introduced in version 3.3.7.   We added a new WRAPPER_PID environment
variable that can be referenced in the wrapper.conf file for things
like log files, etc.   The problem is that the PID was being set
before the process was daemonized (forked).

This is a bug if you call "wrapper.sh start".  It is working fine as
"wrapper.sh console".

We view this as 3.3.7 being pretty much broken for UNIX platforms and
will be doing a 3.3.8 release with this fix within the next couple
days.

Sorry for the trouble.

Cheers,
Leif

On Fri, Oct 30, 2009 at 12:50 AM, Leif Mortenson
<le...@ta...> wrote:
> Dean,
> The PID file should be getting written by the shell script that ships
> with the Wrapper.  Could you please confirm that you are using our
> script?  Most likely you are.
>
> 1) When you first start out, please confirm that no pid file, wrapper
> process, or java process are running.
> 2) run the script with the "console" command.   This should launch the
> Wrapper, and Java.
> 3) There should now be a PID file containing the Wrapper's PID.
> Please confirm the id in the PID file, and also print out a "ps
> -faux".
> 4) Does the PID in the file match that of the Wrapper?   If not,
> please send me your shell script and wrapper.conf file as attachments.
> Also please send me the name of your OS and version.  I should be able
> to find the problem from that.
>
>> Also, the 4017 command above seems odd
>> to me as it passes in all 7 arguments but the WrapperStartStopApp is
>> supposed to only pass in the 2 start args and the 3 stop args I would think
>> into the tomcat bootstrap process?
>
> This is actually working correctly.  The Wrapper is actually launching
> the WrapperStartStopApp class, not the Bootstrap class.  The
> WrapperStartStopApp class is responsible for running the startup and
> stop classes with their parameters at the appropriate times.  This
> looks like you have set it up correctly:
> org.tanukisoftware.wrapper.WrapperStartStopApp
> org.apache.catalina.startup.Bootstrap 1 start
> org.apache.catalina.startup.Bootstrap TRUE 1 stop
>
> Cheers,
> Leif
>
> On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <de...@xs...> wrote:
>> I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun.  when I run
>> ./tomcat start  (tomcat was the wrappertest file)
>> my tomcat starts fine but then when running
>> ./tomcat status
>> it says the pid file is stale yet my wrapper and tomcat are running(and if I
>> kill tomcat, the wrapper restarts it).  ie. my status and stop commands
>> completely don't work because of some pid problem.
>>
>> Here is data from my last run...
>>
>> pid file 4013
>>
>> Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no 4013
>> exists...that must have been the shell file pid or something).
>>
>> root@builddragon:/opt/tomcat/
>> wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat
>> root      4015     1  0 22:18 ?        00:00:00
>> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper
>> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf
>> wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid
>> wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae
>> monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status
>> wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status
>> root      4017  4015  6 22:18 ?        00:00:29 /opt/jdk/bin/java
>> -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed
>> -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat
>> -Djava.io.tmpdir=/opt/tomcat/temp
>> -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib -classpath
>> /opt/
>> tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar
>> -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001
>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=4013
>> -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s
>> ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
>> org.tanukisoftware.wrapper.WrapperStartStopApp
>> org.apache.catalina.startup.Bootstrap 1 start
>> org.apache.catalina.startup.Bootstrap TRUE 1 stop
>> root      4296 27756  0 22:26 pts/0    00:00:00 grep tomcat
>>
>> NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes the
>> pid file which is wrong.  When I kill tomcat, wrapper still starts it up
>> fine but the pid file is all wrong.  Also, the 4017 command above seems odd
>> to me as it passes in all 7 arguments but the WrapperStartStopApp is
>> supposed to only pass in the 2 start args and the 3 stop args I would think
>> into the tomcat bootstrap process?
>>
>> anyone have any idea what is going on?
>> thanks,
>> Dean

Re: [Wrapper-user] Cannot launch service (using java service wrapper)

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

Uri,
I have not played with the EC2 machines personally.   Could you please
post your wrapper.log file?  Most likely it will include some
information that will help be suggest a solution.

Cheers,
Leif

On Thu, Oct 29, 2009 at 4:08 PM, Uri Scheiner <ur...@no...> wrote:
>
> Hi,
>
> I am using Java Service Wrapper and I have the following problem when using
> it on Amazon EC2 machines.
>
> When I try to use an administrator user to launch the service, I get the
> following error:
>
> wrapper  | Unable to start the service - The service did not respond to the
> start or control request in a timely fashion. (0x41d)
>
> I only happens if I try to use a user that I create myself. However, if I
> use the predefined 'Administrator' user (that comes with the machine), it
> works fine.  I compared the parameters of the admin user I created and the
> predefined one, and they look the same.
>
> Can you think what the problem may be? I tried it on several machines in
> Amazon and got the same problem. When I am trying it on my own lab machines,
> it doesn't happens.
>
>
>
> Thanks,
>  Uri