6:33 a.m.
Cleaning published webapp fails on 3rd (and subsequent) attempts
----------------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR2 (tentative)
Reporter: Andre Dietisheim
Assignee: Rob Stryker
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8422) Cleaning published webapp fails on 3rd (and subsequent) attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8422:
------------------------------------
Fix Version/s: 3.2.1
3.3.0.M1
Cleaning published webapp fails on 3rd (and subsequent) attempts
----------------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR2 (tentative)
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8422) Cleaning published webapp fails on 3rd (and subsequent) attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8422:
------------------------------------
Steps to Reproduce:
1) make sure that you have a (WTP) webapp to deploy to a server adapter
2) launch a deltacloud instance and choose to create RSE and the server adapter
3) as soon as the adapter is created, start it
4) add your webapp to it
5) wait until the publishing has completed
6) clean the server adapter
7 (repeat step 6 twice)
Result:
Unfortunately there's no report in the eclipse UI that things failed. The adapter
still says that its started and synchronized.
You see error outputs in the console "failed to copy
/opt/jboss-as/server/default/deploy/<your-weapp>" and the following
stack-trace:
org.eclipse.rse.services.files.RemoteFileException: Error creating Terminal
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalShell.<init>(SshTerminalShell.java:127)
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalService.launchTerminal(SshTerminalService.java:41)
at
org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65)
at
org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at
org.jboss.ide.eclipse.as.rse.core.RSELaunchDelegate.launchCommandNoResult(RSELaunchDelegate.java:126)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.startDeploymentScanner(RSEPublishMethod.java:77)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishFinish(RSEPublishMethod.java:70)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:59)
at
org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.publishFinish(JBossServerBehavior.java:112)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:963)
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)
The above exception wraps a JSchException which says "channel is not opened".
Once things start failing you wont be able to publish to the server any more. Even
creating a new server adapter to your (remote) server will not work.
Weird enough: If you go to the "Remote Systems" view you'll notice that
you're still able to browse the server filesystem. But the terminal and console
services are not working any more. Launching a terminal ends with a stacktrace in the
console:
Exception in thread "Thread-261" java.lang.NullPointerException
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.readDataForever(RSETerminalConnectionThread.java:99)
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.run(RSETerminalConnectionThread.java:70
was:
1) make sure that you have a (WTP) webapp to deploy to a server adapter
2) launch a deltacloud instance and choose to create RSE and the server adapter
3) as soon as the adapter is created, start it
4) add your webapp to it
5) wait until the publishing has completed
6) clean the server adapter
7 (repeat step 6 twice)
Result:
Unfortunately there's no report in the eclipse UI that things failed. The adapter
still says that its started and synchronized.
You see error outputs in the console "failed to copy
/opt/jboss-as/server/default/deploy/<your-weapp>" and the following
stack-trace:
org.eclipse.rse.services.files.RemoteFileException: Error creating Terminal
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalShell.<init>(SshTerminalShell.java:127)
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalService.launchTerminal(SshTerminalService.java:41)
at
org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65)
at
org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at
org.jboss.ide.eclipse.as.rse.core.RSELaunchDelegate.launchCommandNoResult(RSELaunchDelegate.java:126)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.startDeploymentScanner(RSEPublishMethod.java:77)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishFinish(RSEPublishMethod.java:70)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:59)
at
org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.publishFinish(JBossServerBehavior.java:112)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:963)
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)
Cleaning published webapp fails on 3rd (and subsequent) attempts
----------------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR2 (tentative)
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8422) Cleaning published webapp fails on 3rd (and subsequent) attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8422:
------------------------------------
Workaround Description:
1) go to the "Remote Systems" view
2) pick the remote system that is used by your server adapter
3) Disconnect it
4) (Re-)Connect it
Cleaning published webapp fails on 3rd (and subsequent) attempts
----------------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR2 (tentative)
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:04 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8422) Cleaning published webapp fails on and subsequent attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8422:
------------------------------------
Summary: Cleaning published webapp fails on and subsequent attempts (was:
Cleaning published webapp fails on 3rd (and subsequent) attempts)
Steps to Reproduce:
1) make sure that you have a (WTP) webapp to deploy to a server adapter
2) launch a deltacloud instance and choose to create RSE and the server adapter
3) as soon as the adapter is created, start it
4) add your webapp to it
5) wait until the publishing has completed
6) clean the server adapter
7 (repeat step 6 twice at least)
Result:
Unfortunately there's no report in the eclipse UI that things failed. The adapter
still says that its started and synchronized.
You see error outputs in the console "failed to copy
/opt/jboss-as/server/default/deploy/<your-weapp>" and the following
stack-trace:
org.eclipse.rse.services.files.RemoteFileException: Error creating Terminal
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalShell.<init>(SshTerminalShell.java:127)
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalService.launchTerminal(SshTerminalService.java:41)
at
org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65)
at
org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at
org.jboss.ide.eclipse.as.rse.core.RSELaunchDelegate.launchCommandNoResult(RSELaunchDelegate.java:126)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.startDeploymentScanner(RSEPublishMethod.java:77)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishFinish(RSEPublishMethod.java:70)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:59)
at
org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.publishFinish(JBossServerBehavior.java:112)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:963)
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)
The above exception wraps a JSchException which says "channel is not opened".
Once things start failing you wont be able to publish to the server any more. Even
creating a new server adapter to your (remote) server will not work.
Weird enough: If you go to the "Remote Systems" view you'll notice that
you're still able to browse the server filesystem. But the terminal and console
services are not working any more. Launching a terminal ends with a stacktrace in the
console:
Exception in thread "Thread-261" java.lang.NullPointerException
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.readDataForever(RSETerminalConnectionThread.java:99)
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.run(RSETerminalConnectionThread.java:70
was:
1) make sure that you have a (WTP) webapp to deploy to a server adapter
2) launch a deltacloud instance and choose to create RSE and the server adapter
3) as soon as the adapter is created, start it
4) add your webapp to it
5) wait until the publishing has completed
6) clean the server adapter
7 (repeat step 6 twice)
Result:
Unfortunately there's no report in the eclipse UI that things failed. The adapter
still says that its started and synchronized.
You see error outputs in the console "failed to copy
/opt/jboss-as/server/default/deploy/<your-weapp>" and the following
stack-trace:
org.eclipse.rse.services.files.RemoteFileException: Error creating Terminal
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalShell.<init>(SshTerminalShell.java:127)
at
org.eclipse.rse.internal.services.ssh.terminal.SshTerminalService.launchTerminal(SshTerminalService.java:41)
at
org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65)
at
org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at
org.jboss.ide.eclipse.as.rse.core.RSELaunchDelegate.launchCommandNoResult(RSELaunchDelegate.java:126)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.startDeploymentScanner(RSEPublishMethod.java:77)
at
org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishFinish(RSEPublishMethod.java:70)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:59)
at
org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.publishFinish(JBossServerBehavior.java:112)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:963)
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)
The above exception wraps a JSchException which says "channel is not opened".
Once things start failing you wont be able to publish to the server any more. Even
creating a new server adapter to your (remote) server will not work.
Weird enough: If you go to the "Remote Systems" view you'll notice that
you're still able to browse the server filesystem. But the terminal and console
services are not working any more. Launching a terminal ends with a stacktrace in the
console:
Exception in thread "Thread-261" java.lang.NullPointerException
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.readDataForever(RSETerminalConnectionThread.java:99)
at
org.eclipse.rse.internal.terminals.ui.views.RSETerminalConnectionThread.run(RSETerminalConnectionThread.java:70
Cleaning published webapp fails on and subsequent attempts
----------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR2 (tentative)
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8422) Cleaning published webapp fails on and subsequent attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8422.
--------------------------------
Resolution: Duplicate Issue
I believe the root cause here is a duplicate of
https://issues.jboss.org/browse/JBIDE-8438, thread overload due to unclosed shells
Cleaning published webapp fails on and subsequent attempts
----------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Final
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8422) Cleaning published webapp fails on and subsequent attempts
[
https://issues.jboss.org/browse/JBIDE-8422?page=com.atlassian.jira.plugin...
]
Martin Malina closed JBIDE-8422.
--------------------------------
I couldn't reproduce this (I tried cleaning the server many times), so I'm closing
the issue. This is not exactly a duplicate of the other issue - the other issue probably
still holds true - if the error occurred, I wouldn't be able to see it through the UI
I assume.
Verified in jbosstools-3.2_stable_branch.aggregate-Update-2011-05-06_04-07-34-H806.zip .
Cleaning published webapp fails on and subsequent attempts
----------------------------------------------------------
Key: JBIDE-8422
URL: https://issues.jboss.org/browse/JBIDE-8422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Final
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.2.1.M1, 3.3.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5422
days inactive
5502
days old
jbosstools-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Andre Dietisheim (JIRA) -
Martin Malina (JIRA)
-
Rob Stryker (JIRA)