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

Re: [Wrapper-user] java application is failing to start on HP-UX

[nehamunipalli MS <neh...@gm...>]

Hi,
The wrapper.logfile.loglevel was set to INFO. Will check with
wrapper.logfile.loglevel set to DEBUG and get back to you.

Thanks and Regards,
Prasanna


On 9/18/09, Christian Mueller <chr...@ta...>
wrote:
>
> Hi Prasanna,
>
> If you set the log level for the wrapper to debug you should be able to see
> the source of the signal that caused the wrapper to stop.
>
> The relevant information would look like this:
>
> 2009/09/18 16:29:10 | wrapper  | Signal trapped.  Details:
> 2009/09/18 16:29:10 | wrapper  |   signal number=15 (SIGTERM),
> source="kill, sigsend or raise"
> 2009/09/18 16:29:10 | wrapper  |   signal generated by PID: 24503 (Session
> PID: 24503), UID: 1000 (christian)
> 2009/09/18 16:29:10 | wrapper  | TERM trapped.  Shutting down.
> 2009/09/18 16:29:10 | wrapper  | wrapperStopProcess(0) called.
> 2009/09/18 16:29:10 | wrapper  | Sending stop signal to JVM
> 2009/09/18 16:29:10 | wrapper  | Enqueue Event 'jvm_stop'
> 2009/09/18 16:29:10 | wrapperp | send a packet STOP : NULL
>
> if you can't find this in your logfile you might have to set the log level
> to debug in the wrapper.conf file:
> "wrapper.logfile.loglevel=DEBUG"
>
> could you send us over the debug log file so i may have a look at it?
>
> Best regards,
> Christian Mueller
> Tanuki Software, Ltd.
>
>
>  On Fri, Sep 18, 2009 at 3:33 PM, nehamunipalli MS <
> neh...@gm...> wrote:
>
>> Hi,
>> I am not able to reproduce this problem as this is happening on one of the
>> customer's system. To be able to understand where the SIGTERM is coming from
>> i asked the customer to enable debugging and try starting the application
>> again with the hope that I would be getting more information from the logs,
>> as per your suggestion. However, I don't get any information from the logs.
>>
>> Am i missing out something? As per the mail enabling the debug mode should
>> be giving the details of which process is sending the SIGTERM. I am not
>> finding this information in the log.
>>
>> Thanks and Regards,
>> Prasanna
>>
>>
>>   On 9/18/09, Tanuki Software Support <su...@ta...> wrote:
>>
>>>  Prasanna,
>>> The SIGKILL that you saw in the log was sent by the Wrapper to
>>> forcibly kill the the Java process after it did not shutdown within
>>> the expected amount of time.  The question is where the SIGTERM that
>>> initiated the Wrapper to start its shutdown came from.
>>>
>>> Were you able to reproduce this problem?
>>>
>>> Sincerely,
>>> Leif Mortenson
>>> Tanuki Software, Ltd.
>>>
>>> On Fri, Sep 18, 2009 at 2:38 PM, nehamunipalli MS
>>> <neh...@gm...> wrote:
>>> > Hi,
>>> > I did enable debugging for the wrapper. However, i am not getting any
>>> log
>>> > messages about which process is sending the signal. From the previous
>>> logs
>>> > before enabling debug was enable there were log messages that there was
>>> a
>>> > SIGKILL. This time after enabling debugging I am not seeing even that
>>> > message. What I want to know if this is happening because the signal or
>>> due
>>> > to some other reason. Please let me know if there is any other way of
>>> doing
>>> > the investigation.
>>> >
>>> > This is happening on a HP-UX 11.11 host.
>>> >
>>> > Thanks,
>>> > Prasanna
>>> >
>>> >
>>> > On 9/7/09, Leif Mortenson <lei...@ta...> wrote:
>>> >>
>>> >> Nehamuni,
>>> >> The Wrapper and JVM appeared to have been working normally since
>>> >> August 27th.   The application shutdown was triggered by the Wrapper
>>> >> receiving a SIGTERM.
>>> >>
>>> >> This can happen if someone runs the wrapper script with the "stop"
>>> >> command, or if another process issued a SIGTERM.
>>> >>
>>> >> It is possible to see where the SIGTERM came from if you set the
>>> >> wrapper.debug=true property and then reproduce it.
>>> >>
>>> >> You can also tell the Wrapper to completely ignore SIGTERM signals
>>> >> using the following property:
>>> >>
>>> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
>>> >>
>>> >> I had a customer several years ago running Solaris and another process
>>> >> had a bug that was sending out SIGTERMS to the wrong processes.  This
>>> >> was sometimes causing the Wrapper to shutdown.  The above property
>>> >> will tell the Wrapper to ignore such signals.
>>> >>
>>> >> There is no way to get additional log information without reproducing
>>> the
>>> >> event.
>>> >>
>>> >> Sincerely,
>>> >> Leif Mortenson
>>> >> Tanuki Software, Ltd.
>>> >>
>>> >> On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<
>>> neh...@gm...>
>>> >> wrote:
>>> >> > Hi Chirstian,
>>> >> >  I am not sure about this issue as this is happening at a customer
>>> site.
>>> >> > Are
>>> >> > there other steps that I can follow to get more information on what
>>> is
>>> >> > happening like getting more logs about the problem?
>>> >> >
>>> >> >
>>> >> > On 9/7/09, Christian Mueller <
>>> chr...@ta...>
>>> >> > wrote:
>>> >> >>
>>> >> >> Hi,
>>> >> >>
>>> >> >> you installed the daemon on august 27th and the next time the
>>> daemon
>>> >> >> received a SIGTERM on September 3rd.
>>> >> >> did your daemon run for 6.5 days fine and suddenly terminate?
>>> >> >> In the log, the wrapper seems to behave normal. The wrapper process
>>> >> >> received a SIGTERM and therefore tries to shutdown the java
>>> process. as
>>> >> >> the
>>> >> >> jvm didn't finish after a 5sec timeout the wrapper terminates it
>>> with a
>>> >> >> SIGKILL signal.
>>> >> >> Do you have an idea what could the SIGTERM have caused?
>>> >> >>
>>> >> >> Sincerely,
>>> >> >> Christian Mueller
>>> >> >> Tanuki Software, Ltd.
>>> >> >>
>>> >> >>
>>> >> >> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS
>>> >> >> <neh...@gm...>
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> Our java application is failing to start. Following are the
>>> messages
>>> >> >>> getting logged.
>>> >> >>>
>>> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as
>>> Daemon
>>> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime
>>> Environment,
>>> >> >>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM
>>> >> >>> (build
>>> >> >>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>>> >> >>> http://wrapper.tanukisoftware.org
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki
>>> >> >>> Software,
>>> >> >>> Inc. All Rights Reserved.
>>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>>> >> >>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting
>>> down.
>>> >> >>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly
>>> while
>>> >> >>> stopping the application.
>>> >> >>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to
>>> >> >>> signal
>>> >> >>> SIGKILL (9).
>>> >> >>>
>>> >> >>> Please let me know what the problem is and how this can be
>>> resolved?
>>> >> >>> Is
>>> >> >>> this a known issue?
>>>
>>> --
>>> Leif Mortenson
>>> Tanuki Software, Ltd.
>>> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
>>> Tokyo 134-0088 Japan
>>> Tel/Fax: +81-3-3878-3211
>>> http://www.tanukisoftware.com
>>> lei...@ta...
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>>> now&#33;
>>> http://p.sf.net/sfu/devconf
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>> now&#33;
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] java application is failing to start on HP-UX

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

