wrapper-user

[Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

Hi

Altough the system is practically idle I often get VM restarts beacuse 
the ping request times out. I have set the timeout for 4 minutes with
wrapper.ping.timeout=240
wrapper.ping.interval=5

Does anybody know how to fix this problem without disabling VM restarts?

Madis


Here is the logfile for an example restart:

STATUS | wrapper  | 2007/03/14 14:13:17 | Starting the Jawilla Test service...
STATUS | wrapper  | 2007/03/14 14:13:17 | --> Wrapper Started as Service
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Using tick timer.
DEBUG  | wrapperp | 2007/03/14 14:13:17 | server listening on port 32000.
STATUS | wrapper  | 2007/03/14 14:13:17 | Launching a JVM...
DEBUG  | wrapper  | 2007/03/14 14:13:17 | command: 
"H:\WINDOWS\system32\javaw.exe" -Djava.library.path="../lib" -classpath 
"../lib/jawilla-wrapper.jar;../lib/comm.jar" 
-Dwrapper.key="dNieTuNL6egp5T7P" -Dwrapper.port=32000 
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
-Dwrapper.debug="TRUE" -Dwrapper.pid=4772 -Dwrapper.version="3.2.3" 
-Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" 
-Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.jawilla.wrapper.Main
DEBUG  | wrapper  | 2007/03/14 14:13:17 | JVM started (PID=508)
INFO   | jvm 1    | 2007/03/14 14:13:17 | Initializing...
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperManager class initialized by thread: main  Using classloader: 
sun.misc.Launcher$AppClassLoader@d9f9c3
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2007/03/14 14:13:17 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2007/03/14 14:13:17 |
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Running a 32-bit JVM.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2007/03/14 14:13:17 | Java Version   : 1.6.0-b105 Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2007/03/14 14:13:17 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 1    | 2007/03/14 14:13:17 |
INFO   | jvm 1    | 2007/03/14 14:13:17 | Control event monitor thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperManager.start(com.jawilla.wrapper.Main@201f9, args[]) called by thread: main
INFO   | jvm 1    | 2007/03/14 14:13:17 | Startup runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Communications runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 1    | 2007/03/14 14:13:17 | Opened Socket from 31000 to 32000
INFO   | jvm 1    | 2007/03/14 14:13:17 | Send a packet KEY : dNieTuNL6egp5T7P
INFO   | jvm 1    | 2007/03/14 14:13:17 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
DEBUG  | wrapperp | 2007/03/14 14:13:17 | accepted a socket from 127.0.0.1 on port 31000
DEBUG  | wrapperp | 2007/03/14 14:13:17 | read a packet KEY : dNieTuNL6egp5T7P
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Got key from JVM: dNieTuNL6egp5T7P
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet PING_TIMEOUT : 240
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet PROPERTIES : (Property Values)
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Start Application.
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet START : start
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PING_TIMEOUT : 240
INFO   | jvm 1    | 2007/03/14 14:13:17 | PingTimeout from Wrapper is 240000
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_FILE_SEPARATOR->\
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_PATH_SEPARATOR->;
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.format->PM
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.loglevel->ERROR
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.title->Jawilla Test Manager
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.classpath.1->../lib/jawilla-wrapper.jar
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.classpath.2->../lib/comm.jar
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.command->javaw
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.library.path.1->../lib
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.mainclass->com.jawilla.wrapper.Main
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile->../logs/wrapper.log
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.format->LPTM
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.loglevel->DEBUG
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.maxfiles->0
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.maxsize->100k
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.dependency.1->
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.description->Your add here.
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.displayname->Jawilla Test
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.interactive->true
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.name->jawillatest
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.starttype->AUTO_START
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ping.interval->5
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ping.timeout->240
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.syslog.loglevel->ERROR
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet START : start
INFO   | jvm 1    | 2007/03/14 14:13:17 | calling WrapperListener.start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | Waiting for WrapperListener.start runner thread to complete.
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperListener.start runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | user.dir=h:\work\e-police\serviceWrapper\bin
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperListener.start runner thread stopped.
INFO   | jvm 1    | 2007/03/14 14:13:17 | returned from WrapperListener.start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | Send a packet STARTED :
DEBUG  | wrapperp | 2007/03/14 14:13:17 | read a packet STARTED :
DEBUG  | wrapper  | 2007/03/14 14:13:17 | JVM signalled that it was started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Startup runner thread stopped.
STATUS | wrapper  | 2007/03/14 14:13:19 | Jawilla Test started.
DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:31 | send a packet PING : ping
..............................................................................................................
DEBUG  | wrapperp | 2007/03/14 14:17:44 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:17:44 | Received a packet PING : ping
ERROR  | wrapper  | 2007/03/14 14:17:47 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2007/03/14 14:17:47 | JVM did not exit on request, terminated
DEBUG  | wrapperp | 2007/03/14 14:17:47 | server listening on port 32001.
DEBUG  | wrapper  | 2007/03/14 14:17:47 | JVM was only running for 245 seconds leading to a failed restart count of 1.
DEBUG  | wrapper  | 2007/03/14 14:17:47 | Waiting 5 seconds before launching another JVM.
STATUS | wrapper  | 2007/03/14 14:17:52 | Launching a JVM...

[Wrapper-user] Compilation in HP-UX IA64

[Diego R. <dru...@be...>]

Hi, I'm trying to compile the sources in a HP-UX IA64 and I'm getting
the following error:

Wrapper Build System
--------------------
Buildfile: build.xml

init:
OS=3D'HP-UX'

update-info:
Copying 1 file to
/home/cce/wrapper/wrapper_3.1.1_src/src/java/org/tanukisoftware/wrapper
Copying 1 file to /home/cce/wrapper/wrapper_3.1.1_src/src/c

compile-java:
Compiling 1 source file to
/home/cce/wrapper/wrapper_3.1.1_src/build/classes

compile-c-unix:
if test ! -d .deps; then mkdir .deps; fi
gcc -O3 -Wall --pedantic -DHPUX -D_XOPEN_SOURCE_EXTENDED wrapper.c
wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -lm
-o ../../bin/wrapper
wrapper.c: In function 'wrapperProtocolOpen':
wrapper.c:558: warning: dereferencing type-punned pointer will break
strict-aliasing rules
logger.c:230: warning: missing braces around initializer
logger.c:230: warning: (near initialization for
'log_printfMutex.m_short')
ld: Unsatisfied symbol "rk_globfree" in file /var/tmp//cc025oOs.o
ld: Unsatisfied symbol "rk_glob" in file /var/tmp//cc025oOs.o
2 errors.
collect2: ld returned 1 exit status
gmake: *** [wrapper] Error 1

BUILD FAILED
/home/cce/wrapper/wrapper_3.1.1_src/build.xml:316: exec returned: 2


Any Ideas?=20

Diego.
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Re: [Wrapper-user] JVM restart with ping-timeout

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

Madis,
    Looking at your logs, the JVM is receiving pings from the Wrapper 
process
correctly, but it does not appear to be sending the ping reply back to 
the Wrapper.

    This is what a single ping cycle should look like:
---
DEBUG  | wrapperp | send a packet PING : ping
INFO   | jvm 1    | Received a packet PING : ping
INFO   | jvm 1    | Send a packet PING : ping
DEBUG  | wrapperp | read a packet PING : ping
---

    But from your logs, you are only seeing the first two lines:
---
DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
---

    Reviewing the source, I can not think of any reason why this would 
happen
repeatedly.  There are event callbacks, but if the thread was getting 
stuck there
somehow, you would not see the second fourth line.

    Are you using an unmodified version of the wrapper jar?  I ask 
because of
the lines like the following in the log:
---
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
(Property Values)
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
props:set.WRAPPER_FILE_SEPARATOR->\
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
---
    From their timing in the log, they are being printed before your 
application has
been started and must be being displayed from within the internal
WrapperManager.readProperties method.  That is not output that was in 
the original
source.

Cheers,
Leif


madis wrote:
> Hi
>
> Altough the system is practically idle I often get VM restarts beacuse 
> the ping request times out. I have set the timeout for 4 minutes with
> wrapper.ping.timeout=240
> wrapper.ping.interval=5
>
> Does anybody know how to fix this problem without disabling VM restarts?
>
> Madis
>
>
> Here is the logfile for an example restart:
>   
<snip>

Re: [Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

I compile the service wrapper java source with my own project. Kinda got 
that way because when I installed the service on XP sp2,  I could not 
get it started. Everything was OK after I did a little restart but I 
poked around a little before that (not much, just the properties and dll 
resolving).

Tryd with original source from version 3.2.3:

Still doing 50% from full cycle:
....................
INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
....................

If the ping cycle is incomplete why does it take so many trys before VM 
shuts down?

Leif Mortenson wrote:
> Madis,
>     Looking at your logs, the JVM is receiving pings from the Wrapper 
> process
> correctly, but it does not appear to be sending the ping reply back to 
> the Wrapper.
>
>     This is what a single ping cycle should look like:
> ---
> DEBUG  | wrapperp | send a packet PING : ping
> INFO   | jvm 1    | Received a packet PING : ping
> INFO   | jvm 1    | Send a packet PING : ping
> DEBUG  | wrapperp | read a packet PING : ping
> ---
>
>     But from your logs, you are only seeing the first two lines:
> ---
> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
> ---
>
>     Reviewing the source, I can not think of any reason why this would 
> happen
> repeatedly.  There are event callbacks, but if the thread was getting 
> stuck there
> somehow, you would not see the second fourth line.
>
>     Are you using an unmodified version of the wrapper jar?  I ask 
> because of
> the lines like the following in the log:
> ---
> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
> (Property Values)
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
> props:set.WRAPPER_FILE_SEPARATOR->\
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
> ---
>     From their timing in the log, they are being printed before your 
> application has
> been started and must be being displayed from within the internal
> WrapperManager.readProperties method.  That is not output that was in 
> the original
> source.
>
> Cheers,
> Leif
>
>
> madis wrote:
>   
>> Hi
>>
>> Altough the system is practically idle I often get VM restarts beacuse 
>> the ping request times out. I have set the timeout for 4 minutes with
>> wrapper.ping.timeout=240
>> wrapper.ping.interval=5
>>
>> Does anybody know how to fix this problem without disabling VM restarts?
>>
>> Madis
>>
>>
>> Here is the logfile for an example restart:
>>   
>>     
> <snip>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] JVM restart with ping-timeout

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

Madis,
    The Wrapper sends PING packets to the JVM at an interval defined by the
wrapper.ping.interval property, every 5 seconds by default.  The JVM side of
Normally, the JVM immediately responds by sending a PING back to the
Wrapper process.
    A timeout occurs when ever more than the wrapper.ping.timeout has 
expired
without the Wrapper process receiving a PING packet from the JVM.

A) This is not a problem that I have ever had reported in the past.
B) Reviewing the source, I do not see any way at all that this could be 
happening
with the unmodified source.   Immediately after the "Received a 
packet..." message
is logged by the handleSocket() method, it proceeds to call the 
sendCommand()
method where a "Send a packet..." message should be logged.  That is not 
happening.

    I would love to help further, but it is not really possible for me 
to try to debug
modified versions of the Wrapper.   I have given you clues as to where 
the problem
likely is, but you are going to need to go in and debug what is happening.

    Cheers,
    Leif

madis wrote:
> I compile the service wrapper java source with my own project. Kinda 
> got that way because when I installed the service on XP sp2,  I could 
> not get it started. Everything was OK after I did a little restart but 
> I poked around a little before that (not much, just the properties and 
> dll resolving).
>
> Tryd with original source from version 3.2.3:
>
> Still doing 50% from full cycle:
> ....................
> INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
> ....................
>
> If the ping cycle is incomplete why does it take so many trys before 
> VM shuts down?
>
> Leif Mortenson wrote:
>> Madis,
>>     Looking at your logs, the JVM is receiving pings from the Wrapper 
>> process
>> correctly, but it does not appear to be sending the ping reply back to 
>> the Wrapper.
>>
>>     This is what a single ping cycle should look like:
>> ---
>> DEBUG  | wrapperp | send a packet PING : ping
>> INFO   | jvm 1    | Received a packet PING : ping
>> INFO   | jvm 1    | Send a packet PING : ping
>> DEBUG  | wrapperp | read a packet PING : ping
>> ---
>>
>>     But from your logs, you are only seeing the first two lines:
>> ---
>> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
>> ---
>>
>>     Reviewing the source, I can not think of any reason why this would 
>> happen
>> repeatedly.  There are event callbacks, but if the thread was getting 
>> stuck there
>> somehow, you would not see the second fourth line.
>>
>>     Are you using an unmodified version of the wrapper jar?  I ask 
>> because of
>> the lines like the following in the log:
>> ---
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
>> (Property Values)
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
>> props:set.WRAPPER_FILE_SEPARATOR->\
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
>> ---
>>     From their timing in the log, they are being printed before your 
>> application has
>> been started and must be being displayed from within the internal
>> WrapperManager.readProperties method.  That is not output that was in 
>> the original
>> source.
>>
>> Cheers,
>> Leif
>>
>>
>> madis wrote:
>>   
>>> Hi
>>>
>>> Altough the system is practically idle I often get VM restarts beacuse 
>>> the ping request times out. I have set the timeout for 4 minutes with
>>> wrapper.ping.timeout=240
>>> wrapper.ping.interval=5
>>>
>>> Does anybody know how to fix this problem without disabling VM restarts?
>>>
>>> Madis
>>>
>>>
>>> Here is the logfile for an example restart:
>>>   
>>>     
>> <snip>
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>   
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

Deleting class files and recompiling the original source did the trick.

Thanks for pointers.

Leif Mortenson wrote:
> Madis,
>     The Wrapper sends PING packets to the JVM at an interval defined by the
> wrapper.ping.interval property, every 5 seconds by default.  The JVM side of
> Normally, the JVM immediately responds by sending a PING back to the
> Wrapper process.
>     A timeout occurs when ever more than the wrapper.ping.timeout has 
> expired
> without the Wrapper process receiving a PING packet from the JVM.
>
> A) This is not a problem that I have ever had reported in the past.
> B) Reviewing the source, I do not see any way at all that this could be 
> happening
> with the unmodified source.   Immediately after the "Received a 
> packet..." message
> is logged by the handleSocket() method, it proceeds to call the 
> sendCommand()
> method where a "Send a packet..." message should be logged.  That is not 
> happening.
>
>     I would love to help further, but it is not really possible for me 
> to try to debug
> modified versions of the Wrapper.   I have given you clues as to where 
> the problem
> likely is, but you are going to need to go in and debug what is happening.
>
>     Cheers,
>     Leif
>
> madis wrote:
>   
>> I compile the service wrapper java source with my own project. Kinda 
>> got that way because when I installed the service on XP sp2,  I could 
>> not get it started. Everything was OK after I did a little restart but 
>> I poked around a little before that (not much, just the properties and 
>> dll resolving).
>>
>> Tryd with original source from version 3.2.3:
>>
>> Still doing 50% from full cycle:
>> ....................
>> INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
>> ....................
>>
>> If the ping cycle is incomplete why does it take so many trys before 
>> VM shuts down?
>>
>> Leif Mortenson wrote:
>>     
>>> Madis,
>>>     Looking at your logs, the JVM is receiving pings from the Wrapper 
>>> process
>>> correctly, but it does not appear to be sending the ping reply back to 
>>> the Wrapper.
>>>
>>>     This is what a single ping cycle should look like:
>>> ---
>>> DEBUG  | wrapperp | send a packet PING : ping
>>> INFO   | jvm 1    | Received a packet PING : ping
>>> INFO   | jvm 1    | Send a packet PING : ping
>>> DEBUG  | wrapperp | read a packet PING : ping
>>> ---
>>>
>>>     But from your logs, you are only seeing the first two lines:
>>> ---
>>> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
>>> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
>>> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
>>> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
>>> ---
>>>
>>>     Reviewing the source, I can not think of any reason why this would 
>>> happen
>>> repeatedly.  There are event callbacks, but if the thread was getting 
>>> stuck there
>>> somehow, you would not see the second fourth line.
>>>
>>>     Are you using an unmodified version of the wrapper jar?  I ask 
>>> because of
>>> the lines like the following in the log:
>>> ---
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
>>> (Property Values)
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
>>> props:set.WRAPPER_FILE_SEPARATOR->\
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
>>> ---
>>>     From their timing in the log, they are being printed before your 
>>> application has
>>> been started and must be being displayed from within the internal
>>> WrapperManager.readProperties method.  That is not output that was in 
>>> the original
>>> source.
>>>
>>> Cheers,
>>> Leif
>>>
>>>
>>> madis wrote:
>>>   
>>>       
>>>> Hi
>>>>
>>>> Altough the system is practically idle I often get VM restarts beacuse 
>>>> the ping request times out. I have set the timeout for 4 minutes with
>>>> wrapper.ping.timeout=240
>>>> wrapper.ping.interval=5
>>>>
>>>> Does anybody know how to fix this problem without disabling VM restarts?
>>>>
>>>> Madis
>>>>
>>>>
>>>> Here is the logfile for an example restart:
>>>>   
>>>>     
>>>>         
>>> <snip>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>>> opinions on IT & business topics through brief surveys-and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>   
>>>       
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>   
>>     
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>