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

[Wrapper-user] Very Noisy Logs - "Previous control code"

[Wardell, M. <Mar...@co...>]

Hi
 
I am using community edition 3.5.3 on windows (32 bit) and I gets
"loads" of these in my logs. I have searched for this but haven't found
anyone else reporting the same issues.
 
WARN   | wrapper  | 2010/09/10 15:35:19 | Previous control code (4) was
still in queue, overwriting with (4).

Anyone else seen this and dealt with it?
 
Thanks
Mark


This e-mail is confidential and is intended only for the person to whom it is 
addressed.  It may be privileged and should not be read, copied or used by
anyone other than the intended recipient.  If you are not that person, you are
not permitted to make use of the information and you are requested to notify
the sender immediately that you have received it and then destroy the copy in
your possession without disclosing its contents to any person.

Commerzbank AG may monitor outgoing and incoming e-mails.  By replying to this
e-mail you consent to such monitoring.  We believe, but do not warrant, that 
this e-mail and any attachments are virus free, but you must take full 
responsibility for virus checking.

This e-mail was sent either by Commerzbank AG, London Branch, or by Commerzbank
Corporates & Markets, a division of Commerzbank AG.  Commerzbank AG is a 
company incorporated in the Federal Republic of Germany and registered in 
England (registered number FC008139, place of business 30 Gresham Street, 
London EC2V 7PG) and is authorised by Bundesanstalt fuer 
Finanzdienstleistungsaufsicht (BaFin) and authorised and subject to limited 
regulation by the Financial Services Authority (FSA).

Re: [Wrapper-user] Trouble with some paths

[Alberto E. <aes...@s2...>]

Finally we fixed it
We had to copy the librarys from jboss/lib/endorsed to
jboss/Server/default/lib and with that change, all our problems disappeared.
Thanks a lot for the help
Regards
  Alberto E.

 

-----Mensaje original-----
De: Alberto Esparza [mailto:aes...@s2...] 
Enviado el: viernes, 10 de septiembre de 2010 11:50
Para: wra...@li...
Asunto: Re: [Wrapper-user] Trouble with some paths

Hi Leif,

We've finally got it to work, but it throws an error in the Server.log file
about a class it can't find "org/apache/xpath/CachedXPathAPI"
If we launch the JBoss server with the run.bat script, it doesn't throw this
error.

Any clues?
  Thanks and regards
    Alberto E.

 
-----Mensaje original-----
De: Leif Mortenson [mailto:lei...@ta...] 
Enviado el: viernes, 10 de septiembre de 2010 10:15
Para: wra...@li...
Asunto: Re: [Wrapper-user] Trouble with some paths

Alberto,
What is the exact error message that you are seeing?

When I try running the Wrapper, this is the command line that gets
generated:
"C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java"
-server -Xms384m -Xmx768m -XX:PermSize=256m -XX:MaxPermSize=256m
-Dsession.serialization.jboss=true -Djava.library.path="C:\Prueba de
concepto\jboss\lib" -classpath "C:\Prueba de
concepto\jboss\lib\wrapper.jar;C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
;./run.jar"
-Dwrapper.key="V1wZT2BjQi0vCF0dwqsqZIRBikdiJAv4" -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.pid=2112 -Dwrapper.version="3.6.0-a-pro"
-Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
-Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper
-Dwrapper.lang.folder=../lang
org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main -c default
-b bit5-tests-1

This all appears to be correct.  The java exe, classpath, and library
paths are all quoted correctly.   I tested this with version 3.5.4.
Which version of the Wrapper are you using?

Cheers,
Leif

On Fri, Sep 10, 2010 at 12:14 AM, Alberto Esparza <aes...@s2...>
wrote:
> Hi Leif,
>
> Thanks for answering so fast, here is our wrapper.conf contents
>
> wrapper.java.command=C:\Archivos de
> programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.java.classpath.1=C:\Prueba de concepto\jboss\lib\wrapper.jar
> wrapper.java.classpath.2=C:\Archivos de
>
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
> wrapper.java.classpath.3=./run.jar
> wrapper.java.library.path.1=C:\Prueba de concepto\jboss\lib
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Xms384m
> wrapper.java.additional.3=-Xmx768m
> wrapper.java.additional.4=-XX:PermSize=256m
> wrapper.java.additional.5=-XX:MaxPermSize=256m
> wrapper.java.additional.6=-Dsession.serialization.jboss=true
> wrapper.app.parameter.1=org.jboss.Main
> wrapper.app.parameter.2=-c
> wrapper.app.parameter.3=default
> wrapper.app.parameter.4=-b
> wrapper.app.parameter.5=bit5-tests-1
> wrapper.logfile=C:\Prueba de concepto\jboss\server\default\log\wrapper.log
> wrapper.ntservice.name=S21Sec-WebApp
> wrapper.ntservice.displayname=S21sec Bitacora Web Application Server
> wrapper.ntservice.starttype=AUTO_START
>
> We are going to try the command you told us to see if we can get any more
> information.
>
> Thanks and regards,
>  Alberto E.
>
>
>
> -----Mensaje original-----
> De: Leif Mortenson [mailto:lei...@ta...]
> Enviado el: jueves, 09 de septiembre de 2010 17:07
> Para: wra...@li...
> Asunto: Re: [Wrapper-user] Trouble with some paths
>
> Alberto,
> Most likely there is a Quote problem someplace.
>
> Please send me your wrapper.conf.   You also might want to try setting
> the following property so you can see where in the command line it is
> getting messed up.
> wrapper.java.command.loglevel=INFO
>
> Cheers,
> Leif
>
> On Fri, Sep 10, 2010 at 12:00 AM, Alberto Esparza <aes...@s2...>
> wrote:
>> Hi everybody,
>>
>>
>>
>> We are installing a JBoss Server in a 64 bits Windows 2003 server and
>> depending on the path where the JBoss server is deployed, the wrapper
> works
>> fine or fails.
>>
>> If we leave the JBoss folder in C:\ it works just fine, but if we leave
it
>> in C:\Program files it fails.
>>
>> We’ve been trying with different paths and if the path has spaces in it,
> it
>> fails, if it doesn’t, it works.
>>
>> We’ve tried with both the 32 and 64 bit wrappers for Windows with the
same
>> results.
>>
>>
>>
>> Thanks in advance for the help
>>
>>   Alberto E.

----------------------------------------------------------------------------
--
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


----------------------------------------------------------------------------
--
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Wrapper loading

[Kapila_shantha <kde...@ho...>]

Hi All,

I'm using JSW for running my application as service on background. Every
things is now working. But I want to know is there any way to call some
method (Example init()) before loading wrapper modules.

Actually, I'm using HA clustering to make a backup server.

One node is ACTIVE and other one is PASSIVE

When my service down on ACTIVE server,  After three attempts my service
should be moved on the PASSIVE server.

But when I service down on ACTIVE server, It will yet detect the service is
running  then it will never move on to PASSIVE server.

Can you tell me how to call some method (to get result of my modules loading
is okey or not) before loading wrapper modules ?


Regards 
-- 
View this message in context: http://old.nabble.com/Wrapper-loading-tp29675482p29675482.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

[Wrapper-user] Wrapper loading

[kapilashantha r. <kap...@gm...>]

Hi All,

I'm using JSW for running my application as service on background. Every
things is now working. But I want to know is there any way to call some
method (Example init()) before loading wrapper modules.

Actually, I'm using HA clustering to make a backup server.

One node is ACTIVE and other one is PASSIVE

When my service down on ACTIVE server,  After three attempts my service
should be moved on the PASSIVE server.

But when I service down on ACTIVE server, It will yet detect the service is
running  then it will never move on to PASSIVE server.

Can you tell me how to call some method (to get result of my modules loading
is okey or not) before loading wrapper modules ?