Hi Prasanna,

If you set the log level for the wrapper to debug you should be able to see
the source of the signal that caused the wrapper to stop.

The relevant information would look like this:

2009/09/18 16:29:10 | wrapper  | Signal trapped.  Details:
2009/09/18 16:29:10 | wrapper  |   signal number=15 (SIGTERM), source="kill,
sigsend or raise"
2009/09/18 16:29:10 | wrapper  |   signal generated by PID: 24503 (Session
PID: 24503), UID: 1000 (christian)
2009/09/18 16:29:10 | wrapper  | TERM trapped.  Shutting down.
2009/09/18 16:29:10 | wrapper  | wrapperStopProcess(0) called.
2009/09/18 16:29:10 | wrapper  | Sending stop signal to JVM
2009/09/18 16:29:10 | wrapper  | Enqueue Event 'jvm_stop'
2009/09/18 16:29:10 | wrapperp | send a packet STOP : NULL

if you can't find this in your logfile you might have to set the log level
to debug in the wrapper.conf file:
"wrapper.logfile.loglevel=DEBUG"

could you send us over the debug log file so i may have a look at it?

Best regards,
Christian Mueller
Tanuki Software, Ltd.


On Fri, Sep 18, 2009 at 3:33 PM, nehamunipalli MS
<neh...@gm...>wrote:

> Hi,
> I am not able to reproduce this problem as this is happening on one of the
> customer's system. To be able to understand where the SIGTERM is coming from
> i asked the customer to enable debugging and try starting the application
> again with the hope that I would be getting more information from the logs,
> as per your suggestion. However, I don't get any information from the logs.
>
> Am i missing out something? As per the mail enabling the debug mode should
> be giving the details of which process is sending the SIGTERM. I am not
> finding this information in the log.
>
> Thanks and Regards,
> Prasanna
>
>
> On 9/18/09, Tanuki Software Support <su...@ta...> wrote:
>
>> Prasanna,
>> The SIGKILL that you saw in the log was sent by the Wrapper to
>> forcibly kill the the Java process after it did not shutdown within
>> the expected amount of time.  The question is where the SIGTERM that
>> initiated the Wrapper to start its shutdown came from.
>>
>> Were you able to reproduce this problem?
>>
>> Sincerely,
>> Leif Mortenson
>> Tanuki Software, Ltd.
>>
>> On Fri, Sep 18, 2009 at 2:38 PM, nehamunipalli MS
>> <neh...@gm...> wrote:
>> > Hi,
>> > I did enable debugging for the wrapper. However, i am not getting any
>> log
>> > messages about which process is sending the signal. From the previous
>> logs
>> > before enabling debug was enable there were log messages that there was
>> a
>> > SIGKILL. This time after enabling debugging I am not seeing even that
>> > message. What I want to know if this is happening because the signal or
>> due
>> > to some other reason. Please let me know if there is any other way of
>> doing
>> > the investigation.
>> >
>> > This is happening on a HP-UX 11.11 host.
>> >
>> > Thanks,
>> > Prasanna
>> >
>> >
>> > On 9/7/09, Leif Mortenson <lei...@ta...> wrote:
>> >>
>> >> Nehamuni,
>> >> The Wrapper and JVM appeared to have been working normally since
>> >> August 27th.   The application shutdown was triggered by the Wrapper
>> >> receiving a SIGTERM.
>> >>
>> >> This can happen if someone runs the wrapper script with the "stop"
>> >> command, or if another process issued a SIGTERM.
>> >>
>> >> It is possible to see where the SIGTERM came from if you set the
>> >> wrapper.debug=true property and then reproduce it.
>> >>
>> >> You can also tell the Wrapper to completely ignore SIGTERM signals
>> >> using the following property:
>> >> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
>> >>
>> >> I had a customer several years ago running Solaris and another process
>> >> had a bug that was sending out SIGTERMS to the wrong processes.  This
>> >> was sometimes causing the Wrapper to shutdown.  The above property
>> >> will tell the Wrapper to ignore such signals.
>> >>
>> >> There is no way to get additional log information without reproducing
>> the
>> >> event.
>> >>
>> >> Sincerely,
>> >> Leif Mortenson
>> >> Tanuki Software, Ltd.
>> >>
>> >> On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<
>> neh...@gm...>
>> >> wrote:
>> >> > Hi Chirstian,
>> >> >  I am not sure about this issue as this is happening at a customer
>> site.
>> >> > Are
>> >> > there other steps that I can follow to get more information on what
>> is
>> >> > happening like getting more logs about the problem?
>> >> >
>> >> >
>> >> > On 9/7/09, Christian Mueller <chr...@ta...
>> >
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> you installed the daemon on august 27th and the next time the daemon
>> >> >> received a SIGTERM on September 3rd.
>> >> >> did your daemon run for 6.5 days fine and suddenly terminate?
>> >> >> In the log, the wrapper seems to behave normal. The wrapper process
>> >> >> received a SIGTERM and therefore tries to shutdown the java process.
>> as
>> >> >> the
>> >> >> jvm didn't finish after a 5sec timeout the wrapper terminates it
>> with a
>> >> >> SIGKILL signal.
>> >> >> Do you have an idea what could the SIGTERM have caused?
>> >> >>
>> >> >> Sincerely,
>> >> >> Christian Mueller
>> >> >> Tanuki Software, Ltd.
>> >> >>
>> >> >>
>> >> >> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS
>> >> >> <neh...@gm...>
>> >> >> wrote:
>> >> >>>
>> >> >>> Our java application is failing to start. Following are the
>> messages
>> >> >>> getting logged.
>> >> >>>
>> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as
>> Daemon
>> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime
>> Environment,
>> >> >>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM
>> >> >>> (build
>> >> >>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>> >> >>> http://wrapper.tanukisoftware.org
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki
>> >> >>> Software,
>> >> >>> Inc. All Rights Reserved.
>> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>> >> >>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting
>> down.
>> >> >>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly
>> while
>> >> >>> stopping the application.
>> >> >>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to
>> >> >>> signal
>> >> >>> SIGKILL (9).
>> >> >>>
>> >> >>> Please let me know what the problem is and how this can be
>> resolved?
>> >> >>> Is
>> >> >>> this a known issue?
>>
>> --
>> Leif Mortenson
>> Tanuki Software, Ltd.
>> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
>> Tokyo 134-0088 Japan
>> Tel/Fax: +81-3-3878-3211
>> http://www.tanukisoftware.com
>> lei...@ta...
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>> now&#33;
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] java application is failing to start on HP-UX

[nehamunipalli MS <neh...@gm...>]

Hi,
I am not able to reproduce this problem as this is happening on one of the
customer's system. To be able to understand where the SIGTERM is coming from
i asked the customer to enable debugging and try starting the application
again with the hope that I would be getting more information from the logs,
as per your suggestion. However, I don't get any information from the logs.

Am i missing out something? As per the mail enabling the debug mode should
be giving the details of which process is sending the SIGTERM. I am not
finding this information in the log.

Thanks and Regards,
Prasanna


