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

First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.0.CR2
    • 4.0.1.Final
    • server
    • None
    • Hide

      1) Create an ejb project
      2) Add an ejb to it
      3) Create a new empty java project
      4) Export the ejb project as a .jar file to live in the new java project
      5) Refresh java project, see the .jar file
      6) Start eap6.0.0 server
      7) right-click jar file, mark as deployable
      8) See output showing ejb is loaded.
      9) Open in a filesystem browser the folder for eap deployments. Verify jar file exists there.
      10) Shutdown server, shutdown jbds
      11) Verify file is still in standalone/deployments. (it is)
      12) Start jbds
      13) Verify file is still in standalone/deployments. (it is)
      14) Start eap from within jbds
      15) Verify file is still in standalone/deployments, only .dodeploy marker remains in the deployments folder, but the jar has been removed.

      Show
      1) Create an ejb project 2) Add an ejb to it 3) Create a new empty java project 4) Export the ejb project as a .jar file to live in the new java project 5) Refresh java project, see the .jar file 6) Start eap6.0.0 server 7) right-click jar file, mark as deployable 8) See output showing ejb is loaded. 9) Open in a filesystem browser the folder for eap deployments. Verify jar file exists there. 10) Shutdown server, shutdown jbds 11) Verify file is still in standalone/deployments. (it is) 12) Start jbds 13) Verify file is still in standalone/deployments. (it is) 14) Start eap from within jbds 15) Verify file is still in standalone/deployments, only .dodeploy marker remains in the deployments folder, but the jar has been removed.
    • Hide
      On the first IDE and server restart or the first workspace and server restart after marking a new file as deployable, the file was no longer deployed. At the session restart, there was no check to ensure the deployed file IDs matched those in the previous session. This issue has been resolved by ensuring that the file is properly found during the next session and now marking a new file as deployable persists from one session to the next.
      Show
      On the first IDE and server restart or the first workspace and server restart after marking a new file as deployable, the file was no longer deployed. At the session restart, there was no check to ensure the deployed file IDs matched those in the previous session. This issue has been resolved by ensuring that the file is properly found during the next session and now marking a new file as deployable persists from one session to the next.
    • Documented as Resolved Issue

      After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly.

      Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted.

      After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar.

      Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable".

            rob.stryker Rob Stryker (Inactive)
            rhn-support-dstephan David Stephan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: