Menu
▾
▴
Re: [Wrapper-user] JVM restarted during heavy load
|
From: Mattias E. <mat...@in...> - 2012-07-20 08:20:07
|
Hi, You should be able to solve this behaviour by adding/modifying the wrapper.ping.timeout setting i your wrapper.conf file (http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html) The default value is 30 seconds. I usually set the value to about 180 second for The JBoss service (instance) we use to run our own serversoftware. // MEk Gustaf Cele skrev 2012-07-19 17:41: > We're running a JBoss server as a service under Windows using the Java Service Wrapper. For most of the time, JBoss runs fine. But... we've been experiencing some problems: When we run some heavy, long-running jobs, the wrapper sometimes decides to restart the JVM: > > ERROR | wrapper | 2012/07/19 13:11:19 | JVM appears hung: Timed out waiting for signal from JVM. > ERROR | wrapper | 2012/07/19 13:11:19 | JVM did not exit on request, terminated > STATUS | wrapper | 2012/07/19 13:11:24 | Launching a JVM... > INFO | jvm 3 | 2012/07/19 13:11:24 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > INFO | jvm 3 | 2012/07/19 13:11:24 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. > INFO | jvm 3 | 2012/07/19 13:11:24 | > INFO | jvm 3 | 2012/07/19 13:11:24 | > INFO | jvm 3 | 2012/07/19 13:11:24 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'. > INFO | jvm 3 | 2012/07/19 13:11:24 | The file is located on the path at the following location but > INFO | jvm 3 | 2012/07/19 13:11:24 | could not be loaded: > INFO | jvm 3 | 2012/07/19 13:11:24 | C:\Path\to\jboss\4.2.2.GA\lib\wrapper.dll > INFO | jvm 3 | 2012/07/19 13:11:24 | Please verify that the file is readable by the current user > INFO | jvm 3 | 2012/07/19 13:11:24 | and that the file has not been corrupted in any way. > INFO | jvm 3 | 2012/07/19 13:11:24 | One common cause of this problem is running a 32-bit version > INFO | jvm 3 | 2012/07/19 13:11:24 | of the Wrapper with a 64-bit version of Java, or vica versa. > INFO | jvm 3 | 2012/07/19 13:11:24 | This is a 64-bit JVM. > INFO | jvm 3 | 2012/07/19 13:11:24 | Reported cause: > INFO | jvm 3 | 2012/07/19 13:11:24 | C:\Path\to\jboss\4.2.2.GA\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform > INFO | jvm 3 | 2012/07/19 13:11:24 | System signals will not be handled correctly. > > Yes, we are totally going to upgrade to the 64-bit version of the wrapper, but as previously stated - JBoss works fine except sometimes during the long, heavy jobs (the JVM restart happens for approximately one in six jobs). We're wondering what could cause this behavior. > > - If our process is running at 100% CPU, how likely is it that the process won't respond to the wrapper's pings in due time (30 seconds)? > - Could the incompatible 32-bit wrapper.dll have something to do with our woes? > > It may also be relevant say to that this started happening a fairly short while ago, and didn't coincide with any changes to the setup (that we can think of, anyway). The same setup had been running happily for quite some time before, in spite of the incompatible DLL and the long-running CPU hogs. > > Thanks in advance, > > /g > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