On 9/18/09, Tanuki Software Support <su...@ta...> wrote:
>
> Prasanna,
> The SIGKILL that you saw in the log was sent by the Wrapper to
> forcibly kill the the Java process after it did not shutdown within
> the expected amount of time.  The question is where the SIGTERM that
> initiated the Wrapper to start its shutdown came from.
>
> Were you able to reproduce this problem?
>
> Sincerely,
> Leif Mortenson
> Tanuki Software, Ltd.
>
> On Fri, Sep 18, 2009 at 2:38 PM, nehamunipalli MS
> <neh...@gm...> wrote:
> > Hi,
> > I did enable debugging for the wrapper. However, i am not getting any log
> > messages about which process is sending the signal. From the previous
> logs
> > before enabling debug was enable there were log messages that there was a
> > SIGKILL. This time after enabling debugging I am not seeing even that
> > message. What I want to know if this is happening because the signal or
> due
> > to some other reason. Please let me know if there is any other way of
> doing
> > the investigation.
> >
> > This is happening on a HP-UX 11.11 host.
> >
> > Thanks,
> > Prasanna
> >
> >
> > On 9/7/09, Leif Mortenson <lei...@ta...> wrote:
> >>
> >> Nehamuni,
> >> The Wrapper and JVM appeared to have been working normally since
> >> August 27th.   The application shutdown was triggered by the Wrapper
> >> receiving a SIGTERM.
> >>
> >> This can happen if someone runs the wrapper script with the "stop"
> >> command, or if another process issued a SIGTERM.
> >>
> >> It is possible to see where the SIGTERM came from if you set the
> >> wrapper.debug=true property and then reproduce it.
> >>
> >> You can also tell the Wrapper to completely ignore SIGTERM signals
> >> using the following property:
> >> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
> >>
> >> I had a customer several years ago running Solaris and another process
> >> had a bug that was sending out SIGTERMS to the wrong processes.  This
> >> was sometimes causing the Wrapper to shutdown.  The above property
> >> will tell the Wrapper to ignore such signals.
> >>
> >> There is no way to get additional log information without reproducing
> the
> >> event.
> >>
> >> Sincerely,
> >> Leif Mortenson
> >> Tanuki Software, Ltd.
> >>
> >> On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<
> neh...@gm...>
> >> wrote:
> >> > Hi Chirstian,
> >> >  I am not sure about this issue as this is happening at a customer
> site.
> >> > Are
> >> > there other steps that I can follow to get more information on what is
> >> > happening like getting more logs about the problem?
> >> >
> >> >
> >> > On 9/7/09, Christian Mueller <chr...@ta...>
> >> > wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> you installed the daemon on august 27th and the next time the daemon
> >> >> received a SIGTERM on September 3rd.
> >> >> did your daemon run for 6.5 days fine and suddenly terminate?
> >> >> In the log, the wrapper seems to behave normal. The wrapper process
> >> >> received a SIGTERM and therefore tries to shutdown the java process.
> as
> >> >> the
> >> >> jvm didn't finish after a 5sec timeout the wrapper terminates it with
> a
> >> >> SIGKILL signal.
> >> >> Do you have an idea what could the SIGTERM have caused?
> >> >>
> >> >> Sincerely,
> >> >> Christian Mueller
> >> >> Tanuki Software, Ltd.
> >> >>
> >> >>
> >> >> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS
> >> >> <neh...@gm...>
> >> >> wrote:
> >> >>>
> >> >>> Our java application is failing to start. Following are the messages
> >> >>> getting logged.
> >> >>>
> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as
> Daemon
> >> >>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
> >> >>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM
> >> >>> (build
> >> >>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:40 |
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
> >> >>> http://wrapper.tanukisoftware.org
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki
> >> >>> Software,
> >> >>> Inc. All Rights Reserved.
> >> >>> INFO | jvm 1 | 2009/08/27 12:06:41 |
> >> >>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting
> down.
> >> >>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
> >> >>> stopping the application.
> >> >>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to
> >> >>> signal
> >> >>> SIGKILL (9).
> >> >>>
> >> >>> Please let me know what the problem is and how this can be resolved?
> >> >>> Is
> >> >>> this a known issue?
>
> --
> Leif Mortenson
> Tanuki Software, Ltd.
> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel/Fax: +81-3-3878-3211
> http://www.tanukisoftware.com
> lei...@ta...
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] java application is failing to start on HP-UX

[Tanuki S. S. <su...@ta...>]

Prasanna,
The SIGKILL that you saw in the log was sent by the Wrapper to
forcibly kill the the Java process after it did not shutdown within
the expected amount of time.  The question is where the SIGTERM that
initiated the Wrapper to start its shutdown came from.