Regards

Re: [Wrapper-user] Trouble with some paths

[Alberto E. <aes...@s2...>]

Hi Leif,

We've finally got it to work, but it throws an error in the Server.log file
about a class it can't find "org/apache/xpath/CachedXPathAPI"
If we launch the JBoss server with the run.bat script, it doesn't throw this
error.

Any clues?
  Thanks and regards
    Alberto E.

 
-----Mensaje original-----
De: Leif Mortenson [mailto:lei...@ta...] 
Enviado el: viernes, 10 de septiembre de 2010 10:15
Para: wra...@li...
Asunto: Re: [Wrapper-user] Trouble with some paths

Alberto,
What is the exact error message that you are seeing?

When I try running the Wrapper, this is the command line that gets
generated:
"C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java"
-server -Xms384m -Xmx768m -XX:PermSize=256m -XX:MaxPermSize=256m
-Dsession.serialization.jboss=true -Djava.library.path="C:\Prueba de
concepto\jboss\lib" -classpath "C:\Prueba de
concepto\jboss\lib\wrapper.jar;C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
;./run.jar"
-Dwrapper.key="V1wZT2BjQi0vCF0dwqsqZIRBikdiJAv4" -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.pid=2112 -Dwrapper.version="3.6.0-a-pro"
-Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
-Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper
-Dwrapper.lang.folder=../lang
org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main -c default
-b bit5-tests-1

This all appears to be correct.  The java exe, classpath, and library
paths are all quoted correctly.   I tested this with version 3.5.4.
Which version of the Wrapper are you using?

Cheers,
Leif

On Fri, Sep 10, 2010 at 12:14 AM, Alberto Esparza <aes...@s2...>
wrote:
> Hi Leif,
>
> Thanks for answering so fast, here is our wrapper.conf contents
>
> wrapper.java.command=C:\Archivos de
> programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.java.classpath.1=C:\Prueba de concepto\jboss\lib\wrapper.jar
> wrapper.java.classpath.2=C:\Archivos de
>
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
> wrapper.java.classpath.3=./run.jar
> wrapper.java.library.path.1=C:\Prueba de concepto\jboss\lib
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Xms384m
> wrapper.java.additional.3=-Xmx768m
> wrapper.java.additional.4=-XX:PermSize=256m
> wrapper.java.additional.5=-XX:MaxPermSize=256m
> wrapper.java.additional.6=-Dsession.serialization.jboss=true
> wrapper.app.parameter.1=org.jboss.Main
> wrapper.app.parameter.2=-c
> wrapper.app.parameter.3=default
> wrapper.app.parameter.4=-b
> wrapper.app.parameter.5=bit5-tests-1
> wrapper.logfile=C:\Prueba de concepto\jboss\server\default\log\wrapper.log
> wrapper.ntservice.name=S21Sec-WebApp
> wrapper.ntservice.displayname=S21sec Bitacora Web Application Server
> wrapper.ntservice.starttype=AUTO_START
>
> We are going to try the command you told us to see if we can get any more
> information.
>
> Thanks and regards,
>  Alberto E.
>
>
>
> -----Mensaje original-----
> De: Leif Mortenson [mailto:lei...@ta...]
> Enviado el: jueves, 09 de septiembre de 2010 17:07
> Para: wra...@li...
> Asunto: Re: [Wrapper-user] Trouble with some paths
>
> Alberto,
> Most likely there is a Quote problem someplace.
>
> Please send me your wrapper.conf.   You also might want to try setting
> the following property so you can see where in the command line it is
> getting messed up.
> wrapper.java.command.loglevel=INFO
>
> Cheers,
> Leif
>
> On Fri, Sep 10, 2010 at 12:00 AM, Alberto Esparza <aes...@s2...>
> wrote:
>> Hi everybody,
>>
>>
>>
>> We are installing a JBoss Server in a 64 bits Windows 2003 server and
>> depending on the path where the JBoss server is deployed, the wrapper
> works
>> fine or fails.
>>
>> If we leave the JBoss folder in C:\ it works just fine, but if we leave
it
>> in C:\Program files it fails.
>>
>> We’ve been trying with different paths and if the path has spaces in it,
> it
>> fails, if it doesn’t, it works.
>>
>> We’ve tried with both the 32 and 64 bit wrappers for Windows with the
same
>> results.
>>
>>
>>
>> Thanks in advance for the help
>>
>>   Alberto E.

----------------------------------------------------------------------------
--
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Trouble with some paths

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

Alberto,
What is the exact error message that you are seeing?

When I try running the Wrapper, this is the command line that gets generated:
"C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java"
-server -Xms384m -Xmx768m -XX:PermSize=256m -XX:MaxPermSize=256m
-Dsession.serialization.jboss=true -Djava.library.path="C:\Prueba de
concepto\jboss\lib" -classpath "C:\Prueba de
concepto\jboss\lib\wrapper.jar;C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar;./run.jar"
-Dwrapper.key="V1wZT2BjQi0vCF0dwqsqZIRBikdiJAv4" -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.pid=2112 -Dwrapper.version="3.6.0-a-pro"
-Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
-Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper
-Dwrapper.lang.folder=../lang
org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main -c default
-b bit5-tests-1

This all appears to be correct.  The java exe, classpath, and library
paths are all quoted correctly.   I tested this with version 3.5.4.
Which version of the Wrapper are you using?

Cheers,
Leif

On Fri, Sep 10, 2010 at 12:14 AM, Alberto Esparza <aes...@s2...> wrote:
> Hi Leif,
>
> Thanks for answering so fast, here is our wrapper.conf contents
>
> wrapper.java.command=C:\Archivos de
> programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.java.classpath.1=C:\Prueba de concepto\jboss\lib\wrapper.jar
> wrapper.java.classpath.2=C:\Archivos de
> programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
> wrapper.java.classpath.3=./run.jar
> wrapper.java.library.path.1=C:\Prueba de concepto\jboss\lib
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Xms384m
> wrapper.java.additional.3=-Xmx768m
> wrapper.java.additional.4=-XX:PermSize=256m
> wrapper.java.additional.5=-XX:MaxPermSize=256m
> wrapper.java.additional.6=-Dsession.serialization.jboss=true
> wrapper.app.parameter.1=org.jboss.Main
> wrapper.app.parameter.2=-c
> wrapper.app.parameter.3=default
> wrapper.app.parameter.4=-b
> wrapper.app.parameter.5=bit5-tests-1
> wrapper.logfile=C:\Prueba de concepto\jboss\server\default\log\wrapper.log
> wrapper.ntservice.name=S21Sec-WebApp
> wrapper.ntservice.displayname=S21sec Bitacora Web Application Server
> wrapper.ntservice.starttype=AUTO_START
>
> We are going to try the command you told us to see if we can get any more
> information.
>
> Thanks and regards,
>  Alberto E.
>
>
>
> -----Mensaje original-----
> De: Leif Mortenson [mailto:lei...@ta...]
> Enviado el: jueves, 09 de septiembre de 2010 17:07
> Para: wra...@li...
> Asunto: Re: [Wrapper-user] Trouble with some paths
>
> Alberto,
> Most likely there is a Quote problem someplace.
>
> Please send me your wrapper.conf.   You also might want to try setting
> the following property so you can see where in the command line it is
> getting messed up.
> wrapper.java.command.loglevel=INFO
>
> Cheers,
> Leif
>
> On Fri, Sep 10, 2010 at 12:00 AM, Alberto Esparza <aes...@s2...>
> wrote:
>> Hi everybody,
>>
>>
>>
>> We are installing a JBoss Server in a 64 bits Windows 2003 server and
>> depending on the path where the JBoss server is deployed, the wrapper
> works
>> fine or fails.
>>
>> If we leave the JBoss folder in C:\ it works just fine, but if we leave it
>> in C:\Program files it fails.
>>
>> We’ve been trying with different paths and if the path has spaces in it,
> it
>> fails, if it doesn’t, it works.
>>
>> We’ve tried with both the 32 and 64 bit wrappers for Windows with the same
>> results.
>>
>>
>>
>> Thanks in advance for the help
>>
>>   Alberto E.

