[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics
by Jesper Skov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ]
Jesper Skov commented on JBIDE-23658:
-------------------------------------
1. Unpack archive in workspace root
2. Run 'gradlew eclipse' in dk.may.work folder with JDK8 on path
3. Import projects into Eclipse
4. Select dk.may.work.ejb project in Project Explorer
5. Ctrl-n -> Hibernate Console Configuration
Wized comes up with "Could not create JPA based Configuration"
One time I tried the above, it worked.
But then I assigned a JBoss EAP 6.4 Runtime to the JPA facet, and then the wizard failed with same message.
If the Hibernate Console Configuration is created from Run Configurations instead, it seems to work with this test proejct.
At least until the JBoss EAP rutime is assigned to the JPA facet.
Then this also fails.
There are many factors that affect how the JPA / Hibernate plugin works.
And some of those are clearly problematic in our development.
When all potential causes of problems result in the same message, it is really hard to make sense of.
I would dearly love to be able to see some logging from the plugin.
Please tell me that is possible.
[^empty-clean.zip]
> Hibernate console configuration wizard problems - and no way to get specifics
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23658
> URL: https://issues.jboss.org/browse/JBIDE-23658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.2.Final
> Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle
> Reporter: Jesper Skov
> Assignee: Koen Aers
> Attachments: empty-clean.zip
>
>
> Creating a Hibernate Console Configuration using the wizard fails for most of our projects.
> All the feedback we have is the text in red: "Could not create JPA based Configuration"
> I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log.
> I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file.
> We wonder if maybe the plugin/perspective is just dead (or dying).
> The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[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 reassigned JBDS-4010:
-----------------------------------
Assignee: Sudhir Verma (was: Denis Golovin)
> 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)
9 years, 3 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3869:
--------------------------------
Sprint: devex #125 December 2016
> platform installer should check/warn if Hyper-V is already enabled.
> -------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[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 updated JBDS-4010:
--------------------------------
Sprint: devex #125 December 2016
> 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: Denis Golovin
> 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)
9 years, 3 months
[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 edited comment on JBDS-4010 at 12/22/16 1:47 AM:
---------------------------------------------------------------
systeminfo command should be used to get virtualization extension status. Implementation for windows should be in [browser/services/Platform.js#isVirtualizationEnabled()|https://github.com...] method. It expects to return Promise instance.
was (Author: dgolovin):
systeminfo command should be used to get virtualization extension status. Implementation for windows should be in browser/services/Platform.js#isVirtualizationEnabled() method. It expects to return Promise instance.
> 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: Denis Golovin
> 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)
9 years, 3 months
[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:
-------------------------------------
systeminfo command should be used to get virtualization extension status. Implementation for windows should be in browser/services/Platform.js#isVirtualizationEnabled() method. It expects to return Promise instance.
> 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: Denis Golovin
> 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)
9 years, 3 months