Were you able to reproduce this problem?

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Fri, Sep 18, 2009 at 2:38 PM, nehamunipalli MS
<neh...@gm...> wrote:
> Hi,
> I did enable debugging for the wrapper. However, i am not getting any log
> messages about which process is sending the signal. From the previous logs
> before enabling debug was enable there were log messages that there was a
> SIGKILL. This time after enabling debugging I am not seeing even that
> message. What I want to know if this is happening because the signal or due
> to some other reason. Please let me know if there is any other way of doing
> the investigation.
>
> This is happening on a HP-UX 11.11 host.
>
> Thanks,
> Prasanna
>
>
> On 9/7/09, Leif Mortenson <lei...@ta...> wrote:
>>
>> Nehamuni,
>> The Wrapper and JVM appeared to have been working normally since
>> August 27th.   The application shutdown was triggered by the Wrapper
>> receiving a SIGTERM.
>>
>> This can happen if someone runs the wrapper script with the "stop"
>> command, or if another process issued a SIGTERM.
>>
>> It is possible to see where the SIGTERM came from if you set the
>> wrapper.debug=true property and then reproduce it.
>>
>> You can also tell the Wrapper to completely ignore SIGTERM signals
>> using the following property:
>> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
>>
>> I had a customer several years ago running Solaris and another process
>> had a bug that was sending out SIGTERMS to the wrong processes.  This
>> was sometimes causing the Wrapper to shutdown.  The above property
>> will tell the Wrapper to ignore such signals.
>>
>> There is no way to get additional log information without reproducing the
>> event.
>>
>> Sincerely,
>> Leif Mortenson
>> Tanuki Software, Ltd.
>>
>> On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<neh...@gm...>
>> wrote:
>> > Hi Chirstian,
>> >  I am not sure about this issue as this is happening at a customer site.
>> > Are
>> > there other steps that I can follow to get more information on what is
>> > happening like getting more logs about the problem?
>> >
>> >
>> > On 9/7/09, Christian Mueller <chr...@ta...>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> you installed the daemon on august 27th and the next time the daemon
>> >> received a SIGTERM on September 3rd.
>> >> did your daemon run for 6.5 days fine and suddenly terminate?
>> >> In the log, the wrapper seems to behave normal. The wrapper process
>> >> received a SIGTERM and therefore tries to shutdown the java process. as
>> >> the
>> >> jvm didn't finish after a 5sec timeout the wrapper terminates it with a
>> >> SIGKILL signal.
>> >> Do you have an idea what could the SIGTERM have caused?
>> >>
>> >> Sincerely,
>> >> Christian Mueller
>> >> Tanuki Software, Ltd.
>> >>
>> >>
>> >> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS
>> >> <neh...@gm...>
>> >> wrote:
>> >>>
>> >>> Our java application is failing to start. Following are the messages
>> >>> getting logged.
>> >>>
>> >>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
>> >>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
>> >>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM
>> >>> (build
>> >>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>> >>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>> >>> http://wrapper.tanukisoftware.org
>> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki
>> >>> Software,
>> >>> Inc. All Rights Reserved.
>> >>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>> >>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
>> >>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
>> >>> stopping the application.
>> >>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to
>> >>> signal
>> >>> SIGKILL (9).
>> >>>
>> >>> Please let me know what the problem is and how this can be resolved?
>> >>> Is
>> >>> this a known issue?

-- 
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel/Fax: +81-3-3878-3211
http://www.tanukisoftware.com
lei...@ta...

Re: [Wrapper-user] java application is failing to start on HP-UX

[nehamunipalli MS <neh...@gm...>]

Hi,
I did enable debugging for the wrapper. However, i am not getting any log
messages about which process is sending the signal. From the previous logs
before enabling debug was enable there were log messages that there was a
SIGKILL. This time after enabling debugging I am not seeing even that
message. What I want to know if this is happening because the signal or due
to some other reason. Please let me know if there is any other way of doing
the investigation.

This is happening on a HP-UX 11.11 host.

Thanks,
Prasanna


On 9/7/09, Leif Mortenson <lei...@ta...> wrote:
>
> Nehamuni,
> The Wrapper and JVM appeared to have been working normally since
> August 27th.   The application shutdown was triggered by the Wrapper
> receiving a SIGTERM.
>
> This can happen if someone runs the wrapper script with the "stop"
> command, or if another process issued a SIGTERM.
>
> It is possible to see where the SIGTERM came from if you set the
> wrapper.debug=true property and then reproduce it.
>
> You can also tell the Wrapper to completely ignore SIGTERM signals
> using the following property:
> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
>
> I had a customer several years ago running Solaris and another process
> had a bug that was sending out SIGTERMS to the wrong processes.  This
> was sometimes causing the Wrapper to shutdown.  The above property
> will tell the Wrapper to ignore such signals.
>
> There is no way to get additional log information without reproducing the
> event.
>
> Sincerely,
> Leif Mortenson
> Tanuki Software, Ltd.
>
> On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<neh...@gm...>
> wrote:
> > Hi Chirstian,
> >  I am not sure about this issue as this is happening at a customer site.
> Are
> > there other steps that I can follow to get more information on what is
> > happening like getting more logs about the problem?
> >
> >
> > On 9/7/09, Christian Mueller <chr...@ta...>
> wrote:
> >>
> >> Hi,
> >>
> >> you installed the daemon on august 27th and the next time the daemon
> >> received a SIGTERM on September 3rd.
> >> did your daemon run for 6.5 days fine and suddenly terminate?
> >> In the log, the wrapper seems to behave normal. The wrapper process
> >> received a SIGTERM and therefore tries to shutdown the java process. as
> the
> >> jvm didn't finish after a 5sec timeout the wrapper terminates it with a
> >> SIGKILL signal.
> >> Do you have an idea what could the SIGTERM have caused?
> >>
> >> Sincerely,
> >> Christian Mueller
> >> Tanuki Software, Ltd.
> >>
> >>
> >> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS <
> neh...@gm...>
> >> wrote:
> >>>
> >>> Our java application is failing to start. Following are the messages
> >>> getting logged.
> >>>
> >>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
> >>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
> >>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
> >>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
> >>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
> >>> INFO | jvm 1 | 2009/08/27 12:06:40 |
> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
> >>> http://wrapper.tanukisoftware.org
> >>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki
> Software,
> >>> Inc. All Rights Reserved.
> >>> INFO | jvm 1 | 2009/08/27 12:06:41 |
> >>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
> >>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
> >>> stopping the application.
> >>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to
> signal
> >>> SIGKILL (9).
> >>>
> >>> Please let me know what the problem is and how this can be resolved? Is
> >>> this a known issue?
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] java application is failing to start on HP-UX

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

Nehamuni,
The Wrapper and JVM appeared to have been working normally since
August 27th.   The application shutdown was triggered by the Wrapper
receiving a SIGTERM.

This can happen if someone runs the wrapper script with the "stop"
command, or if another process issued a SIGTERM.

It is possible to see where the SIGTERM came from if you set the
wrapper.debug=true property and then reproduce it.

You can also tell the Wrapper to completely ignore SIGTERM signals
using the following property:
http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html

I had a customer several years ago running Solaris and another process
had a bug that was sending out SIGTERMS to the wrong processes.  This
was sometimes causing the Wrapper to shutdown.  The above property
will tell the Wrapper to ignore such signals.

There is no way to get additional log information without reproducing the event.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<neh...@gm...> wrote:
> Hi Chirstian,
>  I am not sure about this issue as this is happening at a customer site. Are
> there other steps that I can follow to get more information on what is
> happening like getting more logs about the problem?
>
>
> On 9/7/09, Christian Mueller <chr...@ta...> wrote:
>>
>> Hi,
>>
>> you installed the daemon on august 27th and the next time the daemon
>> received a SIGTERM on September 3rd.
>> did your daemon run for 6.5 days fine and suddenly terminate?
>> In the log, the wrapper seems to behave normal. The wrapper process
>> received a SIGTERM and therefore tries to shutdown the java process. as the
>> jvm didn't finish after a 5sec timeout the wrapper terminates it with a
>> SIGKILL signal.
>> Do you have an idea what could the SIGTERM have caused?
>>
>> Sincerely,
>> Christian Mueller
>> Tanuki Software, Ltd.
>>
>>
>> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS <neh...@gm...>
>> wrote:
>>>
>>> Our java application is failing to start. Following are the messages
>>> getting logged.
>>>
>>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
>>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
>>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
>>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>>> http://wrapper.tanukisoftware.org
>>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki Software,
>>> Inc. All Rights Reserved.
>>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
>>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
>>> stopping the application.
>>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to signal
>>> SIGKILL (9).
>>>
>>> Please let me know what the problem is and how this can be resolved? Is
>>> this a known issue?

Re: [Wrapper-user] java application is failing to start on HP-UX

[nehamunipalli MS <neh...@gm...>]

Hi Chirstian,
 I am not sure about this issue as this is happening at a customer site. Are
there other steps that I can follow to get more information on what is
happening like getting more logs about the problem?


On 9/7/09, Christian Mueller <chr...@ta...> wrote:
>
> Hi,
>
> you installed the daemon on august 27th and the next time the daemon
> received a SIGTERM on September 3rd.
> did your daemon run for 6.5 days fine and suddenly terminate?
> In the log, the wrapper seems to behave normal. The wrapper process
> received a SIGTERM and therefore tries to shutdown the java process. as the
> jvm didn't finish after a 5sec timeout the wrapper terminates it with a
> SIGKILL signal.
> Do you have an idea what could the SIGTERM have caused?
>
> Sincerely,
> Christian Mueller
> Tanuki Software, Ltd.
>
>
>  On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS <neh...@gm...
> > wrote:
>
>>  Our java application is failing to start. Following are the messages
>> getting logged.
>>
>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki Software,
>> Inc. All Rights Reserved.
>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
>> stopping the application.
>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to signal
>> SIGKILL (9).
>>
>> Please let me know what the problem is and how this can be resolved? Is
>> this a known issue?
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] java application is failing to start on HP-UX

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

Hi,

you installed the daemon on august 27th and the next time the daemon
received a SIGTERM on September 3rd.
did your daemon run for 6.5 days fine and suddenly terminate?
In the log, the wrapper seems to behave normal. The wrapper process received
a SIGTERM and therefore tries to shutdown the java process. as the jvm
didn't finish after a 5sec timeout the wrapper terminates it with a SIGKILL
signal.
Do you have an idea what could the SIGTERM have caused?

Sincerely,
Christian Mueller
Tanuki Software, Ltd.


On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS <neh...@gm...>wrote:

> Our java application is failing to start. Following are the messages
> getting logged.
>
> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
> INFO | jvm 1 | 2009/08/27 12:06:40 |
> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
> http://wrapper.tanukisoftware.org
> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki Software,
> Inc. All Rights Reserved.
> INFO | jvm 1 | 2009/08/27 12:06:41 |
> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
> stopping the application.
> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to signal
> SIGKILL (9).
>
> Please let me know what the problem is and how this can be resolved? Is
> this a known issue?
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] java application is failing to start on HP-UX

[nehamunipalli MS <neh...@gm...>]

Our java application is failing to start. Following are the messages getting
logged.

STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
INFO | jvm 1 | 2009/08/27 12:06:40 |
INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki Software,
Inc. All Rights Reserved.
INFO | jvm 1 | 2009/08/27 12:06:41 |
STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
stopping the application.
STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to signal
SIGKILL (9).

Please let me know what the problem is and how this can be resolved? Is this
a known issue?

Re: [Wrapper-user] Java Service Wrapper 3.3.6 released

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

Ian,
Thank you for reporting this along with the great description.  We
will run some tests and get this fixed for the next release.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Thu, Sep 3, 2009 at 12:41 AM, <IKo...@ax...> wrote:
> Hello,
> In regards to the enhancement where you added the ability to change the timezone, I ran into an issue. I am in the EST timezone (so GMT-5) but with Daylight Saving Time in effect here, we are really only GMT-4. When I set wrapper.timezone=GMT in the wrapper.config, the logs generated by our Java program (which always uses GMT) have the correct times in them, but the time in the wrapper log is off by 1 hour (i.e. in the program log I see 15:22:45 but in the wrapper log I see 16:22:45). If, however, I uncheck the box to automatically adjust for Daylight Saving Time both the times from our Java program and the times in the Wrapper log are the same.
> Our Java program gets the time by making a call to
> Java.util.TimeZone.getTimeZone("GMT") which appears to correctly adjust to add only 4 hours vs. the 5 normally. It seems that the calculation used for the Wrapper is strictly +5 hours regardless of Daylight Saving Time or not.
>
> Not really a big deal, but though I'd point this out.
>
> Thanks,
> Ian Koelliker
>
> -----Original Message-----
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: Sunday, August 30, 2009 11:43 PM
> To: Wrapper User List
> Subject: [Wrapper-user] Java Service Wrapper 3.3.6 released
>
> Hello all,
> We are proud to announce the release of version 3.3.6 of the Java
> Service Wrapper.
>
> New Features are:
> * We now have a Japanese version of our web site.  It is still
> undergoing some work but most of the main pages are ready.
> * The ability to set the timezone used by the Wrapper and its JVM to a
> value other than that of the system.  This can be very useful for
> distributed companies who wish to keep all their logs in sync.
> (Standard, Professional Edition)
> * Improved error messages to help resolve integration problems.
> * Make it possible to configure event messages in the logs
> (Professional Edition)
> * It is no longer necessary to specify classpaths, java parameters,
> etc. as sequential lists of properties.  This has been a much
> requested feature which will make it much easier to maintain the
> Wrapper configuration file.
> * Add the ability to invoke thread dumps automatically in response to
> certain JVM output.  Very useful in tracking down deadlocks, etc.
> * Make it possible to obfuscate the upgrade term in the license key
> files to avoid confusion with end users.
>
> There were also a few bug fixes and other minor features added so be
> sure to take a look at the full release notes:
> http://wrapper.tanukisoftware.org/doc/english/release-notes.html
>
> Version 3.3.6 is available on the usual download page:
> http://wrapper.tanukisoftware.org/doc/english/download.jsp
>
> Let me know if you have any questions getting upgraded.
>
> Cheers,
> Leif

Re: [Wrapper-user] Java Service Wrapper 3.3.6 released

[<IKo...@ax...>]

Hello,
In regards to the enhancement where you added the ability to change the timezone, I ran into an issue. I am in the EST timezone (so GMT-5) but with Daylight Saving Time in effect here, we are really only GMT-4. When I set wrapper.timezone=GMT in the wrapper.config, the logs generated by our Java program (which always uses GMT) have the correct times in them, but the time in the wrapper log is off by 1 hour (i.e. in the program log I see 15:22:45 but in the wrapper log I see 16:22:45). If, however, I uncheck the box to automatically adjust for Daylight Saving Time both the times from our Java program and the times in the Wrapper log are the same.
Our Java program gets the time by making a call to 
Java.util.TimeZone.getTimeZone("GMT") which appears to correctly adjust to add only 4 hours vs. the 5 normally. It seems that the calculation used for the Wrapper is strictly +5 hours regardless of Daylight Saving Time or not.

Not really a big deal, but though I'd point this out.

Thanks,
Ian Koelliker

-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...] 
Sent: Sunday, August 30, 2009 11:43 PM
To: Wrapper User List
Subject: [Wrapper-user] Java Service Wrapper 3.3.6 released

Hello all,
We are proud to announce the release of version 3.3.6 of the Java
Service Wrapper.

New Features are:
* We now have a Japanese version of our web site.  It is still
undergoing some work but most of the main pages are ready.
* The ability to set the timezone used by the Wrapper and its JVM to a
value other than that of the system.  This can be very useful for
distributed companies who wish to keep all their logs in sync.
(Standard, Professional Edition)
* Improved error messages to help resolve integration problems.
* Make it possible to configure event messages in the logs
(Professional Edition)
* It is no longer necessary to specify classpaths, java parameters,
etc. as sequential lists of properties.  This has been a much
requested feature which will make it much easier to maintain the
Wrapper configuration file.
* Add the ability to invoke thread dumps automatically in response to
certain JVM output.  Very useful in tracking down deadlocks, etc.
* Make it possible to obfuscate the upgrade term in the license key
files to avoid confusion with end users.

There were also a few bug fixes and other minor features added so be
sure to take a look at the full release notes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Version 3.3.6 is available on the usual download page:
http://wrapper.tanukisoftware.org/doc/english/download.jsp

Let me know if you have any questions getting upgraded.

Cheers,
Leif

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Java Service Wrapper 3.3.6 released

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

Hello all,
We are proud to announce the release of version 3.3.6 of the Java
Service Wrapper.

New Features are:
* We now have a Japanese version of our web site.  It is still
undergoing some work but most of the main pages are ready.
* The ability to set the timezone used by the Wrapper and its JVM to a
value other than that of the system.  This can be very useful for
distributed companies who wish to keep all their logs in sync.
(Standard, Professional Edition)
* Improved error messages to help resolve integration problems.
* Make it possible to configure event messages in the logs
(Professional Edition)
* It is no longer necessary to specify classpaths, java parameters,
etc. as sequential lists of properties.  This has been a much
requested feature which will make it much easier to maintain the
Wrapper configuration file.
* Add the ability to invoke thread dumps automatically in response to
certain JVM output.  Very useful in tracking down deadlocks, etc.
* Make it possible to obfuscate the upgrade term in the license key
files to avoid confusion with end users.

There were also a few bug fixes and other minor features added so be
sure to take a look at the full release notes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Version 3.3.6 is available on the usual download page:
http://wrapper.tanukisoftware.org/doc/english/download.jsp

