Re: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

There is a 100KB restriction on updates.  I’m sending the log in a zip.

Your mail to 'Wrapper-user' with the subject

    RE: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Message body is too big: 206993 bytes with a limit of 100 KB

Either the message will get posted to the list, or you will receive notification of the moderator's decision.  If you would like to cancel this posting, please visit the following URL:

    https://lists.sourceforge.net/lists/confirm/wrapper-user/2f3d726f66ced27237fcde0879a514eed9898257

From: Tu T. Nguyen
Sent: Monday, January 26, 2015 1:46 PM
To: 'wra...@li...'
Cc: Elaine M. Julius
Subject: RE: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

Hello Alexandre,

Sorry I should have included some details with my last email.

Attached is a log segment of one of the single seconds I mentioned.  You can see that its 854 lines of logging.

An interesting note is that there are 2 separate TIME  (there is only 1 date shown) stamps.  The first one (left most) shows the same time down to the second throughout.  But if you look at the 2nd time that follows, it spans  11:51:05,269 to 11:57:24,863.  This corresponds with the message

INFO   | wrapper  | 2015/01/12 11:57:24 | Wrapper Process has not received any CPU time for 347 seconds.  Extending timeouts.

Which is the roughly the duration of this span of time.

So upon further investigation, the question is asked, was the wrapper hung or storing these messages between  11:51:05,269 to 11:57:24,863 and then finally wrote them out at 11:57:24 ?

Regards,

Tu Nguyen | FTPC Support Engineer | Office: 408.271.3464 | Mobile: 408.464.3252 | Rockwell Automation | Mission Viejo, CA (GMT -8)

From: Tu T. Nguyen
Sent: Monday, January 26, 2015 11:29 AM
To: wra...@li...<mailto:wra...@li...>
Cc: Elaine M. Julius
Subject: RE: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

Hello Alexandre,

I think I am close to figuring out this issue.  If I could get a little advice from you.

I think this issue has to do with excessive logging from the application.

In 3 (out of 3 that I have looked into ) instances where we see this CPU time message,  the logges are filled with 800 or more lines of logging in the exact second the message happens.

To support this, there was a time when the logging was not configured and the app ran 50 days without an issue.

Do you think this amount of logging may cause the CPU time issue/message?

Also.  For the logging level, it was set to “WARNING”, when the actual level should be “WARN”.  I see debug and info message in the log that should not be there.  Can you confirm that “WARNING” is not a valid setting?

Regards,

Tu Nguyen | FTPC Support Engineer | Office: 408.271.3464 | Mobile: 408.464.3252 | Rockwell Automation | Mission Viejo, CA (GMT -8)

From: Alexandre Klein [mailto:ale...@ta...]
Sent: Wednesday, October 01, 2014 10:54 PM
To: wra...@li...<mailto:wra...@li...>
Cc: Elaine M. Julius
Subject: Re: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

Tu,

Since version 3.2.3, the Wrapper has evolved  a lot.
Please take a look at the release notes which contains all bug fixes and new features for the Java Service Wrapper.
http://wrapper.tanukisoftware.com/doc/english/release-notes.html

As you can see, the list is long.  Here are  some changes that might resolve your issue:
- we have fixed memory leaks
- we have improved the way to write large amounts of output (otherwise the Wrapper thought the JVM was frozen)
- we have fixed heap corruption
- we have improved the way the Java side of the Wrapper behaves when the Wrapper fails to ping the JVM for an extended period of time. (This was causing problems on systems which were heavily IO bound because the Wrapper could block for a while while trying to write to the log file and the JVM was exiting)

As Leif mentioned, we haven't received any log file.
Can you send it to: su...@ta...<mailto:su...@ta...>
We would be happy to have a look. If possible, please send us the configuration file (wrapper.conf) as well.

Regards,
Alexandre Klein

Alexandre Klein
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com<http://www.tanukisoftware.com/>

On Thu, Oct 2, 2014 at 9:21 AM, Tu T. Nguyen <ttn...@ra...<mailto:ttn...@ra...>> wrote:
What we are looking for is some justification that we can give our customer that upgrading even might resolve the issue they are seeing.

Based on what you see in the logs, is there anything that would point to an upgrade being likely to resolve the problem?

From: Leif Mortenson [mailto:lei...@ta...<mailto:lei...@ta...>]
Sent: Wednesday, October 01, 2014 6:33 AM
To: Wrapper User List
Cc: Elaine M. Julius
Subject: Re: [Wrapper-user] JVM restarts "Wrapper Process has not received any CPU time for 69 seconds"

Tu,
Is the machine you are running on a physical or a virtual machine?  We have seen cases where a loaded host causes the VM to freeze up when the guest itself does not show any load.
3.2.3 is also a VERY old version of the Wrapper.  There have been a lot of improvements over the years in this area.  Please try 3.5.25 and see how that works for you.
You mentioned log files, but there was nothing attached to your mail.

Cheers,
Leif

On Wed, Oct 1, 2014 at 10:23 PM, Tu T. Nguyen <ttn...@ra...<mailto:ttn...@ra...>> wrote:

Hello,

I have an issue where the wrapper restarts the JVM multiple times a day.  We are using version 3.2.3 on Windows 2003 SP2.  The duration always varies.  We checked the CPU usage and its always very little when this happens .  We have about 6 services that use the wrapper on this machine and they restart at different times.  The suggestion is that if there was a CPU bottle neck they would all have this error at the same time.  We also have other sites which use the same configuration but do not have this problem.

We have collected logs with wrapper debugging enabled.  Please have a look, any help would be much appreciated!

Thank you,

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
Wra...@li...<mailto:Wra...@li...>
https://lists.sourceforge.net/lists/listinfo/wrapper-user