4 Replies Latest reply on May 11, 2009 2:44 AM by jaikiran

    Plugin Release against AS 5.1.0.CR1

    alrubinger

      Hmm, some issues that I didn't see present when patching AS using the Plugin locally:

      http://jboss.hudson.alrubinger.com/job/EJB3_Integration_TestSuite_Plugin_AS5_Latest_Release/ws/jbossas/build/output/jboss-5.1.0.CR1/server/all/log/server.log/*view*/

      org.jboss.deployers.spi.DeploymentException: Error deploying jboss-jca-deployer.jar: org/jboss/ejb3/endpoint/Endpoint
       at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196)
       at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
       at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
       at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
       at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
       at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
       at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
       at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
       at org.jboss.Main.boot(Main.java:216)
       at org.jboss.Main$1.run(Main.java:546)
       at java.lang.Thread.run(Thread.java:595)


      What's weird is that I'd even linked Jaikiran to a Hudson showing the Endpoint tests passing w/ no regression (can't seem to find it now). So I'll have a look tomorrow and clear up this mess.

      S,
      ALR

        • 1. Re: Plugin Release against AS 5.1.0.CR1
          jaikiran

           

          "ALRubinger" wrote:
          Hmm, some issues that I didn't see present when patching AS using the Plugin locally:

          Looks related to the change that i did in https://jira.jboss.org/jira/browse/EJBTHREE-1810. I reverted the change that i had done earlier to the installer component, after EJBTHREE-1780 was resolved. I guess, we still need that change?

          P.S: After reverting the change in EJBTHREE-1810, i had given the plugin a try against 5.1.0.CR1, but did not see this issue - will have to see why it passed locally for me.



          • 2. Re: Plugin Release against AS 5.1.0.CR1
            jaikiran

             

            "ALRubinger" wrote:

            What's weird is that I'd even linked Jaikiran to a Hudson showing the Endpoint tests passing w/ no regression (can't seem to find it now). So I'll have a look tomorrow and clear up this mess.

            S,
            ALR


            Yep, the runs were clean. The revert to EJBTHREE-1810 was after that run.

            • 3. Re: Plugin Release against AS 5.1.0.CR1
              jaikiran

              Looked at the changes done in EJBTHREE-1786. I think we need to bring the ejb3-endpoint, into the plugin, the same way that we have done for ejb3-endpoint-deployers. I'll create a patch and test.

              • 4. Re: Plugin Release against AS 5.1.0.CR1
                jaikiran

                 

                "jaikiran" wrote:
                "ALRubinger" wrote:

                P.S: After reverting the change in EJBTHREE-1810, i had given the plugin a try against 5.1.0.CR1, but did not see this issue - will have to see why it passed locally for me.



                My mistake. I looked at the AS that i tested this against. The test was done against the AS which had been patched once before. Effectively, it already had the ejb3-endpoint.jar in the lib folder and hence i did not run into this issue.