[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17619.
---------------------------------
Verified in JBDS 8.0.0.CR2 B286
> Console for remote server disappears when workspace is switched
> ---------------------------------------------------------------
>
> Key: JBIDE-17619
> URL: https://issues.jboss.org/browse/JBIDE-17619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped.
> The only thing that helped me here was to delete the server and create a new one.
> I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18347) Changing server profile to management does not change pollers
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18347?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18347.
---------------------------------
Verified in JBDS 8.0.0.CR2 B286
> Changing server profile to management does not change pollers
> -------------------------------------------------------------
>
> Key: JBIDE-18347
> URL: https://issues.jboss.org/browse/JBIDE-18347
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> I just noticed that when you create a server with filesystem operations and then change it to use management api, it will not change the poller to management, but it will stay with Web Poller. Whereas when you create a new server with management profile, it will use the management pollers.
> Feel free to set the Fix version yourself.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18455) UI freeze when using server view on remote servers
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18455?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18455.
---------------------------------
OK, I was able to verify this now on my home network. There are delays when accessing the server context menu in CR1, but not anymore with CR2. Verified in JBDS 8.0.0.CR2 B286
> UI freeze when using server view on remote servers
> --------------------------------------------------
>
> Key: JBIDE-18455
> URL: https://issues.jboss.org/browse/JBIDE-18455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> create a remote server
> start it
> now when trying to use the server view with this server things freezes for several seconds.
> stacktrace shows it is blocking the main thread.
> full jstacktrace here: https://gist.github.com/maxandersen/51575583ba5877eb48ec
> important part here:
> {code}
> "main" prio=5 tid=0x0000000102870000 nid=0x513 in Object.wait() [0x00007fff5fbf9000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007f492b908> (a java.lang.Object)
> at org.xnio.AbstractIoFuture.await(AbstractIoFuture.java:101)
> - locked <0x00000007f492b908> (a java.lang.Object)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:101)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> - locked <0x00000007f492a9a0> (a org.jboss.as.protocol.ProtocolConnectionManager)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> - locked <0x00000007f491a368> (a org.jboss.as.controller.client.impl.RemotingModelControllerClient)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> 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)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getServerState(AS71Manager.java:266)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.getServerState(JBoss71ManagerService.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:112)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublish(ManagementPublishController.java:124)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297)
> at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1215)
> at org.eclipse.wst.server.ui.internal.view.servers.PublishAction.accept(PublishAction.java:40)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months