Let me know if you have any questions getting upgraded.

Cheers,
Leif

Re: [Wrapper-user] Security bulletin for tanuki

[Chen, M. M. <min...@hp...>]

 

HI Leif,
Do you know if there is any security bulletin for tanuki, for both 32bit and 64bit? Or any security information that we should be aware of? Thanks.
Regards
Ming

Re: [Wrapper-user] Is JSW i18n compliant

[Pankaj A. <pan...@gm...>]

Hi Leif,

Thanks for the quick response.

My application is in Java and the java program is invoked through a batch
file. Thus I have used JSW to register this batch file as a service in
windows.

Now, in JSW, we have the wrapper.conf file which has the below property for
the service description:

wrapper.ntservice.description=
Now, I want to i18n my java application. And then localize it for Japanese.
If the app is localized for japanese, the above description should be in
japanese language.

So i want to know how to use the JSW to provide the english and japanese
service descriptions. Any way out for now?

Thanks
Pankaj
2009/8/25 Leif Mortenson <lei...@ta...>

> Pankaj,
> The Wrapper itself is not currently localized.  It is used with
> applications in a wide number of languages and things like logging all
> work fine on the native encodings of those systems.
>
> One of the projects that we have been working on for a while now is to
> fully localize the Wrapper.  We are not ready to announce a date, but
> it will be released before the end of the year.
>
> Exactly what i18n functionality are you looking for?  We will try to
> include them in our plans.
>
> Cheers,
> Leif
>
> On Tue, Aug 25, 2009 at 6:00 PM, Pankaj Agrawal<pan...@gm...>
> wrote:
> > Hi All,
> >
> > I am using JSW for registering a bat file as a windows service. I want to
> > know if JSW supports internalization (i18n) or not.
> >
> > Thanks
> >
> > Pankaj
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Is JSW i18n compliant

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

Pankaj,
The Wrapper itself is not currently localized.  It is used with
applications in a wide number of languages and things like logging all
work fine on the native encodings of those systems.

One of the projects that we have been working on for a while now is to
fully localize the Wrapper.  We are not ready to announce a date, but
it will be released before the end of the year.

Exactly what i18n functionality are you looking for?  We will try to
include them in our plans.

Cheers,
Leif

On Tue, Aug 25, 2009 at 6:00 PM, Pankaj Agrawal<pan...@gm...> wrote:
> Hi All,
>
> I am using JSW for registering a bat file as a windows service. I want to
> know if JSW supports internalization (i18n) or not.
>
> Thanks
>
> Pankaj

[Wrapper-user] Is JSW i18n compliant

[Pankaj A. <pan...@gm...>]

Hi All,

I am using JSW for registering a bat file as a windows service. I want to
know if JSW supports internalization (i18n) or not.

Thanks

Pankaj

Re: [Wrapper-user] jvm hung and high CPU usage with wrapper

[hhale21 <hh...@ya...>]

1) the jvm version is correct.
3) Could not find anything like this. 

>>Are you able to tell which thread in your application is eating all of the
CPU?
No application created threads.
It was a RMI thread in one case, but the application does not use RMI.

The thing is it is happening to 3 differnent servers on the same computer. 

Thanks for the reply.


-- 
View this message in context: http://www.nabble.com/jvm-hung-and-high-CPU-usage-with-wrapper-tp25046592p25085794.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] Using sudo causes JVM exit

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

Yes, turned out to be a strangely-broken JRE.

Thanks for the hints.

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


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

Re: [Wrapper-user] Using sudo causes JVM exit

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

> Most likely, this is an environment problem.   The way you have
> the wrapper.java.command property set, the Wrapper will attempt to
> locate the java binary on the system PATH and execute it.   When you
> sudo and become root, the defined PATH may not include the location of
> java.

I just got some success from doing that. I've got to go home now, but will 
play around tomorrow.

Thanks for the help!

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


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

Re: [Wrapper-user] Using sudo causes JVM exit

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

Jason,
Ok.  Most likely, this is an environment problem.   The way you have
the wrapper.java.command property set, the Wrapper will attempt to
locate the java binary on the system PATH and execute it.   When you
sudo and become root, the defined PATH may not include the location of
java.

As a quick test, please try the following in your wrapper.conf file
where the JAVA_HOME directory is set to the location on your system.
---
set.JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
wrapper.java.command=%JAVA_HOME%/bin/java
---

Please let me know how this works for you.
Cheers,
Leif

On Fri, Aug 21, 2009 at 12:14 AM, <Jas...@sc...> wrote:
>
>> In the mean time, could you please set the following property and then
>> show me the resulting log for both the sudo and non-sudo cases?
>
> No problem.
>
> nosudo:
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights
> Reserved.
> wrapper  |     http://wrapper.tanukisoftware.org
> wrapper  |
> wrapper  | Command[0] : java
> wrapper  | Command[1] : -Djava.library.path=../lib
> wrapper  | Command[2] : -classpath
> wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
> wrapper  | Command[4] : -Dwrapper.key=TYtj9XOnixArsbhQ
> wrapper  | Command[5] : -Dwrapper.port=32000
> wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
> wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
> wrapper  | Command[8] : -Dwrapper.pid=27438
> wrapper  | Command[9] : -Dwrapper.version=3.3.5
> wrapper  | Command[10] : -Dwrapper.native_library=wrapper
> wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
> wrapper  | Command[12] : -Dwrapper.jvmid=1
> wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
> wrapper  | Launching a JVM...
> jvm 1    | TestWrapper: Initializing...
> jvm 1    | WrapperManager: Initializing...
> jvm 1    | TestWrapper: start()
> jvm 1    | TestWrapper: ActionServer Enabled.
> jvm 1    | TestWrapper:   Telnet localhost 9999
> jvm 1    | TestWrapper:   Commands:
> jvm 1    | TestWrapper:     S: Shutdown
> jvm 1    | TestWrapper:     H: Expected Halt
> jvm 1    | TestWrapper:     R: Restart
> jvm 1    | TestWrapper:     D: Thread Dump
> jvm 1    | TestWrapper:     U: Unexpected Halt (Simulate crash)
> jvm 1    | TestWrapper:     V: Access Violation (Actual crash)
> jvm 1    | TestWrapper:     G: Make the JVM appear to be hung.
>
> sudo:
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights
> Reserved.
> wrapper  |     http://wrapper.tanukisoftware.org
> wrapper  |
> wrapper  | Command[0] : java
> wrapper  | Command[1] : -Djava.library.path=../lib
> wrapper  | Command[2] : -classpath
> wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
> wrapper  | Command[4] : -Dwrapper.key=092gHHqwSlwEKNm9
> wrapper  | Command[5] : -Dwrapper.port=32000
> wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
> wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
> wrapper  | Command[8] : -Dwrapper.pid=27371
> wrapper  | Command[9] : -Dwrapper.version=3.3.5
> wrapper  | Command[10] : -Dwrapper.native_library=wrapper
> wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
> wrapper  | Command[12] : -Dwrapper.jvmid=1
> wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
> wrapper  | Launching a JVM...
> wrapper  | JVM process is gone.jvm 1    | ]0;Test Wrapper Sample
> Applicationwrapper  | --> Wrapper Started as Console
> jvm 1    | wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
> jvm 1    | wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All
> Rights Reserved.
> jvm 1    | wrapper  |     http://wrapper.tanukisoftware.org
> jvm 1    | wrapper  |
> jvm 1    | wrapper  | Command[0] : java
> jvm 1    | wrapper  | Command[1] : -Djava.library.path=../lib
> jvm 1    | wrapper  | Command[2] : -classpath
> jvm 1    | wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
> jvm 1    | wrapper  | Command[4] : -Dwrapper.key=092gHHqwSlwEKNm9
> jvm 1    | wrapper  | Command[5] : -Dwrapper.port=32000
> jvm 1    | wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
> jvm 1    | wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
> jvm 1    | wrapper  | Command[8] : -Dwrapper.pid=27371
> jvm 1    | wrapper  | Command[9] : -Dwrapper.version=3.3.5
> jvm 1    | wrapper  | Command[10] : -Dwrapper.native_library=wrapper
> jvm 1    | wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
> jvm 1    | wrapper  | Command[12] : -Dwrapper.jvmid=1
> jvm 1    | wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
> jvm 1    | wrapper  | Launching a JVM...
> wrapper  | Unable to start JVM: Permission denied (13)
> wrapper  |
> wrapper  |
> ------------------------------------------------------------------------
> wrapper  | Advice:
> wrapper  | Usually when the Wrapper fails to start the JVM process, it is
> because
> wrapper  | of a problem with the value of the configured hava command.
>  Currently:
> wrapper  | wrapper.java.command=java
> wrapper  | Please make sure that the PATH or any other referenced
> environment
> wrapper  | variables are correctly defined for the current environment.
> wrapper  |
> ------------------------------------------------------------------------
> wrapper  |
> wrapper  | <-- Wrapper Stopped
>
> **********************************************************************
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify pos...@sc...
>
> This footnote also confirms that this email message has been checked for all
> known viruses.
>
> Sony Computer Entertainment Europe Limited
>
> Registered Office: 10 Great Marlborough Street, London W1F 7LP, United
> Kingdom
>
> Registered in England: 3277793
>
> **********************************************************************

