[Wrapper-user] RE: questions

[Jindong Li <Jin...@so...>]

One more thing I noticed, if I log off the system with the service running,
those 3 JVM's that started by my java application which is wrapped by the
service wrapper are killed, reason I know this is happening is that, one JVM
is used to start TOMCAT, once I logged off, I was not able to talk to the
WebServer on port 8080 anymore.

If I then log on again, the service status is still showing running but
really it is just the wrapper that's running, all JVM's started by the
service seem to be no longer running...

Is this because how the windows log off process works?

Anybody else tried log off, if so after logging off, is the application
still running as expected?

Thanks,

Jindong.

		 -----Original Message-----
		From: 	Jindong Li  
		Sent:	Friday, April 04, 2003 3:04 PM
		To:	'wra...@li...'
		Subject:	RE: questions

		Thanks for your prompt reply...

		My application just starts up another 3 JVM's where RMI
servers running in 2 of them and Tomcat running in the 3rd one...so from the
point of the JVM where this application is launched, I suppose there's no
non-daemon threads running?

		Here're the log files I got after turned on debug for the
wrapper...interesting thing is that when I stop the service from command
line using "net stop", sometime it is successful sometimes it isn't...the
first one is the one that I was able to stop the service from command line,
the second one however, I got the "could not be stopped" message.

		It seems to me that in both cases, wrapper is working just
fine...

		 << File: wrapper.log.stopped >>  << File:
wrapper.log.notbestopped >> 

		Any comment would be appreciated...

		Thanks,

		Jindong.

				 -----Original Message-----
				From: 	Jindong Li  
				Sent:	Wednesday, April 02, 2003 11:06 AM
				To:	'wra...@li...';
'wra...@li...'
				Subject:	questions

				Hi there,

				I'm currently exploring the possibility of
using Java Service Wrapper to run our Java application as an NT service
(Windows 2000 professional), everything is going well so far...you guys did
a great job!!

				I do have couple of questions:

*	The WrapperManager detects if there's any non-daemon threads other
than the current thread and system thread running after the application is
launched, in my case since all my threads are daemon threads, I had to start
another thread in my listener code to run indefinitely until it receives the
stop control from the service panel...otherwise, the service will be stopped
right after it was started, any other way to get around that ?

*	When I use the command line command "net start/stop" to start / stop
the service I installed using wrapper.exe, starting is always successful
without any issue but stopping, on the other hand,  I often get "... service
could not be stopped." even though the service has been stopped indeed...any
idea?  This problem does not appear to exist if stopping from the GUI.

				Thanks and really appreciate your help...

				Jindong.

 
###############################################################
This message has been scanned for viruses and other contents.
###############################################################