Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-8961

Improve the handling of temporary deploy dir

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 3.3.0.M2
    • 3.3.0.M1
    • server
    • None
    • Hide

      1) make sure you have your workspace and your JBoss AS on different file systems (ex. workspace in /home, AS in /opt, both mounted on different partitions)
      2) create a deploy only server pointing to a folder under /opt/
      3) create a web project
      4) on the server view, choose the deploy only server, add the web project

      Result:
      an error popups that tells you that the deployment failed

      Show
      1) make sure you have your workspace and your JBoss AS on different file systems (ex. workspace in /home, AS in /opt, both mounted on different partitions) 2) create a deploy only server pointing to a folder under /opt/ 3) create a web project 4) on the server view, choose the deploy only server, add the web project Result: an error popups that tells you that the deployment failed
    • Workaround Exists
    • Hide

      define a temp folder on the same fs as the final deploy directory, in the Deploy Server Only configuration, Deployment tab.

      Show
      define a temp folder on the same fs as the final deploy directory, in the Deploy Server Only configuration, Deployment tab.

    Description

      On linux, having an web project under /home/<username>/workspace/webproject, you can not deploy it to /opt/deployfolder (assuming the rights are corrects), since, during the publish operation, the as plugin tries to rename a temporary file from one filesystem to another.

      Publishing failed
Error renaming /home/fbricon/Dev/test/temp/tmp1839894723052933744.MF to /opt/deploy/web.war/META-INF/MANIFEST.MF
Error renaming /home/fbricon/Dev/test/temp/tmp6164338251434277972.jar to /opt/deploy/web.war/WEB-INF/lib/utility.jar

      The workaround is to define a temp folder on the same fs as the final deploy directory.

      However, the average user will have no clue about how to fix it. There should be a sanity check upon Deploy Only server creation and/or error displayed on the server configuration, if deployment would fail upon invalid configuration. Providing a Quick fix might be useful, or not.

      Attachments

        1. JBIDE-8961_b.png
          31 kB
          Rob Stryker
        2. JBIDE-8961.png
          30 kB
          Rob Stryker

        Activity

          People

            rob.stryker Rob Stryker (Inactive)
            fbricon@redhat.com Fred Bricon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: