[jbosstools-issues] [JBoss JIRA] (JBIDE-11456) Server stopping forever if started forcefully as a second/colliding server and then stopped
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Tue Apr 10 03:33:48 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker resolved JBIDE-11456.
---------------------------------
Resolution: Done
committed the fix. It was fairly easy, just needed to force stop if the graceful stop failed.
> Server stopping forever if started forcefully as a second/colliding server and then stopped
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-11456
> URL: https://issues.jboss.org/browse/JBIDE-11456
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Mac OS X 10.7 Lion
> JBT 3.3.x nightly 2012-04-03 (H4468)
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 3.3.0.Beta3
>
>
> This is my scenario:
> 1. Start AS7.1.1 from Terminal
> 2. Add EAP 6 ER4.1 in JBT
> 3. Try to start EAP 6
> 4. You will be warned that a server is already running on port 8080 - start anyway
> 5. Server will start with errors - that is expected
> 6. Select the EAP 6 server in Server view and click Stop
> 7. The manually started AS7.1.1 will be stopped - don't know if we can do anything about it
> 8. The EAP 6 server in JBT will be in the state "Stopping" forever until timeout is hit (several minutes) - that is bad
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list