[Wrapper-user] RE: Wrapper-user digest, Vol 1 #343 - 5 msgs

[Jan B. <jb...@pr...>]

> >>The code is all checked in to CVS if you would like to give it a try
> >>before the next release.  
> >>    
> >>
> >Sure, is there a way I can download a daily or weekly build? 
> (I cannot
> >find one on sourceforge and I'm not able to build any c/c++ 
> sources on
> >my windows machine)
> >  
> >
> That is because there are not any daily / weekly binary 
> builds.  I went 
> ahead and
> created snapshot and placed it up on the server.  You will 
> get a sneak 
> peek at the
> new documentation layout that will be in the next release.  (Still a 
> work in progress.)
> Be sure to read over the release notes as there are a lot of new 
> features in this
> release.
> 
> http://wrapper.tanukisoftware.org/tmp/wrapper_win32_3.1.0c.zip
> 
> Please post back to this list if you find any problems with this 
> snapshot.  Be sure
> to indicate the version being used.

With the WrapperSimpleApp it works like a charm :-)

STATUS | wrapper  | 2004/04/03 15:15:52 | --> Wrapper Started as Service
STATUS | wrapper  | 2004/04/03 15:15:52 | Launching a JVM...
INFO   | jvm 1    | 2004/04/03 15:15:53 | Wrapper (Version 3.1.0c)
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2004/04/03 15:15:53 | 
INFO   | jvm 1    | 2004/04/03 15:15:53 | Looking for servoy.properties
on C:\servoy.properties
INFO   | jvm 1    | 2004/04/03 15:15:53 | Loading servoy.properties from
C:\Program Files\Servoy\servoy.properties - Done
INFO   | jvm 1    | 2004/04/03 15:16:01 | Starting service
Tomcat-Standalone
INFO   | jvm 1    | 2004/04/03 15:16:01 | Apache Tomcat/4.0.1
INFO   | jvm 1    | 2004/04/03 15:16:03 | Starting service Tomcat-Apache
INFO   | jvm 1    | 2004/04/03 15:16:03 | Apache Tomcat/4.0.1
STATUS | wrapper  | 2004/04/03 15:16:42 | on_exit trigger matched.
Restarting the JVM.  (Exit code: 99)
STATUS | wrapper  | 2004/04/03 15:16:47 | Launching a JVM...
INFO   | jvm 2    | 2004/04/03 15:16:48 | Wrapper (Version 3.1.0c)
http://wrapper.tanukisoftware.org
INFO   | jvm 2    | 2004/04/03 15:16:48 | 
INFO   | jvm 2    | 2004/04/03 15:16:48 | Looking for servoy.properties
on C:\servoy.properties
INFO   | jvm 2    | 2004/04/03 15:16:48 | Loading servoy.properties from
C:\Program Files\Servoy\servoy.properties - Done
INFO   | jvm 2    | 2004/04/03 15:16:55 | Starting service
Tomcat-Standalone
INFO   | jvm 2    | 2004/04/03 15:16:55 | Apache Tomcat/4.0.1
INFO   | jvm 2    | 2004/04/03 15:16:58 | Starting service Tomcat-Apache
INFO   | jvm 2    | 2004/04/03 15:16:58 | Apache Tomcat/4.0.1
STATUS | wrapper  | 2004/04/03 15:17:58 | <-- Wrapper Stopped

But

With WrapperStartStopApp it's a bit strange

STATUS | wrapper  | 2004/04/03 14:17:01 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2004/04/03 14:17:01 | on_exit trigger matched.
Restarting the JVM.  (Exit code: 1)
...
...
...
INFO   | jvm 2    | 2004/04/03 14:55:25 | <last error msg>
ERROR  | wrapper  | 2004/04/03 14:55:54 | Shutdown failed: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2004/04/03 14:55:54 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2004/04/03 14:55:55 | on_exit trigger matched.
Restarting the JVM.  (Exit code: 1)

So I noted 3 issues/ideas
1) the msg "JVM did not exit on request, terminated" could be extended
by how long is waited for exit... See following point.
2) wrapper.jvm_exit.timeout=60 seems not to work? There is not a delay
seen of one minute max between log lines
3) when the JVM is killed becouse it did not stop in time, my exit code
seems lost? I did stop with system.exit(99) and not with '1' as seen in
log line.


Regards Jan Blok