Re: [Wrapper-user] Using sudo causes JVM exit

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

Hi Leif,

The formatting of that second log was a bit odd, here's another:

Running Test Wrapper Sample Application...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights 
Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
wrapper  | 
wrapper  | Command[0] : java
wrapper  | Command[1] : -Djava.library.path=../lib
wrapper  | Command[2] : -classpath
wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
wrapper  | Command[4] : -Dwrapper.key=pKet_XBurGD9AyMs
wrapper  | Command[5] : -Dwrapper.port=32000
wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[8] : -Dwrapper.pid=27776
wrapper  | Command[9] : -Dwrapper.version=3.3.5
wrapper  | Command[10] : -Dwrapper.native_library=wrapper
wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
wrapper  | Command[12] : -Dwrapper.jvmid=1
wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
wrapper  | Launching a JVM...
wrapper  | JVM process is gone.
wrapper  | Unable to start JVM: Permission denied (13)
wrapper  | 
wrapper  | 
------------------------------------------------------------------------
wrapper  | Advice:
wrapper  | Usually when the Wrapper fails to start the JVM process, it is 
because
wrapper  | of a problem with the value of the configured hava command. 
Currently:
wrapper  | wrapper.java.command=java
wrapper  | Please make sure that the PATH or any other referenced 
environment
wrapper  | variables are correctly defined for the current environment.
wrapper  | 
------------------------------------------------------------------------
wrapper  | 
wrapper  | <-- Wrapper Stopped

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

Re: [Wrapper-user] Using sudo causes JVM exit

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

> In the mean time, could you please set the following property and then 
show me the resulting log for both the sudo and non-sudo cases?

No problem.

nosudo:
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights 
Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
wrapper  | 
wrapper  | Command[0] : java
wrapper  | Command[1] : -Djava.library.path=../lib
wrapper  | Command[2] : -classpath
wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
wrapper  | Command[4] : -Dwrapper.key=TYtj9XOnixArsbhQ
wrapper  | Command[5] : -Dwrapper.port=32000
wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[8] : -Dwrapper.pid=27438
wrapper  | Command[9] : -Dwrapper.version=3.3.5
wrapper  | Command[10] : -Dwrapper.native_library=wrapper
wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
wrapper  | Command[12] : -Dwrapper.jvmid=1
wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
wrapper  | Launching a JVM...
jvm 1    | TestWrapper: Initializing...
jvm 1    | WrapperManager: Initializing...
jvm 1    | TestWrapper: start()
jvm 1    | TestWrapper: ActionServer Enabled. 
jvm 1    | TestWrapper:   Telnet localhost 9999
jvm 1    | TestWrapper:   Commands: 
jvm 1    | TestWrapper:     S: Shutdown
jvm 1    | TestWrapper:     H: Expected Halt
jvm 1    | TestWrapper:     R: Restart
jvm 1    | TestWrapper:     D: Thread Dump
jvm 1    | TestWrapper:     U: Unexpected Halt (Simulate crash)
jvm 1    | TestWrapper:     V: Access Violation (Actual crash)
jvm 1    | TestWrapper:     G: Make the JVM appear to be hung.

sudo:
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights 
Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
wrapper  | 
wrapper  | Command[0] : java
wrapper  | Command[1] : -Djava.library.path=../lib
wrapper  | Command[2] : -classpath
wrapper  | Command[3] : ../lib/wrappertest.jar:../lib/wrapper.jar
wrapper  | Command[4] : -Dwrapper.key=092gHHqwSlwEKNm9
wrapper  | Command[5] : -Dwrapper.port=32000
wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[8] : -Dwrapper.pid=27371
wrapper  | Command[9] : -Dwrapper.version=3.3.5
wrapper  | Command[10] : -Dwrapper.native_library=wrapper
wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
wrapper  | Command[12] : -Dwrapper.jvmid=1
wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
wrapper  | Launching a JVM...
wrapper  | JVM process is gone.jvm 1    | ]0;Test Wrapper Sample 
Applicationwrapper  | --> Wrapper Started as Console
jvm 1    | wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
jvm 1    | wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All 
Rights Reserved.
jvm 1    | wrapper  |     http://wrapper.tanukisoftware.org
jvm 1    | wrapper  | 
jvm 1    | wrapper  | Command[0] : java
jvm 1    | wrapper  | Command[1] : -Djava.library.path=../lib
jvm 1    | wrapper  | Command[2] : -classpath
jvm 1    | wrapper  | Command[3] : 
../lib/wrappertest.jar:../lib/wrapper.jar
jvm 1    | wrapper  | Command[4] : -Dwrapper.key=092gHHqwSlwEKNm9
jvm 1    | wrapper  | Command[5] : -Dwrapper.port=32000
jvm 1    | wrapper  | Command[6] : -Dwrapper.jvm.port.min=31000
jvm 1    | wrapper  | Command[7] : -Dwrapper.jvm.port.max=31999
jvm 1    | wrapper  | Command[8] : -Dwrapper.pid=27371
jvm 1    | wrapper  | Command[9] : -Dwrapper.version=3.3.5
jvm 1    | wrapper  | Command[10] : -Dwrapper.native_library=wrapper
jvm 1    | wrapper  | Command[11] : -Dwrapper.cpu.timeout=10
jvm 1    | wrapper  | Command[12] : -Dwrapper.jvmid=1
jvm 1    | wrapper  | Command[13] : org.tanukisoftware.wrapper.test.Main
jvm 1    | wrapper  | Launching a JVM...
wrapper  | Unable to start JVM: Permission denied (13)
wrapper  | 
wrapper  | 
------------------------------------------------------------------------
wrapper  | Advice:
wrapper  | Usually when the Wrapper fails to start the JVM process, it is 
because
wrapper  | of a problem with the value of the configured hava command. 
Currently:
wrapper  | wrapper.java.command=java
wrapper  | Please make sure that the PATH or any other referenced 
environment
wrapper  | variables are correctly defined for the current environment.
wrapper  | 
------------------------------------------------------------------------
wrapper  | 
wrapper  | <-- Wrapper Stopped


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