Re: [Wrapper-user] Trouble with some paths

[Alberto E. <aes...@s2...>]

Hi Leif,

Thanks for answering so fast, here is our wrapper.conf contents

wrapper.java.command=C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=C:\Prueba de concepto\jboss\lib\wrapper.jar
wrapper.java.classpath.2=C:\Archivos de
programa\Bitacora\ConsolesAndReports\Java\jdk1.6.0_16\bin\java\lib\tools.jar
wrapper.java.classpath.3=./run.jar
wrapper.java.library.path.1=C:\Prueba de concepto\jboss\lib
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Xms384m
wrapper.java.additional.3=-Xmx768m
wrapper.java.additional.4=-XX:PermSize=256m
wrapper.java.additional.5=-XX:MaxPermSize=256m
wrapper.java.additional.6=-Dsession.serialization.jboss=true
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c 
wrapper.app.parameter.3=default
wrapper.app.parameter.4=-b
wrapper.app.parameter.5=bit5-tests-1
wrapper.logfile=C:\Prueba de concepto\jboss\server\default\log\wrapper.log
wrapper.ntservice.name=S21Sec-WebApp
wrapper.ntservice.displayname=S21sec Bitacora Web Application Server
wrapper.ntservice.starttype=AUTO_START

We are going to try the command you told us to see if we can get any more
information.

Thanks and regards,
  Alberto E.

 

-----Mensaje original-----
De: Leif Mortenson [mailto:lei...@ta...] 
Enviado el: jueves, 09 de septiembre de 2010 17:07
Para: wra...@li...
Asunto: Re: [Wrapper-user] Trouble with some paths

Alberto,
Most likely there is a Quote problem someplace.

Please send me your wrapper.conf.   You also might want to try setting
the following property so you can see where in the command line it is
getting messed up.
wrapper.java.command.loglevel=INFO

Cheers,
Leif

On Fri, Sep 10, 2010 at 12:00 AM, Alberto Esparza <aes...@s2...>
wrote:
> Hi everybody,
>
>
>
> We are installing a JBoss Server in a 64 bits Windows 2003 server and
> depending on the path where the JBoss server is deployed, the wrapper
works
> fine or fails.
>
> If we leave the JBoss folder in C:\ it works just fine, but if we leave it
> in C:\Program files it fails.
>
> We’ve been trying with different paths and if the path has spaces in it,
it
> fails, if it doesn’t, it works.
>
> We’ve tried with both the 32 and 64 bit wrappers for Windows with the same
> results.
>
>
>
> Thanks in advance for the help
>
>   Alberto E.

----------------------------------------------------------------------------
--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Trouble with some paths

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

Alberto,
Most likely there is a Quote problem someplace.

Please send me your wrapper.conf.   You also might want to try setting
the following property so you can see where in the command line it is
getting messed up.
wrapper.java.command.loglevel=INFO

Cheers,
Leif

On Fri, Sep 10, 2010 at 12:00 AM, Alberto Esparza <aes...@s2...> wrote:
> Hi everybody,
>
>
>
> We are installing a JBoss Server in a 64 bits Windows 2003 server and
> depending on the path where the JBoss server is deployed, the wrapper works
> fine or fails.
>
> If we leave the JBoss folder in C:\ it works just fine, but if we leave it
> in C:\Program files it fails.
>
> We’ve been trying with different paths and if the path has spaces in it, it
> fails, if it doesn’t, it works.
>
> We’ve tried with both the 32 and 64 bit wrappers for Windows with the same
> results.
>
>
>
> Thanks in advance for the help
>
>   Alberto E.

[Wrapper-user] Trouble with some paths

[Alberto E. <aes...@s2...>]

Hi everybody,

 

We are installing a JBoss Server in a 64 bits Windows 2003 server and
depending on the path where the JBoss server is deployed, the wrapper works
fine or fails.

If we leave the JBoss folder in C:\ it works just fine, but if we leave it
in C:\Program files it fails.

We've been trying with different paths and if the path has spaces in it, it
fails, if it doesn't, it works.

We've tried with both the 32 and 64 bit wrappers for Windows with the same
results.

 

Thanks in advance for the help

  Alberto E.

[Wrapper-user] Java Web Start

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

  Hi everyone

I would like to make a Windows Service and Linux Daemon to start and 
stop my application using Java Web Start. I planned of starting my 
application from the service with:

