[JBoss JIRA] (ERT-510) reloadConnections executing in UI thread can cause hang when switch to Docker Tooling perspective [EBZ#517143]
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-510?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg updated ERT-510:
--------------------------------
Sprint: devex #132 May 2017
> reloadConnections executing in UI thread can cause hang when switch to Docker Tooling perspective [EBZ#517143]
> --------------------------------------------------------------------------------------------------------------
>
> Key: ERT-510
> URL: https://issues.jboss.org/browse/ERT-510
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: Docker, bzira
>
> DockerConnectionManager.getInstance() will end up calling reloadConnections if the singleton has not yet been created (likely when a user opens the perspective for the first time). The call exists in various createControl() methods so the reloading of connections could take place under the UI thread.
> We should guard against this by having the logic execute under a background job that populates the Explorer view as it completes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ERT-510) reloadConnections executing in UI thread can cause hang when switch to Docker Tooling perspective [EBZ#517143]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-510:
---------------------------------------
Summary: reloadConnections executing in UI thread can cause hang when switch to Docker Tooling perspective [EBZ#517143]
Key: ERT-510
URL: https://issues.jboss.org/browse/ERT-510
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
DockerConnectionManager.getInstance() will end up calling reloadConnections if the singleton has not yet been created (likely when a user opens the perspective for the first time). The call exists in various createControl() methods so the reloading of connections could take place under the UI thread.
We should guard against this by having the logic execute under a background job that populates the Explorer view as it completes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1082) SwitchYard specific updates to separate it from Fuse proper.
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1082?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick commented on JBTIS-1082:
------------------------------------------
[~lhein] That's true, but we still have to move the SY-specific doc bits out of the Fuse docs and back into some SY-specific place I think, based on what Paul is asking for. :)
> SwitchYard specific updates to separate it from Fuse proper.
> ------------------------------------------------------------
>
> Key: JBTIS-1082
> URL: https://issues.jboss.org/browse/JBTIS-1082
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: switchyard
> Reporter: Paul Leacu
> Assignee: Brian Fitzpatrick
>
> Separate SwitchYard from Fuse Tooling proper. It should exist as a independent jar bundle.
> Initial effort: - update to Oxygen JBTIS target platform
> 1. Modify that org.switchyard.tools.bpmn2.feature requirement to be org.eclipse.bpmn2.modeler.feature.group [1.3.0,1.4.0]
> 2. Pick up 4.5.0.AM1-SNAPSHOT as your JBTIS TP
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24522) Incremental deployment for WF11/EAP7.1 - only redeploy if necessary
by Martin Malina (JIRA)
Martin Malina created JBIDE-24522:
-------------------------------------
Summary: Incremental deployment for WF11/EAP7.1 - only redeploy if necessary
Key: JBIDE-24522
URL: https://issues.jboss.org/browse/JBIDE-24522
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.5.0.AM1
Reporter: Martin Malina
Assignee: Rob Stryker
As discussed with Rob, JBIDE-23784 added support for incremental deployment over management API for WildFly 11 / EAP 7.1. But it does not actually deploy incrementally. It will still redeploy the whole module on the server. The improvement that was done in that JIRA is that now the whole project is not copied over to the server every time there is a change - now only the changes are being sent. But the whole module is still redeployed.
So I think it's worth looking into if it's possible to improve this further so that the module is not always redeployed on the server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24521) Errors publishing a large deployment to a remote server (EAP 7.1 management)
by Martin Malina (JIRA)
Martin Malina created JBIDE-24521:
-------------------------------------
Summary: Errors publishing a large deployment to a remote server (EAP 7.1 management)
Key: JBIDE-24521
URL: https://issues.jboss.org/browse/JBIDE-24521
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.5.0.AM1
Reporter: Martin Malina
I tried to verify EAP 7.1 incremental deployment (JBIDE-23784).
So I first deployed a simple dynamic web project over management API to a remote EAP 7.1 (on a remote machine). Everything fine so far.
Then I just copied a big jar (devstudio installer) into the WebContent dir of the project. Then I did a Refresh of the project in Eclipse and I immediately got an error:
{code}
Could not publish to the server.
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:68)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.waitFor(WildFly11Manager.java:231)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.incrementalPublish(WildFly11Manager.java:601)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.incrementalPublish(WildFly11ManagerService.java:201)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.incrementalPublish(JBoss7ManagerServiceProxy.java:134)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController$IncrementalManagementPublishRunner.incrementalPublish(ManagementPublishController.java:530)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.incrementalPublish(ManagementPublishController.java:474)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:257)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:281)
at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:62)
at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:69)
at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:94)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:65)
... 15 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3236)
at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:52)
at org.jboss.as.controller.client.impl.InputStreamEntry$InMemoryEntry.initialize(InputStreamEntry.java:76)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:220)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{code}
The server adapter showed [Republish]. So I tried to do a full publish, but that kind of failed. It first showed 19 %, now it's been at 29 % for 5 minutes and nothing seems to be happening. The server adapter says [Started, Publishing...] and the module says [Republish]. And I can't even stop the server, it's stuck.
I restarted the IDE. Killed the EAP server on the remote host. Started the server again in the IDE. It showed my module is started. The index worked, the jar was not found. So now I did a full publish on the module. I could see that something was being sent over the network. Then the traffic was over and it was at 33 % for a while and finally it finished successfully this time. So at least that. Then I could add another jsp and it redeployed the module without having to send over the big file again. So at least that worked now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24521) Errors publishing a large deployment to a remote server (EAP 7.1 management)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24521?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-24521:
-------------------------------------
Assignee: Rob Stryker
> Errors publishing a large deployment to a remote server (EAP 7.1 management)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24521
> URL: https://issues.jboss.org/browse/JBIDE-24521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I tried to verify EAP 7.1 incremental deployment (JBIDE-23784).
> So I first deployed a simple dynamic web project over management API to a remote EAP 7.1 (on a remote machine). Everything fine so far.
> Then I just copied a big jar (devstudio installer) into the WebContent dir of the project. Then I did a Refresh of the project in Eclipse and I immediately got an error:
> {code}
> Could not publish to the server.
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:68)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.waitFor(WildFly11Manager.java:231)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.incrementalPublish(WildFly11Manager.java:601)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.incrementalPublish(WildFly11ManagerService.java:201)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.incrementalPublish(JBoss7ManagerServiceProxy.java:134)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController$IncrementalManagementPublishRunner.incrementalPublish(ManagementPublishController.java:530)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.incrementalPublish(ManagementPublishController.java:474)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:257)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:281)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:62)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:69)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:94)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:65)
> ... 15 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3236)
> at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
> at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
> at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:52)
> at org.jboss.as.controller.client.impl.InputStreamEntry$InMemoryEntry.initialize(InputStreamEntry.java:76)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:220)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> The server adapter showed [Republish]. So I tried to do a full publish, but that kind of failed. It first showed 19 %, now it's been at 29 % for 5 minutes and nothing seems to be happening. The server adapter says [Started, Publishing...] and the module says [Republish]. And I can't even stop the server, it's stuck.
> I restarted the IDE. Killed the EAP server on the remote host. Started the server again in the IDE. It showed my module is started. The index worked, the jar was not found. So now I did a full publish on the module. I could see that something was being sent over the network. Then the traffic was over and it was at 33 % for a while and finally it finished successfully this time. So at least that. Then I could add another jsp and it redeployed the module without having to send over the big file again. So at least that worked now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4403) An error when installing Devstudio 10.4.0.GA from Marketplace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4403?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4403:
----------------------------------
"It occurs due to conflicts between the plugins that Eclipse is trying to install during the JBoss Developer Studio installation."
That's not technically true. It occurs because the Eclipse product includes an older version of a required plugin on which JBoss Developer Studio depends (org.eclipse.m2e.feature 1.7.0), so p2 needs to break the product's install definition up into smaller pieces to allow the requirement to be updated to 1.7.1.
So it's less about a "conflict" and more about the way the Eclipse product is defined, using an older version of m2e.
> An error when installing Devstudio 10.4.0.GA from Marketplace
> -------------------------------------------------------------
>
> Key: JBDS-4403
> URL: https://issues.jboss.org/browse/JBDS-4403
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 10.4.0.GA
> Environment: Eclipse Neon.3 for JavaEE Developers
> Reporter: Andrej Podhradsky
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> The following error occurs when installing Devstudio 10.4.0.GA from Marketplace
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748)
> Software currently installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933)
> Only one of the following can be installed at once:
> Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933)
> Maven Project Model Edit Bundle 1.7.1.20161104-1805 (org.eclipse.m2e.model.edit 1.7.1.20161104-1805)
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748)
> To: com.jboss.devstudio.core.rpmdeps.feature.feature.group [10.4.0.v20170504-1343]
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (Feature Dependencies) 10.4.0.v20170504-1343 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 10.4.0.v20170504-1343)
> To: org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805
> Cannot satisfy dependency:
> From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933)
> To: org.eclipse.m2e.model.edit [1.7.0.20160603-1933]
> Cannot satisfy dependency:
> From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805)
> To: org.eclipse.m2e.model.edit [1.7.1.20161104-1805]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months