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

[Wrapper-user] Use log4j2 with the wrapper - plus JSON log output

[Tue D. <Tue...@en...>]

Hi Guys,

Trying to user log4j2 as the logging framework. Our own application is already using log4j2, but it doesn't seem possible to control this for the service wrapper.

What I really need is a way to output JSON to the console. Anyone that have made this possible?



Tue S. Dissing
Technical Lead

CDRator
An Enghouse Networks Company
________________________________
m: +45 29 71 04 00
e:   tue...@en...<mailto:tue...@en...>
w:  www.cdrator.com<http://www.cdrator.com/>
w:  www.enghousenetworks.com<http://www.enghousenetworks.com/>
__________________________________

[Wrapper-user] Java Service Wrapper 3.5.34 released!

[Maxime <ma...@ta...>]

Hello everyone,

We are proud to announce the release of version 3.5.34 of the Java Service
Wrapper.
http://wrapper.tanukisoftware.org/doc/english/download.jsp

This version includes several bug fixes and improvements. You can review
the release notes for a full list of changes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let us know if you have any questions about the release.

Sincerely,

Java Service Wrapper Team
Tanuki Software, Ltd.

Re: [Wrapper-user] Problem starting wrapper (version 3.5.33)

[Cliff M. <cli...@gm...>]

Found it. It was buried in the App. Stupid, stupid check. Thanks!

--

Cliff

On Mon, Sep 25, 2017 at 10:46 PM, Maxime <ma...@ta...> wrote:

> Cliff,
>
> Please check why your java application requires those versions of java and
> if the condition can be changed in your code.
> There is nothing that the Wrapper can do about it since this restriction
> is set on the java application.
>
> Best Regards,
>
> Maxime
>
> On Tue, Sep 26, 2017 at 11:37 AM, Cliff Martin <cli...@gm...>
> wrote:
>
>> Jre is not validated. Java must be within 1.6.0 and 1.8.0. actual version
>> is 1.8.0_144
>>
>> On Mon, Sep 25, 2017, 8:25 PM Maxime <ma...@ta...> wrote:
>>
>>> Cliff,
>>>
>>> Thank you for your email.
>>>
>>> The Java Service Wrapper supports all versions of Java from 1.4.
>>> Is this restriction on your Java Application? If so, can you edit the
>>> code to lift this limit?
>>> Which message is it showing exactly?
>>>
>>> Best Regards,
>>>
>>> Maxime
>>>
>>> On Tue, Sep 26, 2017 at 2:15 AM, Cliff Martin <cli...@gm...>
>>> wrote:
>>>
>>>> I have Java 1.8.0_144 installed, and the Windows service I am trying to
>>>> start stops with a validation error on the JRE saying to only supports
>>>> versions 1.6.0 - 1.8.0. Presumably it thinks 1.8.0_144 > 1.8.0. How do I
>>>> fix this? Is there a configuration option to ignore the version, or set it
>>>> to 9?
>>>>
>>>> --
>>>>
>>>> Cliff
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>>> _________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Problem starting wrapper (version 3.5.33)

[Maxime <ma...@ta...>]

Cliff,

Please check why your java application requires those versions of java and
if the condition can be changed in your code.
There is nothing that the Wrapper can do about it since this restriction is
set on the java application.

Best Regards,

Maxime

On Tue, Sep 26, 2017 at 11:37 AM, Cliff Martin <cli...@gm...>
wrote:

> Jre is not validated. Java must be within 1.6.0 and 1.8.0. actual version
> is 1.8.0_144
>
> On Mon, Sep 25, 2017, 8:25 PM Maxime <ma...@ta...> wrote:
>
>> Cliff,
>>
>> Thank you for your email.
>>
>> The Java Service Wrapper supports all versions of Java from 1.4.
>> Is this restriction on your Java Application? If so, can you edit the
>> code to lift this limit?
>> Which message is it showing exactly?
>>
>> Best Regards,
>>
>> Maxime
>>
>> On Tue, Sep 26, 2017 at 2:15 AM, Cliff Martin <cli...@gm...>
>> wrote:
>>
>>> I have Java 1.8.0_144 installed, and the Windows service I am trying to
>>> start stops with a validation error on the JRE saying to only supports
>>> versions 1.6.0 - 1.8.0. Presumably it thinks 1.8.0_144 > 1.8.0. How do I
>>> fix this? Is there a configuration option to ignore the version, or set it
>>> to 9?
>>>
>>> --
>>>
>>> Cliff
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>> _________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Problem starting wrapper (version 3.5.33)

[Cliff M. <cli...@gm...>]

