I suspect you are using Windows NT/2000/XP and are trying to run the
server as a Windows NT service?
If that is the case, this is a common behaviour for many Java
applications. As soon as you try to run them as a service under Windows
and then logout, the OS sends a signal to terminate the JVM. This has to
be handled in some way - for example by using some sort of service
wrapper that catches the signals from the OS before it reaches the JVM.
A couple of wrappers available:
JNT:
http://www.eworksmart.com/JNT/
Javants (available in the JBoss CVS repository):
http://www.jboss.org/
Wrapper:
http://sourceforge.net/projects/wrapper/
Personally, I have only tried the Javants wrapper in combination with the
JBoss EJB server. Although it required some modifications to work, it did
what it should do. There are probably more wrappers available.
/Ulf Tidstrand
On Mon, 9 Sep 2002, Andrew Newton wrote:
> Ok. I've got a bit of an odd problem I was wondering if anybody else
> has seen. I'm developing a server using beepcore. Whenever I start the
> server, and then logout, it terminates. I even use the nohup command
> and that still doesn't stop it. This even happens if I'm root.
>
> I reproduced this with the Beepd example as well.
>
> I even switched out the JDK's (1.3 for 1.4). Same problem. So I
> downloaded Jakarta Tomcat to see if it was a general Java problem.
> Tomcat does not exhibit this behaviour.
>
> As anybody seen this?
>
> -andy
>
/Ulf
--
More info: http://www.dtek.chalmers.se/~d97ulf/
"Hey, we're different!" - Jay Minor, Creator of the Amiga
http://www.amiga.com/
|
