[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-25616:
-----------------------------------------
Which FIS image are you using?
If using the same than in the screencast it is not working. The Fuse Tech preview 3 FIS image need to be used (which is not yet publicly available)
To have the project correctly configured you need to use Fuse Tooling 10.2.0 and set Camel version to 2.20.1 in the wizard.
You can see this comment for steps: https://issues.jboss.org/browse/OSFUSE-548?focusedCommentId=13522545&page...
> 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.5.3.AM2
>
> Attachments: java
>
>
> 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)
8 years, 2 months
[JBoss JIRA] (JBIDE-25556) OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25556?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25556:
-------------------------------
Sprint: devex #144 January 2018
> OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
> ---------------------------------------------------------------------------
>
> Key: JBIDE-25556
> URL: https://issues.jboss.org/browse/JBIDE-25556
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Error message from error log:
> {code:java}
> eclipse.buildId=11.2.0.AM3-v20180105-1612-B1822
> java.version=9.0.1
> 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_B1822-Java9-2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.common.jdt.debug
> Error
> Thu Jan 11 10:45:50 CET 2018
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
> at java.base/java.util.TimerThread.run(Timer.java:506)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25541) Server New and Noteworthy for 4.5.2.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25541?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-25541.
------------------------------
Resolution: Rejected
> Server New and Noteworthy for 4.5.2.Final
> -----------------------------------------------------
>
> Key: JBIDE-25541
> URL: https://issues.jboss.org/browse/JBIDE-25541
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Critical
> Labels: task
> Fix For: 4.5.2.Final
>
>
> Rob Stryker,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Server by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-25518 #comment Create N&N for Server 4.5.2.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.5.2.Final since the AM3 release of Server, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.2.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.2.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25504:
-------------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.x)
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25602) NullPointerException in RegistryProviderModel.getRegistryURL
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25602?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25602:
-------------------------------
Sprint: devex #144 January 2018
> NullPointerException in RegistryProviderModel.getRegistryURL
> ------------------------------------------------------------
>
> Key: JBIDE-25602
> URL: https://issues.jboss.org/browse/JBIDE-25602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.core.connection.registry.RegistryProviderModel.getRegistryURL(RegistryProviderModel.java:37)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.discoverRegistryPressed(AdvancedConnectionEditor.java:302)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.access$2(AdvancedConnectionEditor.java:300)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$1$1.widgetSelected(AdvancedConnectionEditor.java:128)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.106.0.v20170608-0516 | 3.106.1.v20170926-0519 |
> | org.jboss.tools.openshift.core | 3.4.1.v20171025-1008 | 3.4.2.v20171115-1821 |
> | org.jboss.tools.openshift.ui | 3.4.1.v20171025-1219 | 3.4.2.v20171115-1650 |
> Operating Systems:
> | Linux | 4.10.0 | 4.10.0 |
> | MacOSX | 10.13.1 | 10.13.2 |
> | Windows | 6.2.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5a2a4339e4b037...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months