[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3766:
-------------------------------
Attachment: Is_Restart_Needed.png
Just saw this issue again - are we able to 100% guaranty that users will be able to run our new installer without having to perform a Windows system reboot for the Vagrant install to be successful?
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log
>
>
> See attached log files.
> After some install attempts, Vagrant fails to start. The vagrant install log reports the following:
> {code}
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2.
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
> {code}
> Is a system restart needed to ensure that the vagrant installation is successful on Windows?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-22078:
--------------------------------------
I was able to create a little test project that seems to recreate the problem sometimes. The ProcMon.exe log seems to indicate that in the failing case, the handle ot a watched directory is not closed by the file system watcher. At this moment, this looks like a race condition in the file system watcher to me. Not sure yet how to demonstrate this reliably, though.
> Error publishing war file to wildfy 8 or above on windows
> ---------------------------------------------------------
>
> Key: JBIDE-22078
> URL: https://issues.jboss.org/browse/JBIDE-22078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
> Attachments: Logfile.PML
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22135) weinre phonegap URL doesnt work
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22135?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-22135:
-------------------------------------
Even though this bug is considered to be an upstream one, I do believe that the best solution would be hosting our own weinre debug server on openshift via simple docker image. Then we would have full control of the process. According to the license file weinre is under Apache License Version 2.0 (redistribution is allowed)
> weinre phonegap URL doesnt work
> -------------------------------
>
> Key: JBIDE-22135
> URL: https://issues.jboss.org/browse/JBIDE-22135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.3.1.CR1
> Reporter: Rastislav Wagner
> Assignee: Ilya Buziuk
> Labels: upstream
> Fix For: 4.4.x
>
>
> URLs for weinre in browsersim preferences are pointing to http://debug.build.phonegap.com/client/ which doesnt work anymore. Im not sure if they moved to other location/cancelled or what
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22057:
-----------------------------------
Assignee: Rob Stryker (was: Fred Bricon)
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22137) Release openshift-restclient-java and consume it in OpenShift Eclipse plugin
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-22137:
----------------------------------------
Summary: Release openshift-restclient-java and consume it in OpenShift Eclipse plugin
Key: JBIDE-22137
URL: https://issues.jboss.org/browse/JBIDE-22137
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.3.1.CR1
JBIDE-22136 and JBIDE-22127 required changes in openshift-restclient-java. We therefore have to release a final version of the lib reference it in JBoss Tools before respin-b
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years