Re: [Wrapper-user] Using sudo causes JVM exit

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

Jason,
I will test this ou later tonight.  In the mean time, could you please  
set the following property and then show me the resulting log for both  
the sudo and non-sudo cases?
wrapper.java.command.loglevel=INFO

Thanks,
- Leif

On 2009/08/20, at 21:36, Jas...@sc... wrote:

>
> Hi,
>
> I've used the wrapper successfully for ages, but have recently run  
> into a problem on Linux 64 and OS X 64 (may not be specific to those  
> platforms though).
>
> I need to launch sudo'd, but on Cent OS 5 the JVM was exiting  
> instantly. Bizarrely, removing the sudo meant it booted correctly.
>
> I downloaded 3.3.5 but that didn't help. Finally, I used your  
> testwrapper script and found it exhibits the same problem:
>
> [jchown@centos5 wrapper-linux-x86-64-3.3.5]$ sudo bin/testwrapper  
> console
> Running Test Wrapper Sample Application...
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5
> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All  
> Rights Reserved.
> wrapper  |     http://wrapper.tanukisoftware.org
> wrapper  |
> wrapper  | Launching a JVM...
> wrapper  | JVM process is gone.
> wrapper  | Unable to start JVM: Permission denied (13)
> wrapper  |
> wrapper  |  
> --- 
> ---------------------------------------------------------------------
> wrapper  | Advice:
> wrapper  | Usually when the Wrapper fails to start the JVM process,  
> it is because
> wrapper  | of a problem with the value of the configured hava  
> command.  Currently:
> wrapper  | wrapper.java.command=java
> wrapper  | Please make sure that the PATH or any other referenced  
> environment
> wrapper  | variables are correctly defined for the current  
> environment.
> wrapper  |  
> --- 
> ---------------------------------------------------------------------
> wrapper  |
> wrapper  | <-- Wrapper Stopped
>
> 'sudo java -version' runs fine.
> 'bin/testwrapper console' runs fine.
>
> Anyone have an idea what's up?
>
>
> Jason Chown
> Sony Computer Entertainment Europe Limited
> http://eu.playstation.com
>
>
> **********************************************************************
>
> This email and any files transmitted with it are confidential and  
> intended solely for the use of the individual or entity to whom they  
> are addressed. If you have received this email in error please  
> notify pos...@sc...
>
> This footnote also confirms that this email message has been checked  
> for all known viruses.
>
> Sony Computer Entertainment Europe Limited
>
> Registered Office: 10 Great Marlborough Street, London W1F 7LP,  
> United Kingdom
>
> Registered in England: 3277793
>
> *********************************************************************

[Wrapper-user] Using sudo causes JVM exit

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

Hi,

I've used the wrapper successfully for ages, but have recently run into a 
problem on Linux 64 and OS X 64 (may not be specific to those platforms 
though).

I need to launch sudo'd, but on Cent OS 5 the JVM was exiting instantly. 
Bizarrely, removing the sudo meant it booted correctly. 

I downloaded 3.3.5 but that didn't help. Finally, I used your testwrapper 
script and found it exhibits the same problem:

[jchown@centos5 wrapper-linux-x86-64-3.3.5]$ sudo bin/testwrapper console 
Running Test Wrapper Sample Application... 
wrapper  | --> Wrapper Started as Console 
wrapper  | Java Service Wrapper Community Edition 64-bit 3.3.5 
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights 
Reserved. 
wrapper  |     http://wrapper.tanukisoftware.org 
wrapper  | 
wrapper  | Launching a JVM... 
wrapper  | JVM process is gone. 
wrapper  | Unable to start JVM: Permission denied (13) 
wrapper  | 
wrapper  | 
------------------------------------------------------------------------ 
wrapper  | Advice: 
wrapper  | Usually when the Wrapper fails to start the JVM process, it is 
because 
wrapper  | of a problem with the value of the configured hava command. 
Currently: 
wrapper  | wrapper.java.command=java 
wrapper  | Please make sure that the PATH or any other referenced 
environment 
wrapper  | variables are correctly defined for the current environment. 
wrapper  | 
------------------------------------------------------------------------ 
wrapper  | 
wrapper  | <-- Wrapper Stopped 

'sudo java -version' runs fine.
'bin/testwrapper console' runs fine.

Anyone have an idea what's up?


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



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

Re: [Wrapper-user] jvm hung and high CPU usage with wrapper

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

Hello,
My first guess here is a configuration problem of some sort.

1) When you enabled the wrapper.debug output, there should be a Java
command line displayed at the top of the log.    Could you please
verify that the Wrapper is launching the same JVM version when running
as a service, as a console, and when you run without the Wrapper?   A
fairly common problem is that users run the wrong JVM version because
the Wrapper locates Java on the system path by default.  The PATH is
not always defined the same for various users.
As you are only seeing some problems with the Wrapper, I think this
might be happening with you.

2) 3.2.3 is fairly old, so I think I am aware of most problems in that
version.  There are no problems that I am aware of that would be
isolated to single core machines and none that cause a large CPU
usage.  There have been some synchronization problems over the years
that showed up on multiple CPU systems, but not the other way around.

3) Another user had a problem s couple years ago where their
application was eating lots of CPU when run under the Wrapper.  It
turned out to be a problem in the user's code.   They had code like
this:

while (true) {
    try {
        doSomething();
        Thread.sleep(60000);
    } catch ( Throwable t ) {
        // ignore
    }
}

The doSomething code was throwing an exception due to a path reference
error and the sleep was being skipped.
Are you able to tell which thread in your application is eating all of the CPU?

Cheers,
Leif

On Thu, Aug 20, 2009 at 12:40 AM, hhale21<hh...@ya...> wrote:
>
> Hello,
>
> I am using JSW 3.2.3.  We are experiencing some odd behaviour of our servers
> on single CPU/core Windows XP/SP3 (32bit) computers.  I am looking for ways
> to try and troubleshoot this problem.
>
> There are 3 different servers running as windows services using the
> wrapper.exe.
> On a regular basis 1 or more of these servers is getting jvm hung messages
> and are being started.
> This seems only to occur on single core/CPU computers.  Have not observed
> this on multi core CPUs.  I have wrapper.debug=true in the conf files. I
> don't seen anything in the log files other that logging for the application
> stops completly for 30 secs (default wrapper ping value) before the jvm is
> restarted.
>
> I tried starting one of the servers using the wrapper.exe as regular process
> (as opposed to a service). The hang does not occur however one of the
> threads in the application is using almost 100% of the CPU constantly. I am
> using Process Explorer inspect the process.   JVM has not occurred when not
> run as service.
>
> When I run the server without the wrapper.exe,  I don't have the thread that
> uses 100% of the CPU and so far the server has run with out any issues.
>
> Just looking for some feedback on how to troubleshoot this problem.
>
> Thanks
> --