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. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "Dain Sundstrom" <[EMAIL PROTECTED]> > To: "JBoss-dev" <[EMAIL PROTECTED]> > Sent: Friday, August 30, 2002 1:32 PM > Subject: [JBoss-dev] DeploymentException does NOT stop deployment > > > >>My startup code throws DeploymentExceptions if an error is detected in >>the configuration, and this used to cause deployment to stop. I doesn't >>anymore. >> >>In org.jboss.system.ServiceController.start(ObjectName) we have the >>following code on line 366 (HEAD): >> >>// Call start on the service Proxy >>try >>{ >> ctx.proxy.start(); >>} >>catch (Throwable e) >>{ >> ctx.checkTransition(ServiceContext.NOTSTARTABLE); >> ctx.problem = e; >> log.warn("Problem starting service " + serviceName, e); >> return; >>} >> >>This simply writes an unnecessary exception trace and allows the >>deployment to continue. >> >>Is there a reason for this code? If not I will be more then happy >>remove the try/ catch and allow the code to exception out. >> >> >>BTW: If you want to reproduce this error modify the >>src/resources/cmp2/commerce/META-INF/jbosscmp-jdbc.xml and add some junk >>to one of the cmp-field names (like change userName to userNameXXXXX). >>Then run the following command: >> >>./build.sh -Dtest=org.jboss.test.cmp2.commerce.CommerceTest one-test >> >>Watch the 30 pages of exceptions flow by and the app still deploys. >> >>-- >>xxxxxxxxxxxxxxxxxxxxxxxx >>Dain Sundstrom >>Chief Architect JBossCMP >>JBoss Group, LLC >>xxxxxxxxxxxxxxxxxxxxxxxx > > > > > > ------------------------------------------------------- > 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 -- xxxxxxxxxxxxxxxxxxxxxxxx Dain Sundstrom Chief Architect JBossCMP JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- 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