[
https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi...
]
André Dietisheim edited comment on JBIDE-26794 at 8/21/19 4:38 AM:
-------------------------------------------------------------------
source code that's used is likely here:
https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git
repository:
https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use
https://github.com/openshift-roadshow/nationalparks.git in *Git Repository
URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports
that :8787 is forwarded to :67980 on the pod. As far as I can see the springboot app is
not started in devmode. Very likely that we'd need to use a springboot complaint
fabric8 image instead.
[~jgammonred612] any insights into how you had springboot started in devmode with this
setup, please?
was (Author: adietish):
source code that's used is likely here:
https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git
repository:
https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use
https://github.com/openshift-roadshow/nationalparks.git in *Git Repository
URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports
that :8787 is forwarded to :67980 on the pod. As if the springboot app wasn't started
in dev mode.
OpenShift: Remote debugging is very slow
----------------------------------------
Key: JBIDE-26794
URL:
https://issues.jboss.org/browse/JBIDE-26794
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.11.0.Final
Environment: Version: 12.11.0.GA
Build id: GA-v20190329-0120-B4247
Build date: 20190329-0120
RHPDS
Reporter: Josef Kopriva
Priority: Critical
Fix For: 4.13.x
From Email on devtools-team from [~jgammonred612]:
{code:java}
Hi Folks:
Using this version of Code Ready Studio
Version: 12.11.0.GA
Build id: GA-v20190329-0120-B4247
Build date: 20190329-0120
I recently ran an Openshift Starter Workshop lab and witnessed a clear
issue with Code Ready Studio and INtelliJ
Workshop Starter Lab
(
http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
Lab 19 has a remote debugging setup. The remote debugger in Code Ready
connected very very slowly and would not step over or step out making
using it as a debugger virtually impossible.
One of the lab participants had IntelliJ and it connected immediately
and worked just fine.
Clearly, something is broken in CRS. Maybe someone would want to test
this out and fix?
You can find this lab on RHPDS.
Just FYI to the PM's.
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)