Process p = Runtime.getRuntime().exec("javaws http://...

in order to stop my application I planned of using:

p.destroy();

Is there any example code for such a service?

Lars

Re: [Wrapper-user] Need support

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

Kapila,
I did a search to double check, but this is the first mail we have
received from you.   It looks like you subscribed to the mailing list
21 hours ago.

Not sure what happened to your first message, but could you please
reply with your question and I would be happy to take a look at it.

Cheers,
Leif

On Tue, Sep 7, 2010 at 4:43 PM, Kapila Rajapaksha
<kde...@ho...> wrote:
> Dear Sir,
>
> I can't get reply from you for my problem (JSW). Still my issue in the
> pending status.
>
> Regards
> -Kapila
>

[Wrapper-user] Need support

[Kapila R. <kde...@ho...>]

Dear Sir,

I can't get reply from you for my problem (JSW). Still my issue in the pending status. 

Regards 
-Kapila
 		 	   		  

[Wrapper-user] Java Service Wrapper 3.5.4

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

Hi all,
I would like to announce the release of 3.5.4 of the Java Service
Wrapper.  This versions adds a new German language pack which
completely localizes the Wrapper in German.    We have also started on
the Web site, but it still has a ways to go before all of the pages
are localized.

This release also contains a few minor bug fixes.   Please see the
release notes for a full list of changes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html#3.5.4

Most platforms for the 3.5.4 were released on 8/25, however we had
some problems accessing our z/Linux build server which prevented us
from completing the release of the delta pack.   Sorry for the delay.
Those issues have been worked out and the complete 3.5.4 release is
now available on the Wrapper site:
http://wrapper.tanukisoftware.com/doc/english/download.jsp

As always, please let us know how we can continue to improve the
Wrapper to meet your needs.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.
http://www.tanukisoftware.com

Re: [Wrapper-user] Greed takes down the community version of Win x64

[Tasso A. <ta...@rb...>]

Boris you also have these alternatives:

http://stackoverflow.com/questions/68113/how-to-create-a-windows-service
-from-java-app


-----Original Message-----
From: Boris Hamanov [mailto:bs...@gm...] 
Sent: Wednesday, August 25, 2010 5:44 AM
To: wra...@li...
Subject: Re: [Wrapper-user] Greed takes down the community version of
Win x64

I don't agree that 64 bit JVM is only needed for pro applications.
Running 
32bit software on win64 involves emulation and that is overhead that
nobody 
needs.
I have small web site and lightweight server, but still run it on 64 bit
VM 
as this is the natural choice for my platform. Nowadays 64bit CPUs and
oses 
are commonplace.
Nothing expensive in it anymore. So, please, step into the future and
make 
this little gesture to the open source community. That one, as you said,
has 
always been great to you.
I suppose mostly in the means that it promotes you and contributes to
your 
software. And that means money. Do not think I eat grass.
I appreciate that you explained the situation though. You certainly have
a 
point, but think about what I said. I am sure many people think like me
and 
did you the courtesy of letting you know. You should not be frustrated,
but 
grateful.

--------------------------------------------------
From: "Leif Mortenson" <lei...@ta...>
Sent: Wednesday, August 25, 2010 12:11 PM
To: <wra...@li...>
Subject: Re: [Wrapper-user] Greed takes down the community version of
Win 
x64

> Boris,
> The 64-bit Windows version had never existed prior to version 3.3.0
> when we first released it in the Standard and Professional Edition.
> At the time, supporting the 64-bit Windows platform required the
> purchase of a new high end server specifically for that purpose along
> with a 64-bit copy of Windows XP, which at the time did not come
> cheap.  For this reason, and the ongoing need to support the
> development of the Wrapper, we have made the business decision to not
> make it available in the Community Edition for now.  This is also true
> for the z/Linux and z/OS platforms as they both have significant
> monthly server leasing charges we are covering.
>
> On Windows, you only need to use the 64-bit Windows version if you are
> running a 64-bit JVM.  It is possible to run the 32-bit Wrapper on a
> 64-bit Windows if you are also using a 32-bit JVM.  The 64-bit JVMs
> are mainly needed by very large applications which tend to be of a
> professional nature.  In these cases, yes, users would need to
> purchase a Standard Edition license.
>
> To be honest, comments like yours can be a bit frustrating.  Most
> companies never make anything available for free.  We have always made
> a great effort to generously support open source communities, both
> with the Wrapper and in other projects.  Yet when we decide to make
> small portion of our NEW features closed source to support the whole
> development, you call us greedy and complain.  I am glad that you were
> able to so easily find a solution which meets your needs and doesn't
> make you "angry".
>
> All well.  Regardless of whether or not you decide to make use of the
> Wrapper in your projects, we will continue to do our best to support
> the community which has always been great to us.
>
> I wish you the best in life.
> Cheers,
> Leif
>
> On Wed, Aug 25, 2010 at 5:02 PM, Boris Hamanov <bs...@gm...>
wrote:
>> Is that so? "the community edition has never had
>>> a single feature, let alone platform, removed"
>>
>> So where is it then? The community version for Windows x86x64? Post
the 
>> link
>> maybe?
>> And what it this note here? -
>>
http://wrapper.tanukisoftware.com/doc/english/download.jsp#downloadNote1
>> I quote "*1: 64-bit Windows versions of the Java Service Wrapper are
not
>> currently being made available in the Community Edition."
>> Are you aware that on 64 bit windows, only 64 bit services can be
run?
>> I think so. So why do it? To make me buy the wrapper? Well, you are
>> unsuccessful.
>>
>> I don't mind buying a good software, I am a developer myself and know
the
>> value of this work.
>> But those kind of dirty tricks just makes me angry. GL.
>>
>> --------------------------------------------------
>> From: "Leif Mortenson" <lei...@ta...>
>> Sent: Wednesday, August 25, 2010 4:34 AM
>> To: <wra...@li...>
>> Subject: Re: [Wrapper-user] Greed takes down the community version of
Win
>> x64
>>
>>> Boris,
>>> Thank you for your constructive feedback, and for your first
>>> contribution to the community.
>>>
>>> I do need to correct you however, the community edition has never
had
>>> a single feature, let alone platform, removed.  To this date we are
>>> actively continuing to support and add to the platforms supported by
>>> the community edition.
>>>
>>> The reality is that developing software consumes a lot of resources.
>>> In the case of the Wrapper, after 8 years, thousands of hours of
time,
>>> and well over a million direct and indirect downloads, the
development
>>> community was still a team of one.   This was making it impossible
to
>>> keep the project alive and to keep up with requests for new
features.
>>> We decided to make the compromise of adding additional Standard and
>>> Professional editions to help fund development.  This has been very
>>> successful for the past 3 years.  The Wrapper, including the
Community
>>> Edition, is now very active with a team of several paid developers.
>>>
>>> We have been a long time contributor to open source, both with the
>>> Wrapper and other projects, as is easily visible with Google.
>>>
>>> Unfortunately, not every solution will make everyone happy.
>>>
>>> There are actually a few ways to launch a JVM as a service.  The
>>> Wrapper goes way beyond that however to actually protect, monitor,
and
>>> restart the JVM when needed.  It also contains a large number of
>>> features useful to both developers and system administrators.
>>>
>>> We are always looking for ways to make the Wrapper more useful and
>>> look forward to your feedback.
>>>
>>> Have a great day.
>>>
>>> Cheers,
>>> Leif
>>>
>>> 2010/8/25 Boris Hamanov <bs...@gm...>:
>>>> This wrapper software was recommended to me by Codehouse Jetty
>>>> documentation. I read all the help and decided to download it. What
was
>>>> my
>>>> surprise (very unpleasant one) when I discovered that my server
>>>> configuration is missing from the community version!  Windows x86
64 
>>>> bit!
>>>> The authors were taken by greed and decided that they will charge 
>>>> almost
>>>> 90
>>>> euro for that wrapper (at minimum).  So people with Windows x64
have 
>>>> more
>>>> money to waste is that it? I was so pissed off! I will never pay  a
>>>> single
>>>> cent for this software! I easily solved my simple need (to start my
>>>> server
>>>> on system startup) with Windows task scheduler. For less time that
took
>>>> me
>>>> to read the Java Service Wrapper docs, I might add. Here is my 
>>>> scheduler
>>>> task exported as an XML. You can import it and use it in any
version of
>>>> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this
on 
>>>> my
>>>> blog and notify Codehouse to stop recommending that software.
>>>>
>>>> <?xml version="1.0" encoding="UTF-16"?>
>>>> <Task version="1.2"
>>>> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>>>>   <RegistrationInfo>
>>>>     <Date>2010-08-24T18:11:18.0716</Date>
>>>>     <Author>GreenHouseV\bsh666</Author>
>>>>   </RegistrationInfo>
>>>>   <Triggers>
>>>>     <BootTrigger>
>>>>       <Enabled>true</Enabled>
>>>>     </BootTrigger>
>>>>   </Triggers>
>>>>   <Principals>
>>>>     <Principal id="Author">
>>>>       <UserId>SYSTEM</UserId>
>>>>       <RunLevel>LeastPrivilege</RunLevel>
>>>>     </Principal>
>>>>   </Principals>
>>>>   <Settings>
>>>>     <IdleSettings>
>>>>       <Duration>PT10M</Duration>
>>>>       <WaitTimeout>PT1H</WaitTimeout>
>>>>       <StopOnIdleEnd>true</StopOnIdleEnd>
>>>>       <RestartOnIdle>false</RestartOnIdle>
>>>>     </IdleSettings>
>>>>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>>>>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>>>>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>>>>     <AllowHardTerminate>true</AllowHardTerminate>
>>>>     <StartWhenAvailable>false</StartWhenAvailable>
>>>>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>>>>     <AllowStartOnDemand>true</AllowStartOnDemand>
>>>>     <Enabled>true</Enabled>
>>>>     <Hidden>false</Hidden>
>>>>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>>>>     <WakeToRun>false</WakeToRun>
>>>>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>>>>     <Priority>7</Priority>
>>>>   </Settings>
>>>>   <Actions Context="Author">
>>>>     <Exec>
>>>>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>>>>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>>>>     </Exec>
>>>>   </Actions>
>>>> </Task>
>
>
------------------------------------------------------------------------
------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook
users
> worldwide. Take advantage of special opportunities to increase revenue
and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user 


------------------------------------------------------------------------
------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Greed takes down the community version of Win x64

[Boris H. <bs...@gm...>]

I don't agree that 64 bit JVM is only needed for pro applications. Running 
32bit software on win64 involves emulation and that is overhead that nobody 
needs.
I have small web site and lightweight server, but still run it on 64 bit VM 
as this is the natural choice for my platform. Nowadays 64bit CPUs and oses 
are commonplace.
Nothing expensive in it anymore. So, please, step into the future and make 
this little gesture to the open source community. That one, as you said, has 
always been great to you.
I suppose mostly in the means that it promotes you and contributes to your 
software. And that means money. Do not think I eat grass.
I appreciate that you explained the situation though. You certainly have a 
point, but think about what I said. I am sure many people think like me and 
did you the courtesy of letting you know. You should not be frustrated, but 
grateful.

--------------------------------------------------
From: "Leif Mortenson" <lei...@ta...>
Sent: Wednesday, August 25, 2010 12:11 PM
To: <wra...@li...>
Subject: Re: [Wrapper-user] Greed takes down the community version of Win 
x64

> Boris,
> The 64-bit Windows version had never existed prior to version 3.3.0
> when we first released it in the Standard and Professional Edition.
> At the time, supporting the 64-bit Windows platform required the
> purchase of a new high end server specifically for that purpose along
> with a 64-bit copy of Windows XP, which at the time did not come
> cheap.  For this reason, and the ongoing need to support the
> development of the Wrapper, we have made the business decision to not
> make it available in the Community Edition for now.  This is also true
> for the z/Linux and z/OS platforms as they both have significant
> monthly server leasing charges we are covering.
>
> On Windows, you only need to use the 64-bit Windows version if you are
> running a 64-bit JVM.  It is possible to run the 32-bit Wrapper on a
> 64-bit Windows if you are also using a 32-bit JVM.  The 64-bit JVMs
> are mainly needed by very large applications which tend to be of a
> professional nature.  In these cases, yes, users would need to
> purchase a Standard Edition license.
>
> To be honest, comments like yours can be a bit frustrating.  Most
> companies never make anything available for free.  We have always made
> a great effort to generously support open source communities, both
> with the Wrapper and in other projects.  Yet when we decide to make
> small portion of our NEW features closed source to support the whole
> development, you call us greedy and complain.  I am glad that you were
> able to so easily find a solution which meets your needs and doesn't
> make you "angry".
>
> All well.  Regardless of whether or not you decide to make use of the
> Wrapper in your projects, we will continue to do our best to support
> the community which has always been great to us.
>
> I wish you the best in life.
> Cheers,
> Leif
>
> On Wed, Aug 25, 2010 at 5:02 PM, Boris Hamanov <bs...@gm...> wrote:
>> Is that so? "the community edition has never had
>>> a single feature, let alone platform, removed"
>>
>> So where is it then? The community version for Windows x86x64? Post the 
>> link
>> maybe?
>> And what it this note here? -
>> http://wrapper.tanukisoftware.com/doc/english/download.jsp#downloadNote1
>> I quote "*1: 64-bit Windows versions of the Java Service Wrapper are not
>> currently being made available in the Community Edition."
>> Are you aware that on 64 bit windows, only 64 bit services can be run?
>> I think so. So why do it? To make me buy the wrapper? Well, you are
>> unsuccessful.
>>
>> I don't mind buying a good software, I am a developer myself and know the
>> value of this work.
>> But those kind of dirty tricks just makes me angry. GL.
>>
>> --------------------------------------------------
>> From: "Leif Mortenson" <lei...@ta...>
>> Sent: Wednesday, August 25, 2010 4:34 AM
>> To: <wra...@li...>
>> Subject: Re: [Wrapper-user] Greed takes down the community version of Win
>> x64
>>
>>> Boris,
>>> Thank you for your constructive feedback, and for your first
>>> contribution to the community.
>>>
>>> I do need to correct you however, the community edition has never had
>>> a single feature, let alone platform, removed.  To this date we are
>>> actively continuing to support and add to the platforms supported by
>>> the community edition.
>>>
>>> The reality is that developing software consumes a lot of resources.
>>> In the case of the Wrapper, after 8 years, thousands of hours of time,
>>> and well over a million direct and indirect downloads, the development
>>> community was still a team of one.   This was making it impossible to
>>> keep the project alive and to keep up with requests for new features.
>>> We decided to make the compromise of adding additional Standard and
>>> Professional editions to help fund development.  This has been very
>>> successful for the past 3 years.  The Wrapper, including the Community
>>> Edition, is now very active with a team of several paid developers.
>>>
>>> We have been a long time contributor to open source, both with the
>>> Wrapper and other projects, as is easily visible with Google.
>>>
>>> Unfortunately, not every solution will make everyone happy.
>>>
>>> There are actually a few ways to launch a JVM as a service.  The
>>> Wrapper goes way beyond that however to actually protect, monitor, and
>>> restart the JVM when needed.  It also contains a large number of
>>> features useful to both developers and system administrators.
>>>
>>> We are always looking for ways to make the Wrapper more useful and
>>> look forward to your feedback.
>>>
>>> Have a great day.
>>>
>>> Cheers,
>>> Leif
>>>
>>> 2010/8/25 Boris Hamanov <bs...@gm...>:
>>>> This wrapper software was recommended to me by Codehouse Jetty
>>>> documentation. I read all the help and decided to download it. What was
>>>> my
>>>> surprise (very unpleasant one) when I discovered that my server
>>>> configuration is missing from the community version!  Windows x86 64 
>>>> bit!
>>>> The authors were taken by greed and decided that they will charge 
>>>> almost
>>>> 90
>>>> euro for that wrapper (at minimum).  So people with Windows x64 have 
>>>> more
>>>> money to waste is that it? I was so pissed off! I will never pay  a
>>>> single
>>>> cent for this software! I easily solved my simple need (to start my
>>>> server
>>>> on system startup) with Windows task scheduler. For less time that took
>>>> me
>>>> to read the Java Service Wrapper docs, I might add. Here is my 
>>>> scheduler
>>>> task exported as an XML. You can import it and use it in any version of
>>>> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on 
>>>> my
>>>> blog and notify Codehouse to stop recommending that software.
>>>>
>>>> <?xml version="1.0" encoding="UTF-16"?>
>>>> <Task version="1.2"
>>>> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>>>>   <RegistrationInfo>
>>>>     <Date>2010-08-24T18:11:18.0716</Date>
>>>>     <Author>GreenHouseV\bsh666</Author>
>>>>   </RegistrationInfo>
>>>>   <Triggers>
>>>>     <BootTrigger>
>>>>       <Enabled>true</Enabled>
>>>>     </BootTrigger>
>>>>   </Triggers>
>>>>   <Principals>
>>>>     <Principal id="Author">
>>>>       <UserId>SYSTEM</UserId>
>>>>       <RunLevel>LeastPrivilege</RunLevel>
>>>>     </Principal>
>>>>   </Principals>
>>>>   <Settings>
>>>>     <IdleSettings>
>>>>       <Duration>PT10M</Duration>
>>>>       <WaitTimeout>PT1H</WaitTimeout>
>>>>       <StopOnIdleEnd>true</StopOnIdleEnd>
>>>>       <RestartOnIdle>false</RestartOnIdle>
>>>>     </IdleSettings>
>>>>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>>>>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>>>>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>>>>     <AllowHardTerminate>true</AllowHardTerminate>
>>>>     <StartWhenAvailable>false</StartWhenAvailable>
>>>>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>>>>     <AllowStartOnDemand>true</AllowStartOnDemand>
>>>>     <Enabled>true</Enabled>
>>>>     <Hidden>false</Hidden>
>>>>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>>>>     <WakeToRun>false</WakeToRun>
>>>>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>>>>     <Priority>7</Priority>
>>>>   </Settings>
>>>>   <Actions Context="Author">
>>>>     <Exec>
>>>>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>>>>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>>>>     </Exec>
>>>>   </Actions>
>>>> </Task>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user 

Re: [Wrapper-user] Greed takes down the community version of Win x64

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

Boris,
The 64-bit Windows version had never existed prior to version 3.3.0
when we first released it in the Standard and Professional Edition.
At the time, supporting the 64-bit Windows platform required the
purchase of a new high end server specifically for that purpose along
with a 64-bit copy of Windows XP, which at the time did not come
cheap.  For this reason, and the ongoing need to support the
development of the Wrapper, we have made the business decision to not
make it available in the Community Edition for now.  This is also true
for the z/Linux and z/OS platforms as they both have significant
monthly server leasing charges we are covering.

On Windows, you only need to use the 64-bit Windows version if you are
running a 64-bit JVM.  It is possible to run the 32-bit Wrapper on a
64-bit Windows if you are also using a 32-bit JVM.  The 64-bit JVMs
are mainly needed by very large applications which tend to be of a
professional nature.  In these cases, yes, users would need to
purchase a Standard Edition license.

To be honest, comments like yours can be a bit frustrating.  Most
companies never make anything available for free.  We have always made
a great effort to generously support open source communities, both
with the Wrapper and in other projects.  Yet when we decide to make
small portion of our NEW features closed source to support the whole
development, you call us greedy and complain.  I am glad that you were
able to so easily find a solution which meets your needs and doesn't
make you "angry".

All well.  Regardless of whether or not you decide to make use of the
Wrapper in your projects, we will continue to do our best to support
the community which has always been great to us.

I wish you the best in life.
Cheers,
Leif

On Wed, Aug 25, 2010 at 5:02 PM, Boris Hamanov <bs...@gm...> wrote:
> Is that so? "the community edition has never had
>> a single feature, let alone platform, removed"
>
> So where is it then? The community version for Windows x86x64? Post the link
> maybe?
> And what it this note here? -
> http://wrapper.tanukisoftware.com/doc/english/download.jsp#downloadNote1
> I quote "*1: 64-bit Windows versions of the Java Service Wrapper are not
> currently being made available in the Community Edition."
> Are you aware that on 64 bit windows, only 64 bit services can be run?
> I think so. So why do it? To make me buy the wrapper? Well, you are
> unsuccessful.
>
> I don't mind buying a good software, I am a developer myself and know the
> value of this work.
> But those kind of dirty tricks just makes me angry. GL.
>
> --------------------------------------------------
> From: "Leif Mortenson" <lei...@ta...>
> Sent: Wednesday, August 25, 2010 4:34 AM
> To: <wra...@li...>
> Subject: Re: [Wrapper-user] Greed takes down the community version of Win
> x64
>
>> Boris,
>> Thank you for your constructive feedback, and for your first
>> contribution to the community.
>>
>> I do need to correct you however, the community edition has never had
>> a single feature, let alone platform, removed.  To this date we are
>> actively continuing to support and add to the platforms supported by
>> the community edition.
>>
>> The reality is that developing software consumes a lot of resources.
>> In the case of the Wrapper, after 8 years, thousands of hours of time,
>> and well over a million direct and indirect downloads, the development
>> community was still a team of one.   This was making it impossible to
>> keep the project alive and to keep up with requests for new features.
>> We decided to make the compromise of adding additional Standard and
>> Professional editions to help fund development.  This has been very
>> successful for the past 3 years.  The Wrapper, including the Community
>> Edition, is now very active with a team of several paid developers.
>>
>> We have been a long time contributor to open source, both with the
>> Wrapper and other projects, as is easily visible with Google.
>>
>> Unfortunately, not every solution will make everyone happy.
>>
>> There are actually a few ways to launch a JVM as a service.  The
>> Wrapper goes way beyond that however to actually protect, monitor, and
>> restart the JVM when needed.  It also contains a large number of
>> features useful to both developers and system administrators.
>>
>> We are always looking for ways to make the Wrapper more useful and
>> look forward to your feedback.
>>
>> Have a great day.
>>
>> Cheers,
>> Leif
>>
>> 2010/8/25 Boris Hamanov <bs...@gm...>:
>>> This wrapper software was recommended to me by Codehouse Jetty
>>> documentation. I read all the help and decided to download it. What was
>>> my
>>> surprise (very unpleasant one) when I discovered that my server
>>> configuration is missing from the community version!  Windows x86 64 bit!
>>> The authors were taken by greed and decided that they will charge almost
>>> 90
>>> euro for that wrapper (at minimum).  So people with Windows x64 have more
>>> money to waste is that it? I was so pissed off! I will never pay  a
>>> single
>>> cent for this software! I easily solved my simple need (to start my
>>> server
>>> on system startup) with Windows task scheduler. For less time that took
>>> me
>>> to read the Java Service Wrapper docs, I might add. Here is my scheduler
>>> task exported as an XML. You can import it and use it in any version of
>>> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on my
>>> blog and notify Codehouse to stop recommending that software.
>>>
>>> <?xml version="1.0" encoding="UTF-16"?>
>>> <Task version="1.2"
>>> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>>>   <RegistrationInfo>
>>>     <Date>2010-08-24T18:11:18.0716</Date>
>>>     <Author>GreenHouseV\bsh666</Author>
>>>   </RegistrationInfo>
>>>   <Triggers>
>>>     <BootTrigger>
>>>       <Enabled>true</Enabled>
>>>     </BootTrigger>
>>>   </Triggers>
>>>   <Principals>
>>>     <Principal id="Author">
>>>       <UserId>SYSTEM</UserId>
>>>       <RunLevel>LeastPrivilege</RunLevel>
>>>     </Principal>
>>>   </Principals>
>>>   <Settings>
>>>     <IdleSettings>
>>>       <Duration>PT10M</Duration>
>>>       <WaitTimeout>PT1H</WaitTimeout>
>>>       <StopOnIdleEnd>true</StopOnIdleEnd>
>>>       <RestartOnIdle>false</RestartOnIdle>
>>>     </IdleSettings>
>>>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>>>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>>>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>>>     <AllowHardTerminate>true</AllowHardTerminate>
>>>     <StartWhenAvailable>false</StartWhenAvailable>
>>>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>>>     <AllowStartOnDemand>true</AllowStartOnDemand>
>>>     <Enabled>true</Enabled>
>>>     <Hidden>false</Hidden>
>>>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>>>     <WakeToRun>false</WakeToRun>
>>>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>>>     <Priority>7</Priority>
>>>   </Settings>
>>>   <Actions Context="Author">
>>>     <Exec>
>>>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>>>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>>>     </Exec>
>>>   </Actions>
>>> </Task>

Re: [Wrapper-user] Greed takes down the community version of Win x64

[Boris H. <bs...@gm...>]

Is that so? "the community edition has never had
> a single feature, let alone platform, removed"

So where is it then? The community version for Windows x86x64? Post the link 
maybe?
And what it this note here? - 
http://wrapper.tanukisoftware.com/doc/english/download.jsp#downloadNote1
I quote "*1: 64-bit Windows versions of the Java Service Wrapper are not 
currently being made available in the Community Edition."
Are you aware that on 64 bit windows, only 64 bit services can be run?
I think so. So why do it? To make me buy the wrapper? Well, you are 
unsuccessful.

I don't mind buying a good software, I am a developer myself and know the 
value of this work.
But those kind of dirty tricks just makes me angry. GL.

--------------------------------------------------
From: "Leif Mortenson" <lei...@ta...>
Sent: Wednesday, August 25, 2010 4:34 AM
To: <wra...@li...>
Subject: Re: [Wrapper-user] Greed takes down the community version of Win 
x64

> Boris,
> Thank you for your constructive feedback, and for your first
> contribution to the community.
>
> I do need to correct you however, the community edition has never had
> a single feature, let alone platform, removed.  To this date we are
> actively continuing to support and add to the platforms supported by
> the community edition.
>
> The reality is that developing software consumes a lot of resources.
> In the case of the Wrapper, after 8 years, thousands of hours of time,
> and well over a million direct and indirect downloads, the development
> community was still a team of one.   This was making it impossible to
> keep the project alive and to keep up with requests for new features.
> We decided to make the compromise of adding additional Standard and
> Professional editions to help fund development.  This has been very
> successful for the past 3 years.  The Wrapper, including the Community
> Edition, is now very active with a team of several paid developers.
>
> We have been a long time contributor to open source, both with the
> Wrapper and other projects, as is easily visible with Google.
>
> Unfortunately, not every solution will make everyone happy.
>
> There are actually a few ways to launch a JVM as a service.  The
> Wrapper goes way beyond that however to actually protect, monitor, and
> restart the JVM when needed.  It also contains a large number of
> features useful to both developers and system administrators.
>
> We are always looking for ways to make the Wrapper more useful and
> look forward to your feedback.
>
> Have a great day.
>
> Cheers,
> Leif
>
> 2010/8/25 Boris Hamanov <bs...@gm...>:
>> This wrapper software was recommended to me by Codehouse Jetty
>> documentation. I read all the help and decided to download it. What was 
>> my
>> surprise (very unpleasant one) when I discovered that my server
>> configuration is missing from the community version!  Windows x86 64 bit!
>> The authors were taken by greed and decided that they will charge almost 
>> 90
>> euro for that wrapper (at minimum).  So people with Windows x64 have more
>> money to waste is that it? I was so pissed off! I will never pay  a 
>> single
>> cent for this software! I easily solved my simple need (to start my 
>> server
>> on system startup) with Windows task scheduler. For less time that took 
>> me
>> to read the Java Service Wrapper docs, I might add. Here is my scheduler
>> task exported as an XML. You can import it and use it in any version of
>> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on my
>> blog and notify Codehouse to stop recommending that software.
>>
>> <?xml version="1.0" encoding="UTF-16"?>
>> <Task version="1.2"
>> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>>   <RegistrationInfo>
>>     <Date>2010-08-24T18:11:18.0716</Date>
>>     <Author>GreenHouseV\bsh666</Author>
>>   </RegistrationInfo>
>>   <Triggers>
>>     <BootTrigger>
>>       <Enabled>true</Enabled>
>>     </BootTrigger>
>>   </Triggers>
>>   <Principals>
>>     <Principal id="Author">
>>       <UserId>SYSTEM</UserId>
>>       <RunLevel>LeastPrivilege</RunLevel>
>>     </Principal>
>>   </Principals>
>>   <Settings>
>>     <IdleSettings>
>>       <Duration>PT10M</Duration>
>>       <WaitTimeout>PT1H</WaitTimeout>
>>       <StopOnIdleEnd>true</StopOnIdleEnd>
>>       <RestartOnIdle>false</RestartOnIdle>
>>     </IdleSettings>
>>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>>     <AllowHardTerminate>true</AllowHardTerminate>
>>     <StartWhenAvailable>false</StartWhenAvailable>
>>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>>     <AllowStartOnDemand>true</AllowStartOnDemand>
>>     <Enabled>true</Enabled>
>>     <Hidden>false</Hidden>
>>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>>     <WakeToRun>false</WakeToRun>
>>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>>     <Priority>7</Priority>
>>   </Settings>
>>   <Actions Context="Author">
>>     <Exec>
>>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>>     </Exec>
>>   </Actions>
>> </Task>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

Re: [Wrapper-user] Greed takes down the community version of Win x64

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

Boris,
Thank you for your constructive feedback, and for your first
contribution to the community.

I do need to correct you however, the community edition has never had
a single feature, let alone platform, removed.  To this date we are
actively continuing to support and add to the platforms supported by
the community edition.

The reality is that developing software consumes a lot of resources.
In the case of the Wrapper, after 8 years, thousands of hours of time,
and well over a million direct and indirect downloads, the development
community was still a team of one.   This was making it impossible to
keep the project alive and to keep up with requests for new features.
 We decided to make the compromise of adding additional Standard and
Professional editions to help fund development.  This has been very
successful for the past 3 years.  The Wrapper, including the Community
Edition, is now very active with a team of several paid developers.

We have been a long time contributor to open source, both with the
Wrapper and other projects, as is easily visible with Google.

Unfortunately, not every solution will make everyone happy.

There are actually a few ways to launch a JVM as a service.  The
Wrapper goes way beyond that however to actually protect, monitor, and
restart the JVM when needed.  It also contains a large number of
features useful to both developers and system administrators.

We are always looking for ways to make the Wrapper more useful and
look forward to your feedback.

Have a great day.

Cheers,
Leif

2010/8/25 Boris Hamanov <bs...@gm...>:
> This wrapper software was recommended to me by Codehouse Jetty
> documentation. I read all the help and decided to download it. What was my
> surprise (very unpleasant one) when I discovered that my server
> configuration is missing from the community version!  Windows x86 64 bit!
> The authors were taken by greed and decided that they will charge almost 90
> euro for that wrapper (at minimum).  So people with Windows x64 have more
> money to waste is that it? I was so pissed off! I will never pay  a single
> cent for this software! I easily solved my simple need (to start my server
> on system startup) with Windows task scheduler. For less time that took me
> to read the Java Service Wrapper docs, I might add. Here is my scheduler
> task exported as an XML. You can import it and use it in any version of
> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on my
> blog and notify Codehouse to stop recommending that software.
>
> <?xml version="1.0" encoding="UTF-16"?>
> <Task version="1.2"
> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>   <RegistrationInfo>
>     <Date>2010-08-24T18:11:18.0716</Date>
>     <Author>GreenHouseV\bsh666</Author>
>   </RegistrationInfo>
>   <Triggers>
>     <BootTrigger>
>       <Enabled>true</Enabled>
>     </BootTrigger>
>   </Triggers>
>   <Principals>
>     <Principal id="Author">
>       <UserId>SYSTEM</UserId>
>       <RunLevel>LeastPrivilege</RunLevel>
>     </Principal>
>   </Principals>
>   <Settings>
>     <IdleSettings>
>       <Duration>PT10M</Duration>
>       <WaitTimeout>PT1H</WaitTimeout>
>       <StopOnIdleEnd>true</StopOnIdleEnd>
>       <RestartOnIdle>false</RestartOnIdle>
>     </IdleSettings>
>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>     <AllowHardTerminate>true</AllowHardTerminate>
>     <StartWhenAvailable>false</StartWhenAvailable>
>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>     <AllowStartOnDemand>true</AllowStartOnDemand>
>     <Enabled>true</Enabled>
>     <Hidden>false</Hidden>
>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>     <WakeToRun>false</WakeToRun>
>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>     <Priority>7</Priority>
>   </Settings>
>   <Actions Context="Author">
>     <Exec>
>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>     </Exec>
>   </Actions>
> </Task>

[Wrapper-user] Greed takes down the community version of Win x64

[Boris H. <bs...@gm...>]

This wrapper software was recommended to me by Codehouse Jetty documentation. I read all the help and decided to download it. What was my surprise (very unpleasant one) when I discovered that my server configuration is missing from the community version!  Windows x86 64 bit! The authors were taken by greed and decided that they will charge almost 90 euro for that wrapper (at minimum).  So people with Windows x64 have more money to waste is that it? I was so pissed off! I will never pay  a single cent for this software! I easily solved my simple need (to start my server on system startup) with Windows task scheduler. For less time that took me to read the Java Service Wrapper docs, I might add. Here is my scheduler task exported as an XML. You can import it and use it in any version of Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on my blog and notify Codehouse to stop recommending that software.

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2010-08-24T18:11:18.0716</Date>
    <Author>GreenHouseV\bsh666</Author>
  </RegistrationInfo>
  <Triggers>
    <BootTrigger>
      <Enabled>true</Enabled>
    </BootTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>SYSTEM</UserId>
      <RunLevel>LeastPrivilege</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <IdleSettings>
      <Duration>PT10M</Duration>
      <WaitTimeout>PT1H</WaitTimeout>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
      <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
    </Exec>
  </Actions>
</Task>

Re: [Wrapper-user] Cannot start application in service.

[Christian <chr...@ta...>]

Jeff,

I have just added a new property (wrapper.java.command.resolve) in order
to control whether the wrapper will try to resolve the path to the jvm
specified by the wrapper.java.command or not.

This property will be part of the 3.5.4 release we are going to release
this week (around Wednesday).

I hope this will help you to use run-java-tool on Gentoo.

Cheers,
Christian


-----Original Message-----
From: Jeff Shanab <js...@ea...>
Reply-to: wra...@li...
To: wra...@li...
Subject: Re: [Wrapper-user] Cannot start application in service.
Date: Sun, 22 Aug 2010 10:44:07 -0500

My suspicion after you helped me and I got it working, was that the script returns immediately and appears to JSW as a VM that ran
for less than a second.

The second post looks like it supports that by modifing the way the script ends, the && java on the end starts the longer apperaing
running java process. ?

Gentoo is just my distro of choice and I am poring to linux an application written with the JSW for installation on windows 2003
sever. I am guesing that the customer will want ubuntu or fedora and I will package accordingly later.

> Jeff,
> I also found the following:
> http://www.infohit.net/blog/post/run-java-tool-was-invoked-directly.html
> and this
> http://dingfelder.wordpress.com/2007/07/14/installing-eclipse-33-on-gentoo/
> 
> It does appear to be a Gentoo thing.  I would like to find out exactly
> what you were doing to help with future requests.
> 
> The Wrapper always goes through and resolves any and all symbolic
> links to get to the real path of a file a file reference.   That might
> have something to do with why you were getting the following message:
> ---
> jvm 5    | * run-java-tool was invoked directly
> jvm 5    | * run-java-tool should only be used via symlinks to it
> ---
> 
> Cheers,
> Leif
> 
> On Sat, Aug 21, 2010 at 1:48 PM, Jeff Shanab <js...@ea...> wrote:
>> Thanks. (I guess I have become de-sensitized by warnings. :-)
>>
>> That sucks. I think it is a gentoo thing
>>
>> I went back to the default %JAVA_HOME%/bin/java and it started up. Thanks!
>>
>>
>>> Jeff,
>>> What does your wrapper.conf look like?  The error about the use
>>> of run-java-tool  is the problem
>>>
>>> - Leif
>>>
>>>
>>> On 2010/08/21, at 8:53, Jeff Shanab <js...@ea...
>>> <mailto:js...@ea...>> wrote:
>>>
>>>> run-java-tool
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Cannot start application in service.

[Jeff S. <js...@ea...>]

My suspicion after you helped me and I got it working, was that the script returns immediately and appears to JSW as a VM that ran
for less than a second.

The second post looks like it supports that by modifing the way the script ends, the && java on the end starts the longer apperaing
running java process. ?

Gentoo is just my distro of choice and I am poring to linux an application written with the JSW for installation on windows 2003
sever. I am guesing that the customer will want ubuntu or fedora and I will package accordingly later.

> Jeff,
> I also found the following:
> http://www.infohit.net/blog/post/run-java-tool-was-invoked-directly.html
> and this
> http://dingfelder.wordpress.com/2007/07/14/installing-eclipse-33-on-gentoo/
> 
> It does appear to be a Gentoo thing.  I would like to find out exactly
> what you were doing to help with future requests.
> 
> The Wrapper always goes through and resolves any and all symbolic
> links to get to the real path of a file a file reference.   That might
> have something to do with why you were getting the following message:
> ---
> jvm 5    | * run-java-tool was invoked directly
> jvm 5    | * run-java-tool should only be used via symlinks to it
> ---
> 
> Cheers,
> Leif
> 
> On Sat, Aug 21, 2010 at 1:48 PM, Jeff Shanab <js...@ea...> wrote:
>> Thanks. (I guess I have become de-sensitized by warnings. :-)
>>
>> That sucks. I think it is a gentoo thing
>>
>> I went back to the default %JAVA_HOME%/bin/java and it started up. Thanks!
>>
>>
>>> Jeff,
>>> What does your wrapper.conf look like?  The error about the use
>>> of run-java-tool  is the problem
>>>
>>> - Leif
>>>
>>>
>>> On 2010/08/21, at 8:53, Jeff Shanab <js...@ea...
>>> <mailto:js...@ea...>> wrote:
>>>
>>>> run-java-tool
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

Re: [Wrapper-user] Cannot start application in service.

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

Jeff,
I also found the following:
http://www.infohit.net/blog/post/run-java-tool-was-invoked-directly.html
and this
http://dingfelder.wordpress.com/2007/07/14/installing-eclipse-33-on-gentoo/

It does appear to be a Gentoo thing.  I would like to find out exactly
what you were doing to help with future requests.

The Wrapper always goes through and resolves any and all symbolic
links to get to the real path of a file a file reference.   That might
have something to do with why you were getting the following message:
---
jvm 5    | * run-java-tool was invoked directly
jvm 5    | * run-java-tool should only be used via symlinks to it
---

Cheers,
Leif

On Sat, Aug 21, 2010 at 1:48 PM, Jeff Shanab <js...@ea...> wrote:
> Thanks. (I guess I have become de-sensitized by warnings. :-)
>
> That sucks. I think it is a gentoo thing
>
> I went back to the default %JAVA_HOME%/bin/java and it started up. Thanks!
>
>
>> Jeff,
>> What does your wrapper.conf look like?  The error about the use
>> of run-java-tool  is the problem
>>
>> - Leif
>>
>>
>> On 2010/08/21, at 8:53, Jeff Shanab <js...@ea...
>> <mailto:js...@ea...>> wrote:
>>
>>> run-java-tool

Re: [Wrapper-user] Cannot start application in service.

[Jeff S. <js...@ea...>]

Thanks. (I guess I have become de-sensitized by warnings. :-)

That sucks. I think it is a gentoo thing

I went back to the default %JAVA_HOME%/bin/java and it started up. Thanks!


> Jeff,
> What does your wrapper.conf look like?  The error about the use
> of run-java-tool  is the problem
> 
> - Leif
> 
> 
> On 2010/08/21, at 8:53, Jeff Shanab <js...@ea...
> <mailto:js...@ea...>> wrote:
> 
>> run-java-tool
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> 
> 
> 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Cannot start application in service.

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

Jeff,
What does your wrapper.conf look like?  The error about the use of run- 
java-tool  is the problem

- Leif


On 2010/08/21, at 8:53, Jeff Shanab <js...@ea...> wrote:

> run-java-tool

[Wrapper-user] Cannot start application in service.

[Jeff S. <js...@ea...>]

I have used the Java Service Wrapper in the past with success but am having trouble with a new application.

It runs from the command line ok.

The logs do not show a specific problem

...
wrapper  | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30
wrapper  | Launching a JVM...
wrapper  | Signal trapped.  Details:
wrapper  |   signal number=17 (SIGCHLD), source="unknown"
wrapper  | Received SIGCHLD, checking JVM process status.
wrapper  | JVM process exited with a code of 1, setting the wrapper exit code to 1.
wrapper  | JVM exited while loading the application.
jvm 5    | * run-java-tool was invoked directly
jvm 5    | * run-java-tool should only be used via symlinks to it
wrapper  | JVM was only running for 0 seconds leading to a failed restart count of 5.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapperp | closing backend server.
wrapper  | <-- Wrapper Stopped