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

Remove project from server fails if server adapter is set to deploy as archive

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.2.1.M1, 3.3.0.M1
    • 3.2.0.Final
    • server
    • None
    • Hide

      1) make sure you have a WTP web app to deploy to a server adapter
      2) make sure you have a server adapter that adapts a remote server and is set to deploy in archive mode (see screenshot)
      3) have the adapter started
      4) add the webapp to the server adapter and wait until publishing is finished
      5) remove the webapp from the server adapter

      Result:
      Adapter seems to do something (a dialog with progress pops up and disappears very quickly. A message in the status bar shows up a bit long) and the webapp is removed from the server adapter. In the console you can spot the following stacktrace:

      org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
      at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:449)
      at org.eclipse.rse.internal.services.ssh.files.SftpFileService.upload(SftpFileService.java:752)
      at org.jboss.ide.eclipse.as.rse.core.archives.RSEZippedJSTPublisher.publishModule(RSEZippedJSTPublisher.java:85)
      at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77)
      at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67)
      at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1025)
      at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1115)
      at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:948)
      at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
      at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889)
      at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

      If you verify the deploy-folder on the server, you'll see that the war is still present. Accessing it shows you that the war is still running. The admin-console confirms that the webapp is still deployed and UP.

      ps. this does not happen when publishing in "exploded" mode

      Show
      1) make sure you have a WTP web app to deploy to a server adapter 2) make sure you have a server adapter that adapts a remote server and is set to deploy in archive mode (see screenshot) 3) have the adapter started 4) add the webapp to the server adapter and wait until publishing is finished 5) remove the webapp from the server adapter Result: Adapter seems to do something (a dialog with progress pops up and disappears very quickly. A message in the status bar shows up a bit long) and the webapp is removed from the server adapter. In the console you can spot the following stacktrace: org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:449) at org.eclipse.rse.internal.services.ssh.files.SftpFileService.upload(SftpFileService.java:752) at org.jboss.ide.eclipse.as.rse.core.archives.RSEZippedJSTPublisher.publishModule(RSEZippedJSTPublisher.java:85) at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1025) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1115) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:948) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) If you verify the deploy-folder on the server, you'll see that the war is still present. Accessing it shows you that the war is still running. The admin-console confirms that the webapp is still deployed and UP. ps. this does not happen when publishing in "exploded" mode
    • Hide

      no workaround found so far. You may have to remove the war manually from the server.

      Show
      no workaround found so far. You may have to remove the war manually from the server.

    Attachments

      Issue Links

        Activity

          People

            rob.stryker Rob Stryker (Inactive)
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: