[JBoss JIRA] (JBIDE-19350) Deployment/transfer operations cannot be canceled
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19350.
---------------------------------
This has been verified already, closing.
> Deployment/transfer operations cannot be canceled
> -------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18907.
---------------------------------
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18907:
---------------------------------------
I just tried it now and what I don't like too much about it is that it will show Starting until time out is reached. I understand that this is because it works the same way as when the EAP server is actually started by the tooling - the time out is to ensure that the server has enough time to get started. This would be not really needed - when you click Start, you will typically have the server already started, so it might make more sense to get and error immediately if the poller can't reach the server.
But I guess it's good enough.
Once I started the server with the management port exposed, it worked as expected and I could deploy a module.
Verified in JBDS 9.0.0.Alpha2 B24 BYOE. Closing.
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19324) Arquillian core freezes Eclipse startup
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19324?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19324.
-----------------------------------
Verified JBDS 9.0.0.alpha2
> Arquillian core freezes Eclipse startup
> ---------------------------------------
>
> Key: JBIDE-19324
> URL: https://issues.jboss.org/browse/JBIDE-19324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
> Attachments: dump.txt, restart.ogv
>
>
> When I have arquillian.xml with at least one container defined and I open it with Arquillian editor and restart Eclipse, the Eclipse wont start and it freezes on loading arquillian core plugin (see screencast).
> I am also attaching thread dump (thanks to [~rhopp])
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19508) Compile failed in org.jboss.tools.jmx.ui and org.jboss.tools.jmx.jvmmonitor.tools
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19508?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19508.
---------------------------------
Seems to be fine in jenkins now. Closing.
> Compile failed in org.jboss.tools.jmx.ui and org.jboss.tools.jmx.jvmmonitor.tools
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-19508
> URL: https://issues.jboss.org/browse/JBIDE-19508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/715/console}
> 00:02:37.945 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.jmx.ui: Compilation failure: Compilation failure:
> 00:02:37.946 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/ConnectDebuggerAction.java:[45]
> 00:02:37.947 [ERROR] return RemoteDebugActivator.isRemoteDebuggerConnected(wrapper.getDebugHost(), wrapper.getDebugPort());
> 00:02:37.947 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.947 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.948 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/ConnectDebuggerAction.java:[62]
> 00:02:37.948 [ERROR] ILaunchConfiguration config = RemoteDebugActivator.createOrGetDefaultLaunchConfiguration(
> 00:02:37.949 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.949 [ERROR] The method createOrGetDefaultLaunchConfiguration(String, String, IJavaProject, IJavaProject[]) is undefined for the type RemoteDebugActivator
> 00:02:37.949 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/views/navigator/ActionProvider.java:[121]
> 00:02:37.950 [ERROR] if( RemoteDebugActivator.isRemoteDebuggerConnected(debuggable.getDebugHost(), debuggable.getDebugPort())) {
> 00:02:37.951 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.951 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.951 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/DisconnectDebuggerAction.java:[35]
> 00:02:37.952 [ERROR] return RemoteDebugActivator.isRemoteDebuggerConnected(wrapper.getDebugHost(), wrapper.getDebugPort());
> 00:02:37.952 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.953 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.953 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/DisconnectDebuggerAction.java:[39]
> 00:02:37.954 [ERROR] ILaunch l = RemoteDebugActivator.getExistingRemoteDebugLaunch(con.getDebugHost(), con.getDebugPort());
> 00:02:37.954 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.955 [ERROR] The method getExistingRemoteDebugLaunch(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.955 [ERROR] 5 problems (5 errors)
> 00:02:37.955 [ERROR] -> [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19343:
-----------------------------------------
[~mickael_istria] Is it all fixed? Can we close this issue?
> integration tests do not fetch their required runtimes if not present in the cache folder
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build, server
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month