A deployment exception should clean up all the resources set up. It seems that since we added the EJB as MBean (i think I did?) we don't remove it if something goes wrong. We need to centralize these or have the proper callbacks in the dependents to clean their own stuff.
Deployment should almost be a transactional operation, it all happens or it doesn't, we have the architecture to do it now (centralized) so let's do it. marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Monday, March 04, 2002 11:18 AM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Problem with new deployer | | |I noticed that yesterday also. I'll see what I can do. First I'm trying |to fix the deployment order problem, so at least you can start the |server;-) | |david jencks | |On 2002.03.04 13:38:42 -0500 Dain Sundstrom wrote: |> I have been working on the XmlFileLoader stuff I discussed yesterday and |> it has revealed a problem with the new deployer. When a |> DeploymentException is thrown in the create life cycle method the |> deployer does not remove the ejbs that were registered a part for |> ejb-jar. Then later when you fix the first problem you have to restart |> the server because you have junk still registered in jndi. |> |> For example, on my first deploy, I get the following exception: |> |> 12:28:55,838 ERROR [EntityContainer] Exception in service lifecyle |> operation: create org.jboss.deployment.DeploymentException: Invalid XML: |> |file=file:/home/dain/work/jboss/jboss-all/build/output/jboss-3.0.0b eta2/server/default/tmp/deploy/home/dain/work/jboss/jboss-all/testsuite/outp ut/lib/cmp2-|readonly.jar/69.cmp2-readonly.jar!/META-INF/jbosscmp-jdbc.xml |> --- Several stack traces here then --- |> 12:28:55,998 WARN [ServiceController] Ignoring request to destroy |> non-existant service: jboss.j2ee:service=EJB,jndiName=ejb/EJBTestRunner |> 12:28:55,998 WARN [ServiceController] Ignoring request to destroy |> non-existant service: jboss.j2ee:service=EJB,jndiName=PublisherEJB |> 12:28:55,999 INFO [EjbModule] Remove JSR-77 EJB Module: |> jboss.management.single |> |:J2EEDomain=Manager,name=cmp2-readonly.jar,J2EEServer=Single,J2EEAp |plication=cmp2-readonly.jar,type=EjbModule |> 12:28:55,999 INFO [EjbModule] Remove fake JSR-77 parent Application: |> |jboss.management.single:J2EEDomain=Manager,J2EEServer=Single,name=c |mp2-readonly.jar,type=J2EEApplication |> 12:28:56,000 INFO [EjbModule] Destroyed |> 12:28:56,001 INFO [MainDeployer] Cleaned Deployment |> file:/home/dain/work/jboss/jboss-all/testsuite/output/lib/cmp2-readonly.jar > 12:28:56,001 INFO [MainDeployer] Undeployed > file:/home/dain/work/jboss/jboss-all/testsuite/output/lib/cmp2-readonly.jar > > Then I fix the problem, deploy again, and I get the following exception: > > 12:35:12,895 INFO [MainDeployer] Starting deployment of package: > file:/home/dain/work/jboss/jboss-all/testsuite/output/lib/cmp2-readonly.jar > 12:35:12,960 INFO [EjbModule] Creating > 12:35:12,974 INFO [EjbModule] Deploying PublisherEJB > 12:35:12,977 INFO [EjbModule] Deploying BookEJB > 12:35:12,980 INFO [EjbModule] Deploying EJBTestRunnerEJB > 12:35:12,983 ERROR [EjbModule] Initialization failed > javax.management.InstanceAlreadyExistsException: > jboss.j2ee:service=EJB,jndiName=BookEJB > at > com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134 ) > at > com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.ja va:2352) > > Any ideas? > > -dain > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
