[jbosstools-issues] [JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007419#comment-13007419 ] 

Rob Stryker commented on JBIDE-17619:
-------------------------------------

The host shell listener is contributed by our rse.ui plugin.  The activator of our rse.ui plugin registers a host-shell listener with RSEHostShellModel, a class we own in our rse.core plugin,  to send the messages to the console view. If our rse.ui plugin has not yet been started, the listener is not registered.  

This was not replicatable for me because the server editor was open on workspace restart, and the server editor forced the loading of our rse.ui plugin to display various widgets. This meant that rse.ui was always started before I got to start the server, and so the listener was always registered, and the console always loaded. 

The real question now is when to start rse.ui plugin, or how to force it starting and at what time is most appropriate. 

Workaround:  Open the server editor. The console will begin showing updates. 

> 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)