The deployment should be going into a failed state as soon as an error occurs. I thought we were talking about the change to not fail the server if a core component fails. I didn't make the change so I don't know if this is it or not. Until we clearly define the state machine of deployments we are not going to have well defined failure and recovery semantics.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Dain Sundstrom" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 30, 2002 1:57 PM Subject: Re: [JBoss-dev] DeploymentException does NOT stop deployment > Yes I agree about 24x7, but the application (ejb-jar) still deploys. > This is a test case and I can execute test the just fail. It total > breaks the server, because my code (and others) assume that if a > DeploymenException is thrown it rolls back the deployment. > > Anyway this code catches Throwable. That means an out of memory error > will not cause a deployment rollback. > > Are you serious that this is desirable behavior? > > -dain > > Scott M Stark wrote: > > That was a conscious decision. If we are going to get to 24x7 > > available kernels it means never restarting the server. Bad apps > > should be fixable without taking down the server. The warning > > log message is necessary if an admin is to be informed that > > a deployment has failed. Otherwise your letting your customers > > perform you administration by telling your app is broke. > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
