January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4010: ------------------------------------- According to [~sudhirverma] (he has Windows 7 Enterprise Edition) systeminfo.exe output does not have hyper-v requirements at all. It means we should use different solution that would work for both windows 7 and 10. > DevSuite installer should check if virtualization extension is enabled > ---------------------------------------------------------------------- > > Key: JBDS-4010 > URL: https://issues.jboss.org/browse/JBDS-4010 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Sudhir Verma > Assignee: Sudhir Verma > Labels: ui > Fix For: 10.3.0.AM2 > > > Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows. > {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr > anslationExtensions" > __GENUS : 2 > __CLASS : Win32_Processor > __SUPERCLASS : > __DYNASTY : > __RELPATH : > __PROPERTY_COUNT : 2 > __DERIVATION : {} > __SERVER : > __NAMESPACE : > __PATH : > SecondLevelAddressTranslationExtensions : True > VirtualizationFirmwareEnabled : True > PSComputerName :{code} > *Update* > Better to use systeminfo command. Here is example of output: > {code}$ systeminfo > Host Name: ESKIMO-ASUS > OS Name: Microsoft Windows 10 Pro > OS Version: 10.0.14393 N/A Build 14393 > OS Manufacturer: Microsoft Corporation > OS Configuration: Standalone Workstation > OS Build Type: Multiprocessor Free > Registered Owner: eskimo > Registered Organization: > Product ID: 00330-80000-00000-AA020 > Original Install Date: 9/26/2016, 4:15:45 AM > System Boot Time: 12/19/2016, 4:23:14 PM > System Manufacturer: ASUSTeK Computer Inc. > System Model: G53SX > System Type: x64-based PC > Processor(s): 1 Processor(s) Installed. > [01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2201 Mhz > BIOS Version: American Megatrends Inc. G53SX.203, 7/5/2011 > Windows Directory: C:\WINDOWS > System Directory: C:\WINDOWS\system32 > Boot Device: \Device\HarddiskVolume1 > System Locale: en-us;English (United States) > Input Locale: en-us;English (United States) > Time Zone: (UTC-08:00) Pacific Time (US & Canada) > Total Physical Memory: 16,361 MB > Available Physical Memory: 10,150 MB > Virtual Memory: Max Size: 32,745 MB > Virtual Memory: Available: 23,976 MB > Virtual Memory: In Use: 8,769 MB > Page File Location(s): C:\pagefile.sys > Domain: WORKGROUP > Logon Server: \\ESKIMO-ASUS > Hotfix(s): 7 Hotfix(s) Installed. > [01]: KB3176935 > [02]: KB3176936 > [03]: KB3176937 > [04]: KB3199209 > [05]: KB3199986 > [06]: KB3209498 > [07]: KB3206632 > Network Card(s): 3 NIC(s) Installed. > [01]: Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter > Connection Name: Wi-Fi > DHCP Enabled: Yes > DHCP Server: 192.168.0.1 > IP address(es) > [01]: 192.168.0.101 > [02]: Realtek PCIe GBE Family Controller > Connection Name: Ethernet > Status: Media disconnected > [03]: Cisco Systems VPN Adapter for 64-bit Windows > Connection Name: Ethernet 3 > DHCP Enabled: No > IP address(es) > [01]: 10.3.230.99 > [02]: fe80::e40c:d8f4:d1f6:5959 > Hyper-V Requirements: VM Monitor Mode Extensions: Yes > Virtualization Enabled In Firmware: Yes > Second Level Address Translation: Yes > Data Execution Prevention Available: Yes > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Rob Stryker closed JBDS-4227. ----------------------------- Resolution: Rejected Not a bug ;) User error. > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 10.2.0.GA > > Attachments: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4227: ------------------------------ Fix Version/s: 10.2.0.GA > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 10.2.0.GA > > Attachments: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1009) Create an RPM installation for Fuse Tooling

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1009?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1009: ------------------------------ Summary: Create an RPM installation for Fuse Tooling (was: Create an RPM installation got Fuse Tooling) > Create an RPM installation for Fuse Tooling > ------------------------------------------- > > Key: JBTIS-1009 > URL: https://issues.jboss.org/browse/JBTIS-1009 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: Fuse IDE > Reporter: Paul Leacu > Assignee: Paul Leacu > > Details to follow - create an RPM for fuse tooling. Base off of the devstudio RPM. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4230) JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4230?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4230: ---------------------------------- Latest snapshot build (devstudio-10.3.0.AM1-v20170103-1259-B6826-installer-standalone.jar) contains a new executable: {code}devstudio-wayland{code} [~rimolive] Can you try that and see if it works for you? > JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4230 > URL: https://issues.jboss.org/browse/JBDS-4230 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Environment: Fedora 25 with Wayland > Reporter: Ricardo Martinelli Oliveira > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.3.0.AM1 > > > Workaround: Add GDK_BACKEND=x11 in devstudio.ini file to force use x11 to run JBDS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-477) RFE: support --net option in Docker run image UI [EBZ#507994]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-477: --------------------------------------- Summary: RFE: support --net option in Docker run image UI [EBZ#507994] Key: ERT-477 URL: https://issues.jboss.org/browse/ERT-477 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot There is no way of specifying --net=xxxx in the Docker Tooling UI. Perhaps a text widget could be created for additional options and these could be parsed similar to what the docker run command allows. This would allow a workaround for any obscure option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23302. ------------------------------ Resolution: Done Fixed thanks to Ryszard and Xavier. > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Assignee: Xavier Coulon > Fix For: 4.4.3.AM1 > > Attachments: image.png, stage-http.png, stage.png > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4234) <Reading Schema Error:null>

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4234?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4234. ---------------------------- Resolution: Duplicate Issue Jeff, you can't close an issue with Fixversion = LATER. Needs to be a real version (or JIRALINT will complain and spam you). Also recommended to set an assignee. Thanks! > <Reading Schema Error:null> > --------------------------- > > Key: JBDS-4234 > URL: https://issues.jboss.org/browse/JBDS-4234 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: hibernate > Reporter: kokila vishwa > Assignee: Koen Aers > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4234) <Reading Schema Error:null>

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4234?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4234: -------------------------------- Resolution: (was: Duplicate Issue) Assignee: Koen Aers > <Reading Schema Error:null> > --------------------------- > > Key: JBDS-4234 > URL: https://issues.jboss.org/browse/JBDS-4234 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: hibernate > Reporter: kokila vishwa > Assignee: Koen Aers > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4234) <Reading Schema Error:null>

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4234?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4234: ----------------------------- Fix Version/s: 10.3.0.AM1 (was: LATER) > <Reading Schema Error:null> > --------------------------- > > Key: JBDS-4234 > URL: https://issues.jboss.org/browse/JBDS-4234 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: hibernate > Reporter: kokila vishwa > Assignee: Koen Aers > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017