Jre is not validated. Java must be within 1.6.0 and 1.8.0. actual version
is 1.8.0_144

On Mon, Sep 25, 2017, 8:25 PM Maxime <ma...@ta...> wrote:

> Cliff,
>
> Thank you for your email.
>
> The Java Service Wrapper supports all versions of Java from 1.4.
> Is this restriction on your Java Application? If so, can you edit the code
> to lift this limit?
> Which message is it showing exactly?
>
> Best Regards,
>
> Maxime
>
> On Tue, Sep 26, 2017 at 2:15 AM, Cliff Martin <cli...@gm...>
> wrote:
>
>> I have Java 1.8.0_144 installed, and the Windows service I am trying to
>> start stops with a validation error on the JRE saying to only supports
>> versions 1.6.0 - 1.8.0. Presumably it thinks 1.8.0_144 > 1.8.0. How do I
>> fix this? Is there a configuration option to ignore the version, or set it
>> to 9?
>>
>> --
>>
>> Cliff
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Problem starting wrapper (version 3.5.33)

[Maxime <ma...@ta...>]

Cliff,

Thank you for your email.

The Java Service Wrapper supports all versions of Java from 1.4.
Is this restriction on your Java Application? If so, can you edit the code
to lift this limit?
Which message is it showing exactly?

Best Regards,

Maxime

On Tue, Sep 26, 2017 at 2:15 AM, Cliff Martin <cli...@gm...>
wrote:

> I have Java 1.8.0_144 installed, and the Windows service I am trying to
> start stops with a validation error on the JRE saying to only supports
> versions 1.6.0 - 1.8.0. Presumably it thinks 1.8.0_144 > 1.8.0. How do I
> fix this? Is there a configuration option to ignore the version, or set it
> to 9?
>
> --
>
> Cliff
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Problem starting wrapper (version 3.5.33)

[Cliff M. <cli...@gm...>]

I have Java 1.8.0_144 installed, and the Windows service I am trying to
start stops with a validation error on the JRE saying to only supports
versions 1.6.0 - 1.8.0. Presumably it thinks 1.8.0_144 > 1.8.0. How do I
fix this? Is there a configuration option to ignore the version, or set it
to 9?

--

Cliff

Re: [Wrapper-user] Please add "JSON" to logging format

[Maxime <ma...@ta...>]

Watanabe

Thank you for your email and your suggestion to add JSON as possible log
format. This is indeed an interesting idea.

Actually we did not plan to add support for json format in the near future,
but we will surely keep the idea in mind and discuss about it. The ability
to easily process and parse the json format is indeed a good point,
although as pointed by Karthik, other formats would also have this feature.

In the current versions, we try to keep the logging features of the Wrapper
easy to configure for the users and we generally advise to use tools such
as log4j for specific needs. Help on how to output JSON with log4j can
easily be found on the internet.

Please let us know if you have any other remarks or suggestions.

Best Regards,

Maxime

On Thu, Sep 14, 2017 at 8:52 AM, Y.Watanabe <na...@gm...> wrote:

