[jbosstools-issues] [JBoss JIRA] (JBIDE-14108) EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable

[Darryl Miles (JIRA)]

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

Darryl Miles edited comment on JBIDE-14108 at 6/20/13 4:13 AM:
---------------------------------------------------------------

The highest JBoss Tools I can see in Eclipse feature list is 3.6.0.Final-v20130327 (for Hibernate Tools).
There is also 3.4.0 and 2.4.1 and 1.4.0 in JBoss Eclipse features.  All dated as above.  I do not know which "JBoss Tooling" production version this related to, but I don't think it is 4.1.x, I also think I am using the correct and latest version for Juno.

I can try Kepler in a few weeks, after release.


Well I just took a look at the project I am developing and I know the EAR is started on the local EAP6.1 instance, but in the Eclipse UI only the 'Start' action is possible and the state indicator against the EAR module is [Stopped, Synchronized].

When I click 'Start' it does make it undeploy and redeploy, and the 'Restart' button is now possible to use.  The 'Stop' button is not available (greyed out).  Also the status continues to say [Starting, Synchronized].  Indicating it has not completed startup, but the JBoss EAP 6.1 log output says it has completed a successful deployment.


My workaround has been to use the "Full Publish" option.  This causes a redeploy to take place but after it is done the UI information goes back to a rational state ([Started, Synchronized] with the Stop and Restart buttons available).  It is not forever stuck at '[Starting, Synchronized]'.


I think the "Stop" status should be available even when in 'Starting' state.  If it is not possible to do it right away, the UI should queue it internally and send the Stop request as soon as possible.  Ideally the pending Stop request should cause the UI to start taking counter measures to ensure the JBoss AS runtime makes process towards a stop.  Such as warning the user when it won't stop, offering to kill process, whatever.
                
      was (Author: dlmiles):
    The highest JBoss Tools I can see in Eclipse feature list is 3.6.0.Final-v20130327 (for Hibernate Tools).
There is also 3.4.0 and 2.4.1 and 1.4.0 in JBoss Eclipse features.  All dated as above.  I do not know which "JBoss Tooling" production version this related to, but I don't think it is 4.1.x, I also think I am using the correct and latest version for Juno.

I can try Kepler in a few weeks, after release.


Well I just took a look at the project I am developing and I know the EAR is started on the local EAP6.1 instance, but in the Eclipse UI only the 'Start' action is possible and the state indicator against the EAR module is [Stopped, Synchronized].

When I click 'Start' it does make it undeploy and redeploy, and the 'Restart' button is now possible to use.  The 'Stop' button is not available (greyed out).  Also the status continues to say [Starting, Synchronized].  Indicating it has not completed startup, but the JBoss EAP 6.1 log output says it has completed a successful deployment.


My workaround has been to use the "Full Publish" option.  This causes a redeploy to take place but after it is done the UI information goes back to a rational state ([Started, Synchronized] with the Stop and Restart buttons available).  It is not forever stuck at '[Starting, Synchronized]'.

                  
> EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-14108
>                 URL: https://issues.jboss.org/browse/JBIDE-14108
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.0.Alpha1
>         Environment: Windows7 EAP6.1 Juno-SR2
>            Reporter: Darryl Miles
>            Assignee: Rob Stryker
>             Fix For: 4.1.x
>
>
> EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable.
> I configure and start EAP 6.1.
> While it is running I use Add/Remove... to add an EAR project (maybe any deployable project will work)
> I wait for it to bootup.
> Once booted I use the action "Stop" or "Restart".
> This action occurs but the state of the dialog is not update.
> What should happen is the "Start" button should become available again.
> The "Restart" action seems to always be available.  But even using it when it was stopped does not result in the "Stop" action from being available again.
> Only the first use of adding the module the buttons work as expected.
> I think the server runtime connector should have be able to guess the current status of each module by looking for all the files expected:
> *.deployed (means started, so Restart and Start are valid action)
> *.isdeploying (means it is on the way up)
> *.undeployed (means stopped)
> *.isundeploying (I never saw this before, but I guess it may exist)
> *.failed (means stopped)
> No file found (means stopped)
> This means it is possible to poll the state of these files always and update accordingly.
> Also there is no ICON picture next to the Restart next to the per-module setting.  I am sure there is one around somewhere and the colour and grey of this icon give good indicator the action is possible or not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira