[JBoss JIRA] (JBIDE-26035) Convert SSP to function in an osgi environment
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26035?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26035:
------------------------------------
I don't think Jigsaw provides isolation and not supporting multi version is a blocker
> Convert SSP to function in an osgi environment
> ----------------------------------------------
>
> Key: JBIDE-26035
> URL: https://issues.jboss.org/browse/JBIDE-26035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> {code}
> mkdir felix
> cd felix
> wget http://download.nextag.com/apache/felix/org.apache.felix.main.distributio...
> unzip org.apache.felix.main.distribution-5.6.10.zip
> cd ../
> git clone git@github.com:robstryker/org.jboss.tools.ssp.git
> cd org.jboss.tools.ssp
> git checkout osgi_branch1
> mvn clean install
> #cp api/target/org.jboss.tools.ssp.api-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp launching/target/org.jboss.tools.ssp.launching-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle
> #cp server-spi/target/org.jboss.tools.ssp.server.spi-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp server/target/org.jboss.tools.ssp.server-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> du -ah | grep "jar$" | grep "target/" | grep -v "test-classes" | grep -v "classes/" | grep -v "schema" | grep -v "client" | cut -c 1,2,3,4 --complement | awk '{ print "cp " $0 " ../felix/felix-framework-5.6.10/bundle/";}' | sh
> cd ../felix/felix-framework-5.6.10/
> java -jar bin/felix.jar
> {code}
> Note error:
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> ERROR: Bundle org.jboss.tools.ssp.server.wildfly [11] Error starting file:/home/rob/tmp/ssp_osgi/felix/felix-framework-5.6.10/bundle/org.jboss.tools.ssp.server.wildfly-0.8-SNAPSHOT.jar (org.osgi.framework.BundleException: Activator start error in bundle org.jboss.tools.ssp.server.wildfly [11].)
> java.lang.NoClassDefFoundError: org/osgi/framework/BundleActivator
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
> This is very strange. All the other bundles start fine. This bundle can't even find its osgi classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24979:
-------------------------------------
Sprint: devex #139 October 2017, devex #148 April 2018, devex #150 June 2019 (was: devex #139 October 2017, devex #148 April 2018)
> Scale up/down/to: NPE if you have only a rc, no dc for your app
> ---------------------------------------------------------------
>
> Key: JBIDE-24979
> URL: https://issues.jboss.org/browse/JBIDE-24979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.x
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, scale
> Fix For: 4.6.0.AM2
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png
>
>
> # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
> !image-2017-09-04-21-24-57-027.png!
> The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing.
> Result:
> Nothing happens and in the log you discover the following:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24979:
----------------------------------------
Assignee: Dmitrii Bocharov (was: Jeff MAURY)
> Scale up/down/to: NPE if you have only a rc, no dc for your app
> ---------------------------------------------------------------
>
> Key: JBIDE-24979
> URL: https://issues.jboss.org/browse/JBIDE-24979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.x
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, scale
> Fix For: 4.6.0.AM2
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png
>
>
> # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
> !image-2017-09-04-21-24-57-027.png!
> The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing.
> Result:
> Nothing happens and in the log you discover the following:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25616:
-------------------------------------
Labels: docker_image fis upstream (was: )
> [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: docker_image, fis, upstream
> Fix For: 4.6.x
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25616:
-------------------------------------
Summary: [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com (was: Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com)
> [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25616:
------------------------------------------
[~aurelien.pupier] do we know when FIS 7 with support for debugging gets available?
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months