[JBoss JIRA] (JBDS-4768) org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4768?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4768:
----------------------------------
Do we have the issue with upstream ?
> org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4768
> URL: https://issues.jboss.org/browse/JBDS-4768
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central-update, updatesite
> Affects Versions: 12.11.0.GA
> Environment: Fedora 29, openjdk 11
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.x
>
>
> {code}
> eclipse.buildId=4.11.0.I20190307-0500
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> org.eclipse.debug.ui
> Error
> Fri Mar 29 16:03:31 CET 2019
> org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
> eclipse.buildId=4.11.0.I20190307-0500
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> org.eclipse.ui
> Error
> Fri Mar 29 16:17:03 CET 2019
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4699)
> at org.eclipse.swt.SWT.error(SWT.java:4614)
> at org.eclipse.swt.SWT.error(SWT.java:4585)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:530)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467)
> at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736)
> at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBDS-4768) org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
by Ondrej Dockal (Jira)
Ondrej Dockal created JBDS-4768:
-----------------------------------
Summary: org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
Key: JBDS-4768
URL: https://issues.jboss.org/browse/JBDS-4768
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Bug
Components: central-update, updatesite
Affects Versions: 12.11.0.GA
Environment: Fedora 29, openjdk 11
Reporter: Ondrej Dockal
Assignee: Jeff MAURY
Fix For: 12.x
{code}
eclipse.buildId=4.11.0.I20190307-0500
java.version=11.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
org.eclipse.debug.ui
Error
Fri Mar 29 16:03:31 CET 2019
org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory
eclipse.buildId=4.11.0.I20190307-0500
java.version=11.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
org.eclipse.ui
Error
Fri Mar 29 16:17:03 CET 2019
Unhandled event loop exception
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4699)
at org.eclipse.swt.SWT.error(SWT.java:4614)
at org.eclipse.swt.SWT.error(SWT.java:4585)
at org.eclipse.swt.widgets.Widget.error(Widget.java:530)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467)
at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736)
at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBIDE-26603) NPE at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46)
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26603:
-------------------------------------
Summary: NPE at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46)
Key: JBIDE-26603
URL: https://issues.jboss.org/browse/JBIDE-26603
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.11.0.Final
Environment: Fedora 29, Java 11
Reporter: Ondrej Dockal
Assignee: Jeff MAURY
{code}
!ENTRY org.eclipse.ui.navigator 4 2 2019-03-29 15:07:56.266
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getCachedVmModel(RemoteDebugActivator.java:143)
at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.getVmModel(JvmConnectionWrapper.java:244)
at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.debugEnabled(JvmConnectionWrapper.java:260)
at org.jboss.tools.jmx.ui.internal.views.navigator.ActionProvider.fillContextMenu(ActionProvider.java:119)
at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:228)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:222)
at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:177)
at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:258)
at org.eclipse.ui.navigator.CommonNavigatorManager.lambda$1(CommonNavigatorManager.java:270)
at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:342)
at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:473)
at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:468)
at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:500)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:259)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5783)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1411)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1420)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1196)
at org.eclipse.reddeer.core.handler.MenuHandler.sendShowUI(MenuHandler.java:119)
at org.eclipse.reddeer.core.handler.MenuHandler$1.run(MenuHandler.java:59)
at org.eclipse.reddeer.core.handler.MenuHandler$1.run(MenuHandler.java:1)
at org.eclipse.reddeer.common.util.Display$ErrorHandlingRunnable.run(Display.java:162)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at org.eclipse.reddeer.jdt.junit.UITestApplication.start(UITestApplication.java:69)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ]
Josef Kopriva updated JBDS-4756:
--------------------------------
Environment: CentralCI
> Cannot start devstudio on mac os with jdk 11
> --------------------------------------------
>
> Key: JBDS-4756
> URL: https://issues.jboss.org/browse/JBDS-4756
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.11.0.AM1
> Environment: CentralCI
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: 12.11.0.GA
>
> Attachments: Screenshot_20190204_115602.png
>
>
> I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here:
> !Screenshot_20190204_115602.png|thumbnail!
> More info links [here|https://support.apple.com/kb/DL1572?locale=en_US].
> I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace:
> {code}
> java.awt.HeadlessException
> at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186)
> at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244)
> at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237)
> at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {code}
> It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ]
Josef Kopriva updated JBDS-4756:
--------------------------------
Priority: Major (was: Critical)
> Cannot start devstudio on mac os with jdk 11
> --------------------------------------------
>
> Key: JBDS-4756
> URL: https://issues.jboss.org/browse/JBDS-4756
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.11.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: 12.11.0.GA
>
> Attachments: Screenshot_20190204_115602.png
>
>
> I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here:
> !Screenshot_20190204_115602.png|thumbnail!
> More info links [here|https://support.apple.com/kb/DL1572?locale=en_US].
> I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace:
> {code}
> java.awt.HeadlessException
> at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186)
> at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244)
> at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237)
> at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {code}
> It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBIDE-26602) Switching JDKs for EAP7.2 breaks EAP Launch configuration
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26602:
-------------------------------------
Summary: Switching JDKs for EAP7.2 breaks EAP Launch configuration
Key: JBIDE-26602
URL: https://issues.jboss.org/browse/JBIDE-26602
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.11.0.Final
Reporter: Josef Kopriva
Switching JDK for EAP7.2 results in wrong launch command for EAP.
The issue is with parameter: --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26311:
---------------------------------------
UPDATE: If I use EAP 7.2 and do deploy before shutting down the server, shutdown works as expected, but If I start server and shutdown right away, then it fails.
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Major
> Labels: regression
> Fix For: 4.11.x
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26582?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26582:
------------------------------------
I would like to see the same kind of support that we have for spring boot so no native in the first place
> Add support for Quarkus based applications
> ------------------------------------------
>
> Key: JBIDE-26582
> URL: https://issues.jboss.org/browse/JBIDE-26582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Reporter: Jeff MAURY
> Priority: Major
> Fix For: 4.12.0.Final
>
>
> We should support JBoss Tools based inner loop for Quarkus based applications.
> In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop.
> That would also probably means an update of the openJDK base image
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26582?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26582 at 3/29/19 4:34 AM:
-------------------------------------------------------------------
[~jeffmaury] what is your vision for this support looking like? In my limited understanding native images would only run on linux, but the dev-mode hotcode replace might be something that we can support?
was (Author: adietish):
[~jeffmaury] what is your vision for this support looking like? As far as I understood so far native images would only run on linux, but the dev-mode hotcode replace might be something that we can support?
> Add support for Quarkus based applications
> ------------------------------------------
>
> Key: JBIDE-26582
> URL: https://issues.jboss.org/browse/JBIDE-26582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Reporter: Jeff MAURY
> Priority: Major
> Fix For: 4.12.0.Final
>
>
> We should support JBoss Tools based inner loop for Quarkus based applications.
> In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop.
> That would also probably means an update of the openJDK base image
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month