7 Replies Latest reply on Apr 17, 2008 10:58 AM by Bob Ninja

    WAR hot-swap

    Antonio Mota Newbie

      Hello:

      I was testing a app on AS5Beta2 without problems. Today I installed Beta4 to do the same kind of testing but I found errors doing the hot deploy of a already started war.

      I'm doing this by exporting the war file directly to the deploy dir on JBoss from within the Eclipse IDE.

      Is there some known problem with this?

      Thanks.

        • 1. Re: WAR hot-swap
          Antonio Mota Newbie

          If I export the war to another location and then drop it into the deploy dir of JBoss, here's what I get (only in Beta4, in Beta2 it's OK):

          16:34:03,087 INFO [TomcatDeployment] undeploy, ctxPath=/SLayer, vfsUrl=SLayer.war
          16:34:03,243 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/jboss/jboss-5.0.0.Beta4/server/default/deploy/SLayer.war state=Not Installed mode=Manual requiredState=Parse
          org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/jboss/jboss-5.0.0.Beta4/server/default/deploy/SLayer.war
          at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:232)
          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199)
          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
          at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
          at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
          at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
          at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
          at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
          at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
          at java.lang.Thread.run(Thread.java:595)
          Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: null
          at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193)
          at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
          at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:120)
          at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
          ... 25 more
          Caused by: java.net.MalformedURLException
          at java.net.URL.<init>(URL.java:601)
          at java.net.URL.<init>(URL.java:464)
          at java.net.URL.<init>(URL.java:413)
          at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
          at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
          at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
          at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
          at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
          at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:189)
          ... 29 more
          16:34:03,243 WARN [HDScanner] Failed to process changes
          org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

          *** CONTEXTS IN ERROR: Name -> Error

          vfsfile:/C:/jboss/jboss-5.0.0.Beta4/server/default/deploy/SLayer.war -> java.net.MalformedURLException


          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:576)
          at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:559)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
          at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
          at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
          at java.lang.Thread.run(Thread.java:595)


          • 2. Re: WAR hot-swap
            Antonio Mota Newbie

            Actually it doesen't work on Beta2 either, it works only on jboss-4.2.2.GA.

            • 3. Re: WAR hot-swap
              Antonio Mota Newbie

              This is so interesting... After some changes, not it exports ok into JBoss 5B4 but the server doesen't undeply/deploy the war file as it did in 4.2.2GA.

              Anyone?

              • 4. Re: WAR hot-swap
                Antonio Mota Newbie

                I still have this problem, no one has the same problem?

                Thanks.

                • 5. Re: WAR hot-swap
                  Antonio Mota Newbie

                  Now I have another situation hot deploying the birt.war example that comes with birt.

                  BTW, does anyone answer questions on this forums? I just saw my old posts way back in 2005 and saw that I never had one answer even...

                  16:06:44,706 INFO [TomcatDeployment] deploy, ctxPath=/birt, vfsUrl=birt.war
                  16:06:55,097 WARN [HDScanner] Failed to process changes
                  org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                  *** DEPLOYMENTS MISSING DEPLOYERS: Name

                  vfsfile:/C:/jboss/jboss-5.0.0.Beta4/server/default/deploy/birt.war

                  • 6. Re: WAR hot-swap
                    Peter Johnson Master

                    Was the app server running when you placed the birt.war file into the deploy directory? Or did you copy first, and then start the app server? I have found that many archives will not deploy properly unless the app server is brought up first, and then the file deployed.

                    Also, does birt.war work on JBossAS 4.2.2? If so, you will just have to patiently wait along with the rest of us as the jbossas team fixes the multitude of deployment problems they have introduced with the new deployers in 5.0.

                    • 7. Re: WAR hot-swap
                      Bob Ninja Newbie

                      Got the same issue for a trivial WAR file (index.jsp and web.xml)

                      At last I stopped the server, deleted the war file in deploy dir using OS (file manager), then restarted and copied WAR file into deploy again (as if it were a new deployment). Then it worked.

                      So you may have to restart the server and try re-deploying from scratch.

                      I am using the latest BETA4.