4 Replies Latest reply on Jun 27, 2008 2:31 AM by tarch82

    Deployment Problem -- Unable to replace existing file

    rajeevdr

      Hi,
      When I am trying to deploy new version of the existing file 'StudentEAR.ear' in JBoss 5.0.0.4 beta server, I am getting the below error.

      I am using Eclipse Europa & JBoss 5.0.0.4 beta server. I am right clicking on the project & selecting run as --> run on server for deployment. The same method works with JBoss 4.2.2 GA with out any problem.

      BUILD FAILED
      C:\JBoss\eclipse\plugins\org.eclipse.jst.server.generic.jboss_1.5.105.v200709061325\buildfiles\jboss323.xml:33: Unable to remove existing file C:\JBoss\jboss-5.0.0.Beta4\server\default\deploy\StudentEAR.ear
      


      Is it required to change anything in xml configuration files? Can anybody help me to solve the above problem?
      ----------
      Thanks,
      Rajeev R

        • 1. Re: Deployment Problem -- Unable to replace existing file
          peterj

          This is a known issue with 5.0.0.beta4 - it tends to lock files on Windows. Probably related to the new virtual file system. Until the next version comes out, you will have to restart the app server if you want to redeploy anything.

          • 2. Re: Deployment Problem -- Unable to replace existing file
            rajeevdr

            Thank you very much Peter. This issue was eating my head from quite some time.

            __________
            Regards,
            Rajeev R.

            • 3. Re: Deployment Problem -- Unable to replace existing file
              rweed

              I had the file locking issue on Windows with 5.0.0.beta4, so I tried the Linux version and there is no locking problem there.

              JBoss goes through the undeploy/deploy process, BUT it is still accessing the old classes. SO, under Linux, you still need to restart the server to effect your changes even without the file locking issue.

              • 4. Re: Deployment Problem -- Unable to replace existing file
                tarch82

                 

                "rweed" wrote:

                I had the file locking issue on Windows with 5.0.0.beta4, so I tried the Linux version and there is no locking problem there.

                JBoss goes through the undeploy/deploy process, BUT it is still accessing the old classes. SO, under Linux, you still need to restart the server to effect your changes even without the file locking issue.


                I have the same problem of rweed with Linux...this is quite annoying, mainly because of the long start time. Is there some known workaround?

                Thank you in advance,
                bye Tarch!