[ https://issues.jboss.org/browse/JBIDE-8449?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8449: ------------------------------------ Steps to Reproduce: 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 was: 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8449?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-8449. -------------------------------- Fix Version/s: 3.2.1 3.3.0.M1 Resolution: Done Committed to trunk and branch... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira