On May 29, 2007, at 3:09 PM, Mark Aufdencamp wrote:
I would guess this probably depends on your application, but it
doesnt sound like a good idea. I would think that an EJB container
would need to be able to safely complete transactions and passivate/
deallocate it's Beans particular CMP Entity Beans. The Web
container might also maintain Application scoped information that
needs a clean safe shutdown as well.
However, both the shutdown jar or console command and hitting ctrl-c
on your console have approximately the same effect in code -- calling
the shutdown hook that stops and unloads all the running
configurations in reverse order of their starting. If your
application uses transactions properly any kind of shutdown shouldn't
result in data corruption, but you may lose partially computed
results in process. We don't make any attempt I'm aware of to finish
processing in flight requests before turning off a gbean.
thanks
david jencks
Mark Aufdencamp
[EMAIL PROTECTED]
-------- Original Message --------
Subject: Safe shutdown
From: Joel Spotts <[EMAIL PROTECTED]>
Date: Tue, May 29, 2007 5:05 pm
To: [email protected]
Is there any danger in stopping geronimo by simply killing the
application as opposed to running the shutdown.jar or shutdown.bat?
For various reasons (which I can get into if the answer is that it
is not safe) I cannot easily stop the server with the shutdown tool.
Thanks,
Yoel Spotts
