[jbosstools-issues] [JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
Rob Stryker (JIRA)
issues at jboss.org
Tue Apr 5 13:17:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186990#comment-13186990 ]
Rob Stryker commented on JBIDE-22113:
-------------------------------------
I'll look into it, but, just to be clear, this isn't the tools sending any force command at all. Obviously we're running the shutdown command, so we might not be providing everything vagrant needs (whether in environment or otherwise).
Aside from the different output, is there any noticable impact on anything? Does state not get persisted properly? Etc? We'll look into these details.
> CDK shutdown always goes to Forcing shutdown of VM on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-22113
> URL: https://issues.jboss.org/browse/JBIDE-22113
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> On OS X, when I stop CDK in JBDS, I get this in the console:
> ==> default: Unregistering box with vagrant-registration...
> ==> default: Attempting graceful shutdown of VM...
> And a few seconds later, the server adapter shows "Stopped".
> Today while testing on Windows I noticed that it behaves differently.
> It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
> ==> default: Forcing shutdown of VM...
> After this, the server adapter shows "Stopped".
> So for some unknown reason, on Windows the graceful shutdown fails to work.
> This is JBDS+CDK installed from the latest windows installer (built April 4th).
> It would be good to see if others see this on Windows as well or not.
> Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list