> Hi. Sorry to late reply.
> This is just a problem of log format choice.
> I feel good json to log format, another one likes txt splitter by pipe.
> And in the world, Json is the standard format. Elasticsearch,
> fluentd,logstash...
> I am waiting that JSW support json for one of the supported log format.
>
>
> 2017年7月23日(日) 14:20 Karthik Kumar Viswanathan <kar...@gm...>:
>
>> It's a good idea, but I have these ideas on them:
>>
>> - JSON isn't an appendable format, and this sort of log will not be well
>> formed JSON.
>> - CSV and YAML are good ideas - and they do support incremental updates
>> and parsing libraries are available.
>> - TXT files do allow appending and incremental updates are possible -
>> except, they require escaping \n s in Exceptions etc.
>>
>> On 23 July 2017 at 10:29, Y.Watanabe <na...@gm...> wrote:
>>
>>> Hi.
>>> I hope that JSW have "JSON" format configuration on
>>> "wrapper.console.format".
>>>
>>> Belong to "12-factor app" theory, (https://12factor.net/ )
>>> Our Java-Web application logs to STDOUT,
>>> and JSW catches the stdout log, write into "wrapper.log"
>>>
>>> So, both of JSW log and application log into one file like below.
>>>
>>> STATUS | wrapper  | 2015/11/01 13:45:33.560 | JVM start......
>>> {"severity":"INFO","datetime":"2015-11-01 17:05:27
>>> -0700","msg":"foobar"}
>>>
>>> But it is not convinient to use jq command line tool like this.
>>>
>>> $ cat test.log | jq .
>>> parse error: Invalid numeric literal at line 1, column 7
>>>
>>> If JSW log format support JSON,
>>>
>>> {"STATUS":"wrapper","datetime":"2015/11/01 13:45:33.560", "msg":"JVM
>>> start."}
>>> {"severity":"INFO","datetime":"2015-11-01 17:05:27
>>> -0700","msg":"foobar"}
>>>
>>> I can use "jq" or any other tool for json !
>>>
>>> $ cat test.log | jq .
>>> {
>>>   "STATUS": "wrapper",
>>>   "datetime": "2015/11/01 13:45:33.560",
>>>   "msg": "JVM start."
>>> }
>>> {
>>>   "severity": "INFO",
>>>   "datetime": "2015-11-01 17:05:27 -0700",
>>>   "msg": "foobar"
>>> }
>>>
>>>
>>> Regards.
>>>
>>> ----
>>> Watanabe.
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>> _________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Please add "JSON" to logging format

[Y.Watanabe <na...@gm...>]

Hi. Sorry to late reply.
This is just a problem of log format choice.
I feel good json to log format, another one likes txt splitter by pipe.
And in the world, Json is the standard format. Elasticsearch,
fluentd,logstash...
I am waiting that JSW support json for one of the supported log format.


2017年7月23日(日) 14:20 Karthik Kumar Viswanathan <kar...@gm...>:

> It's a good idea, but I have these ideas on them:
>
> - JSON isn't an appendable format, and this sort of log will not be well
> formed JSON.
> - CSV and YAML are good ideas - and they do support incremental updates
> and parsing libraries are available.
> - TXT files do allow appending and incremental updates are possible -
> except, they require escaping \n s in Exceptions etc.
>
> On 23 July 2017 at 10:29, Y.Watanabe <na...@gm...> wrote:
>
>> Hi.
>> I hope that JSW have "JSON" format configuration on
>> "wrapper.console.format".
>>
>> Belong to "12-factor app" theory, (https://12factor.net/ )
>> Our Java-Web application logs to STDOUT,
>> and JSW catches the stdout log, write into "wrapper.log"
>>
>> So, both of JSW log and application log into one file like below.
>>
>> STATUS | wrapper  | 2015/11/01 13:45:33.560 | JVM start......
>> {"severity":"INFO","datetime":"2015-11-01 17:05:27 -0700","msg":"foobar"}
>>
>> But it is not convinient to use jq command line tool like this.
>>
>> $ cat test.log | jq .
>> parse error: Invalid numeric literal at line 1, column 7
>>
>> If JSW log format support JSON,
>>
>> {"STATUS":"wrapper","datetime":"2015/11/01 13:45:33.560", "msg":"JVM
>> start."}
>> {"severity":"INFO","datetime":"2015-11-01 17:05:27 -0700","msg":"foobar"}
>>
>> I can use "jq" or any other tool for json !
>>
>> $ cat test.log | jq .
>> {
>>   "STATUS": "wrapper",
>>   "datetime": "2015/11/01 13:45:33.560",
>>   "msg": "JVM start."
>> }
>> {
>>   "severity": "INFO",
>>   "datetime": "2015-11-01 17:05:27 -0700",
>>   "msg": "foobar"
>> }
>>
>>
>> Regards.
>>
>> ----
>> Watanabe.
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Java service crashed after 5 hours

[Maxime A. <max...@ta...>]

Hana

Thank you for your email.

These restarts are initiated by the OS. As you can see in the log, the
Wrapper catches a SERVICE_CONTROL_STOP signal (for example at 10:17:18) and
stops in response. This may happen for instance when you stop the service
from the "Services" window accessible from the control panel. The Wrapper
is behaving normally here, so if those restarts are unexpected the cause
should be searched at the OS level.

Around both 10:17:59 and 19:29:00, the Wrapper is forwarding the logs of
the JVM normally, so any log message coming from your application will also
be printed by the Wrapper. Unfortunately it seems that for some reason your
application doesn't always catch the file as expected, although it is still
running. You should probably add some debug messages in your code to better
understand what your application is doing.

Best Regards,

Maxime

On Tue, Aug 29, 2017 at 10:43 AM, Hana Wu <Ha...@se...> wrote:

> Hi Team,
>
>
>
> Thanks for your feedback, I set the ‘wrapper.debug’ to true and running
> one month. It works well, but today it crashed again, the details log in
> attachment. The service be restarted at 18:00 everyday.  You can see the
> log,
>
>
>
> Service be restarted 10:17:18, and the new file coming in at 10:17:59, it
> caught. Then
>
> Service be restarted 18:00:00, and the new file coming in at 19:29:00, It
> did not catch it.
>
>
>
> Could you help check?
>
>
>
> Thanks so much,
>
> Hana
>
>
>
> *From:* Maxime [mailto:ma...@ta...]
> *Sent:* Monday, 24 July 2017 12:26 p.m.
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] Java service crashed after 5 hours
>
>
>
> Hana
>
> Thank you for your email.
>
> Could you please run the Wrapper in debug mode and send us the log file so
> that we can see more outputs just before the Wrapper stops? To execute in
> debug mode, just set wrapper.debug=TRUE and make sure the property is not
> commented, then relaunch the Wrapper.
>
> Note that in your configuration you have set the
> wrapper.ntservice.recovery.* properties of the standard edition but they
> will be ignored because you are using the community edition. This should
> not cause the Wrapper to stop though.
>
> Best Regards,
>
> Maxime
>
>
>
> 2017-07-24 11:41 GMT+09:00 Hana Wu <Ha...@se...>:
>
> Hi Team,
>
>
>
> Thanks for your help.
>
>
>
> I used java service wrapper to running a jar file. My java application is
> for monitoring a folder if it has a new file coming in, the service can
> started and working well for several hours, after that, it doesn’t work,
> need restart service.
>
>
>
> Below is the detailed information:
>
>
>
>
>
>    - The version of the Wrapper you are using. - *Java Service Wrapper
>    Community Edition 32-bit 3.5.32*
>    The OS and version that you are running on. – *Windows Server 2008 R2
>    Datacenter, 64 bit OS*
>    - Your wrapper.conf file. – see attachment
>    - Your wrapper.log file. – see attachment
>
>
>
> Thanks,
>
> Hana
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>


-- 
Maxime Andrighetto
Tanuki Software Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

[Hana Wu <Ha...@se...>]

Thanks, I understand☺

From: Maxime [mailto:ma...@ta...]
Sent: Tuesday, 29 August 2017 5:07 p.m.
To: wra...@li...
Subject: Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hana

I am not sure to understand your question. Do you mean the "previous" version?

Since version 3.5.31, we stopped allowing the Wrapper to run when versions of wrapper.exe and native library (wrapper.dll) do not match or when the native libary can't be loaded.
By nature, a 64-bit JVM can't load the 32-bit native library, and the Wrapper will now stop after failing to load it. Older versions of the Wrapper used to show a warning and then attempted to continue, but this would often lead to unpredictable behaviour and many features simply not working.
Best Regards,
Maxime

On Tue, Aug 29, 2017 at 5:34 PM, Hana Wu <Ha...@se...<mailto:Ha...@se...>> wrote:
The last version can support, right?

From: Maxime [mailto:ma...@ta...<mailto:ma...@ta...>]
Sent: Tuesday, 29 August 2017 4:14 p.m.
To: wra...@li...<mailto:wra...@li...>
Subject: Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hana
Thank you for your email.

The 32-bit version of the Wrapper won't work with a 64-bit JVM. You will need to use the 64-bit version instead.
You may download and try it on the download page of the Java Service Wrapper website.

https://wrapper.tanukisoftware.com/doc/english/download.jsp
Best Regards,
Maxime

On Tue, Aug 29, 2017 at 4:41 PM, Hana Wu <Ha...@se...<mailto:Ha...@se...>> wrote:
Hi Maxime,

Thanks, For 3.5.33 version, Does 32-bit community support 64-bit windows VM?

Thanks,
Hana

From: Maxime [mailto:ma...@ta...<mailto:ma...@ta...>]
Sent: Wednesday, 26 July 2017 10:31 a.m.
To: wra...@li...<mailto:wra...@li...>
Subject: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hello everyone,

We are proud to announce the release of version 3.5.33 of the Java Service Wrapper.
http://wrapper.tanukisoftware.org/doc/english/download.jsp

This version includes several bug fixes and improvements. You can review the release notes for a full list of changes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let us know if you have any questions about the release.

Sincerely,

Java Service Wrapper Team
Tanuki Software, Ltd.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Wrapper-user mailing list
Wra...@li...<mailto:Wra...@li...>
https://lists.sourceforge.net/lists/listinfo/wrapper-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Wrapper-user mailing list
Wra...@li...<mailto:Wra...@li...>
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

[Maxime <ma...@ta...>]

Hana

I am not sure to understand your question. Do you mean the "previous"
version?

Since version 3.5.31, we stopped allowing the Wrapper to run when versions
of wrapper.exe and native library (wrapper.dll) do not match or when the
native libary can't be loaded.
By nature, a 64-bit JVM can't load the 32-bit native library, and the
Wrapper will now stop after failing to load it. Older versions of the
Wrapper used to show a warning and then attempted to continue, but this
would often lead to unpredictable behaviour and many features simply not
working.

Best Regards,

Maxime

On Tue, Aug 29, 2017 at 5:34 PM, Hana Wu <Ha...@se...> wrote:

> The last version can support, right?
>
>
>
> *From:* Maxime [mailto:ma...@ta...]
> *Sent:* Tuesday, 29 August 2017 4:14 p.m.
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!
>
>
>
> Hana
>
> Thank you for your email.
>
>
>
> The 32-bit version of the Wrapper won't work with a 64-bit JVM. You will
> need to use the 64-bit version instead.
>
> You may download and try it on the download page of the Java Service
> Wrapper website.
>
> https://wrapper.tanukisoftware.com/doc/english/download.jsp
>
> Best Regards,
>
> Maxime
>
>
>
> On Tue, Aug 29, 2017 at 4:41 PM, Hana Wu <Ha...@se...> wrote:
>
> Hi Maxime,
>
>
>
> Thanks, For 3.5.33 version, Does 32-bit community support 64-bit windows
> VM?
>
>
>
> Thanks,
>
> Hana
>
>
>
> *From:* Maxime [mailto:ma...@ta...]
> *Sent:* Wednesday, 26 July 2017 10:31 a.m.
> *To:* wra...@li...
> *Subject:* [Wrapper-user] Java Service Wrapper 3.5.33 released!
>
>
>
> Hello everyone,
>
> We are proud to announce the release of version 3.5.33 of the Java Service
> Wrapper.
> http://wrapper.tanukisoftware.org/doc/english/download.jsp
>
> This version includes several bug fixes and improvements. You can review
> the release notes for a full list of changes.
> http://wrapper.tanukisoftware.org/doc/english/release-notes.html
>
> Please let us know if you have any questions about the release.
>
> Sincerely,
>
> Java Service Wrapper Team
> Tanuki Software, Ltd.
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

[Hana Wu <Ha...@se...>]

The last version can support, right?

From: Maxime [mailto:ma...@ta...]
Sent: Tuesday, 29 August 2017 4:14 p.m.
To: wra...@li...
Subject: Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hana
Thank you for your email.

The 32-bit version of the Wrapper won't work with a 64-bit JVM. You will need to use the 64-bit version instead.
You may download and try it on the download page of the Java Service Wrapper website.

https://wrapper.tanukisoftware.com/doc/english/download.jsp
Best Regards,
Maxime

On Tue, Aug 29, 2017 at 4:41 PM, Hana Wu <Ha...@se...<mailto:Ha...@se...>> wrote:
Hi Maxime,

Thanks, For 3.5.33 version, Does 32-bit community support 64-bit windows VM?

Thanks,
Hana

From: Maxime [mailto:ma...@ta...<mailto:ma...@ta...>]
Sent: Wednesday, 26 July 2017 10:31 a.m.
To: wra...@li...<mailto:wra...@li...>
Subject: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hello everyone,

We are proud to announce the release of version 3.5.33 of the Java Service Wrapper.
http://wrapper.tanukisoftware.org/doc/english/download.jsp

This version includes several bug fixes and improvements. You can review the release notes for a full list of changes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let us know if you have any questions about the release.

Sincerely,

Java Service Wrapper Team
Tanuki Software, Ltd.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Wrapper-user mailing list
Wra...@li...<mailto:Wra...@li...>
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

[Maxime <ma...@ta...>]

Hana

Thank you for your email.

The 32-bit version of the Wrapper won't work with a 64-bit JVM. You will
need to use the 64-bit version instead.

You may download and try it on the download page of the Java Service
Wrapper website.

https://wrapper.tanukisoftware.com/doc/english/download.jsp

Best Regards,

Maxime

On Tue, Aug 29, 2017 at 4:41 PM, Hana Wu <Ha...@se...> wrote:

> Hi Maxime,
>
>
>
> Thanks, For 3.5.33 version, Does 32-bit community support 64-bit windows
> VM?
>
>
>
> Thanks,
>
> Hana
>
>
>
> *From:* Maxime [mailto:ma...@ta...]
> *Sent:* Wednesday, 26 July 2017 10:31 a.m.
> *To:* wra...@li...
> *Subject:* [Wrapper-user] Java Service Wrapper 3.5.33 released!
>
>
>
> Hello everyone,
>
> We are proud to announce the release of version 3.5.33 of the Java Service
> Wrapper.
> http://wrapper.tanukisoftware.org/doc/english/download.jsp
>
> This version includes several bug fixes and improvements. You can review
> the release notes for a full list of changes.
> http://wrapper.tanukisoftware.org/doc/english/release-notes.html
>
> Please let us know if you have any questions about the release.
>
> Sincerely,
>
> Java Service Wrapper Team
> Tanuki Software, Ltd.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java Service Wrapper 3.5.33 released!

[Hana Wu <Ha...@se...>]

Hi Maxime,

Thanks, For 3.5.33 version, Does 32-bit community support 64-bit windows VM?

Thanks,
Hana

From: Maxime [mailto:ma...@ta...]
Sent: Wednesday, 26 July 2017 10:31 a.m.
To: wra...@li...
Subject: [Wrapper-user] Java Service Wrapper 3.5.33 released!

Hello everyone,

We are proud to announce the release of version 3.5.33 of the Java Service Wrapper.
http://wrapper.tanukisoftware.org/doc/english/download.jsp

This version includes several bug fixes and improvements. You can review the release notes for a full list of changes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let us know if you have any questions about the release.

Sincerely,

Java Service Wrapper Team
Tanuki Software, Ltd.

Re: [Wrapper-user] Java service crashed after 5 hours

[Hana Wu <Ha...@se...>]

Hi Team,

Thanks for your feedback, I set the ‘wrapper.debug’ to true and running one month. It works well, but today it crashed again, the details log in attachment. The service be restarted at 18:00 everyday.  You can see the log,

Service be restarted 10:17:18, and the new file coming in at 10:17:59, it caught. Then
Service be restarted 18:00:00, and the new file coming in at 19:29:00, It did not catch it.

Could you help check?

Thanks so much,
Hana

From: Maxime [mailto:ma...@ta...]
Sent: Monday, 24 July 2017 12:26 p.m.
To: wra...@li...
Subject: Re: [Wrapper-user] Java service crashed after 5 hours

Hana

Thank you for your email.

Could you please run the Wrapper in debug mode and send us the log file so that we can see more outputs just before the Wrapper stops? To execute in debug mode, just set wrapper.debug=TRUE and make sure the property is not commented, then relaunch the Wrapper.

Note that in your configuration you have set the wrapper.ntservice.recovery.* properties of the standard edition but they will be ignored because you are using the community edition. This should not cause the Wrapper to stop though.

Best Regards,

Maxime

2017-07-24 11:41 GMT+09:00 Hana Wu <Ha...@se...<mailto:Ha...@se...>>:
Hi Team,

Thanks for your help.

I used java service wrapper to running a jar file. My java application is for monitoring a folder if it has a new file coming in, the service can started and working well for several hours, after that, it doesn’t work, need restart service.

Below is the detailed information:



  *   The version of the Wrapper you are using. - Java Service Wrapper Community Edition 32-bit 3.5.32
The OS and version that you are running on. – Windows Server 2008 R2 Datacenter, 64 bit OS
  *   Your wrapper.conf file. – see attachment
  *   Your wrapper.log file. – see attachment

Thanks,
Hana

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Wrapper-user mailing list
Wra...@li...<mailto:Wra...@li...>
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] problem with java service wrapper

[Alexandre K. <ale...@ta...>]

Hello,

Thank you for your email.

As you could see the Wrapper works as expected by detecting the string
"java.lang.OutOfMemoryError" and restarting your application.
Unfortunately, in your case, there is a kind of false-positive action
triggered because of the following line:
- KEY(index=8 name=REMARK type=12 [VARCHAR] length=512 unsigned=false
blob=false desc=VARCHAR(512)) = java.lang.OutOfMemoryError: GC overhead
limit exceeded

To solve that kind of situation, you can create a filter to catch that line
and do nothing. A line can be filtered only once, so the Wrapper will not
apply any other filters.

For example:
wrapper.filter.trigger.1=KEY(index=
wrapper.filter.action.1=NONE

wrapper.filter.trigger.5=java.lang.OutOfMemoryError
wrapper.filter.action.5=RESTART
wrapper.filter.message.5=Replicator ran out of memory, restarting

Now the line will be filtered by the filter #1 and your application will
not restart.

I hope this will help you solve your issue.

Please let me know if you have any other questions.

Regards,
Alexandre Klein


Alexandre Klein
Tanuki Software, Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

On Fri, Aug 18, 2017 at 6:29 PM, yeasxy <ye...@ye...> wrote:

> Hello:
>    I encountered a problem when used the java service wrapper , I hope you
> can help me, thank you very much.
>    Service wrapper is used by Tungsten Replicator ,a MYSQL replication
> engine. At wrapper.conf, I set up JVM to restart in case of
> "java.lang.OutOfMemoryError". But when the SQL column contains the field
> "java.lang.OutOfMemoryError", the Java Service Wrapper will *captures it
> and think it's an exception, and restart JVM*.
>    It make me vary upset because I don't know how to resolve it. So could
> you help me to have a check?
>
>    Here is some information with my environment:
> *Wrapper Version* :Java Service Wrapper Community Edition 64-bit 3.5.17
> *The OS and version*: 36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
> *wrapper.conf* :  Please check the attachment
> *wrapper.log file* ： Please check the attachment
>
> Forgive my poor English
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] problem with java service wrapper

[yeasxy <ye...@ye...>]

Hello:
   I encountered a problem when used the java service wrapper , I hope you can help me, thank you very much.
   Service wrapper is used by Tungsten Replicator ,a MYSQL replication engine. At wrapper.conf, I set up JVM to restart in case of "java.lang.OutOfMemoryError". But when the SQL column contains the field "java.lang.OutOfMemoryError", the Java Service Wrapper will captures it and think it's an exception, and restart JVM.
   It make me vary upset because I don't know how to resolve it. So could you help me to have a check?


   Here is some information with my environment:
Wrapper Version :Java Service Wrapper Community Edition 64-bit 3.5.17
The OS and version: 36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
wrapper.conf :  Please check the attachment
wrapper.log file ： Please check the attachment


Forgive my poor English

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

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

Abhilash,
Please see this page:
https://wrapper.tanukisoftware.com/doc/english/howto-upgrade.html

It is also very important that you update the wrapper.jar and also the bat
or sh scripts that you are using.

Let me know if you run into any issues.

Cheers,
Leif

On Thu, Jul 27, 2017 at 7:12 AM, Abhilash <abh...@gm...> wrote:

> Hi Lief,
>
> Is it enough by updating wrapper.dll and wrapper.jar in lib folder to
> upgrade the version?
>
>
>
> --
> View this message in context: http://java-service-wrapper.
> 996253.n3.nabble.com/Very-Noisy-Logs-Previous-control-code-tp272p3409.html
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>

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

[Abhilash <abh...@gm...>]

Hi Lief,

Is it enough by updating wrapper.dll and wrapper.jar in lib folder to
upgrade the version?



--
View this message in context: http://java-service-wrapper.996253.n3.nabble.com/Very-Noisy-Logs-Previous-control-code-tp272p3409.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] DEP / ASLR on Windows x86 binaries

[Maxime <ma...@ta...>]

Hello

A few months ago, you pointed out that the Wrapper doesn't specify it is DEP
& ASLR compatible.
The version 3.5.33 of the Wrapper has just been released and enables both
DEP & ASLR for Windows. Note that DEP is enabled through a dynamic call to
SetProcessDEPPolicy of the NX API. This was done to enable DEP on Windows
XP SP3 as well. ASLR is specified via the '/DYNAMICBASE' link option.

There is no change regarding DEP  when using the 64-bit version of the
Wrapper because Windows automatically enables DEP for 64-bit processes.

You may have a look at the release notes for a full list of changes made in
3.5.33:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let me know if you have any questions.

Best Regards,

Maxime

2017-02-23 12:54 GMT+09:00 yi-jing chou <yij...@gm...>:

> Hi Maxime,
>
> Thanks for your response.
>
> Do you have any schedule to release the build to enable ASLR and DEP/NX?
>
> For ASLR and DEP/NX in Windows x86, add "/NXCOMPAT" and "/DYNAMICBASE"
> into compile options can enable them.
> I understand your consideration about to support different platforms, but
> for Windows x86 that is simple to add the compile options.
> Could you please consider to release the build which ASLR and DEP/NX are
> enabled for Windows x86 first?
>
> Thanks.
>
> Best regards,
> Gino
>
> 2017-01-12 16:59 GMT+08:00 Maxime <ma...@ta...>:
>
>> Hello
>>
>> Thank you for your email.
>>
>> The Wrapper is indeed not compiled with the ASLR and DEP/NX compile flags
>> in its current version.
>> We will investigate about the possible implications this may have on the
>> different platforms we support, and consider adding these protections on a
>> future release.
>>
>> Best Regards,
>>
>> Maxime
>>
>>
>> On Wed, Jan 11, 2017 at 4:08 PM, yi-jing chou <yij...@gm...>
>> wrote:
>>
>>> Hi,
>>>
>>> I find the wrapper.exe and wrapper.dll for Windows x86 doesn't enable
>>> DEP(Data Execution Prevention) and ASLR(Address space layout randomization).
>>> It is a security risk and some malicious code can attack the program if
>>> it doesn't enable DEP / ASLR.
>>>
>>> Do you have plan to enhance it?
>>>
>>>
>>> Thank you
>>> Gino Chou
>>>
>>>
>>> DEP / ASLR on Windows x86 binaries
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Java Service Wrapper 3.5.33 released!

[Maxime <ma...@ta...>]

Hello everyone,

We are proud to announce the release of version 3.5.33 of the Java Service
Wrapper.
http://wrapper.tanukisoftware.org/doc/english/download.jsp

This version includes several bug fixes and improvements. You can review
the release notes for a full list of changes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let us know if you have any questions about the release.

Sincerely,

Java Service Wrapper Team
Tanuki Software, Ltd.

Re: [Wrapper-user] Java 9 support

[Alexandre K. <ale...@ta...>]

Tom,

After doing more tests with Java 9, we discovered that the Wrapper will
crash if the "wrapper.lang" property is set to something different than
en_US.

For example, the following will create an EXCEPTION_ACCESS_VIOLATION:
wrapper.lang=de_DE
wrapper.lang=ja_JP

We will investigate on the issue.

Regards,
Alexandre Klein

Alexandre Klein
Tanuki Software, Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

On Tue, Jul 4, 2017 at 6:45 PM, Thomas Ibbotson <
Tho...@ma...> wrote:

> Hi Alexandre,
>
>
>
> That’s great, thanks very much for going out of your way to test this.
>
>
>
> Tom
>
>
>
> *From:* Alexandre Klein [mailto:ale...@ta...]
> *Sent:* Tuesday, July 04, 2017 9:32 AM
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] Java 9 support
>
>
>
> Hi Tom,
>
> I downloaded Java 9+176 and ran the Wrapper (wrapper-windows-x86-64-3.5.32-pro)
> without any problem.
>
> Please note Java 9+176 is a preview version. The final version will be
> released later. I'm optimistic that the Wrapper will be compatible with the
> final version of Java 9.
>
> Regards,
>
> Alexandre Klein
>
>
> Alexandre Klein
>
> Tanuki Software, Ltd.
>
> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>
> Tokyo 134-0088 Japan
>
> Tel: +81-3-3878-3211 <+81%203-3878-3211>
>
> Fax: +81-3-3878-0313 <+81%203-3878-0313>
>
> http://www.tanukisoftware.com
>
>
>
> On Fri, Jun 30, 2017 at 11:51 PM, Thomas Ibbotson <
> Tho...@ma...> wrote:
>
> Hi all,
>
>
>
> Can anyone confirm if the Java Service Wrapper currently supports Java 9,
> or if it is planned for a future release?
>
>
>
> Thanks,
>
> Tom
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java service crashed after 5 hours

[Maxime <ma...@ta...>]

Hana

Thank you for your email.

Could you please run the Wrapper in debug mode and send us the log file so
that we can see more outputs just before the Wrapper stops? To execute in
debug mode, just set wrapper.debug=TRUE and make sure the property is not
commented, then relaunch the Wrapper.

Note that in your configuration you have set the
wrapper.ntservice.recovery.* properties of the standard edition but they
will be ignored because you are using the community edition. This should
not cause the Wrapper to stop though.

Best Regards,

Maxime

2017-07-24 11:41 GMT+09:00 Hana Wu <Ha...@se...>:

> Hi Team,
>
>
>
> Thanks for your help.
>
>
>
> I used java service wrapper to running a jar file. My java application is
> for monitoring a folder if it has a new file coming in, the service can
> started and working well for several hours, after that, it doesn’t work,
> need restart service.
>
>
>
> Below is the detailed information:
>
>
>
>
>
>    - The version of the Wrapper you are using. - *Java Service Wrapper
>    Community Edition 32-bit 3.5.32*
>    The OS and version that you are running on. – *Windows Server 2008 R2
>    Datacenter, 64 bit OS*
>    - Your wrapper.conf file. – see attachment
>    - Your wrapper.log file. – see attachment
>
>
>
> Thanks,
>
> Hana
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Java service crashed after 5 hours

[Hana Wu <Ha...@se...>]

Hi Team,

Thanks for your help.

I used java service wrapper to running a jar file. My java application is for monitoring a folder if it has a new file coming in, the service can started and working well for several hours, after that, it doesn't work, need restart service.

Below is the detailed information:



  *   The version of the Wrapper you are using. - Java Service Wrapper Community Edition 32-bit 3.5.32
The OS and version that you are running on. - Windows Server 2008 R2 Datacenter, 64 bit OS
  *   Your wrapper.conf file. - see attachment
  *   Your wrapper.log file. - see attachment

Thanks,
Hana