[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25000:
------------------------------------------
Still no obvious solution in our code, nothing worked.
Have to discuss it with openshift-dev, suggesting that a readyness-probe for the debugging port should be added in case debugging is enabled.
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.x
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26223) Server adapter: Error occurred during starting server adapter for nodejs app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26223?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26223:
-------------------------------------
Steps to Reproduce:
1. Create and Start CDK 3.2+ server adapter using newest CDK (v3.5.0)
2. Preferences -> Openshift 3 -> add path to oc
3. Add new application into running OS3 connection (nodejs)
4. Create new server adapter for this app
5. Adapter is created and started succesfully
Actual result: Adapter is started, but I got this error:
!Screenshot_20180719_150025.png|thumbnail!
was:
1. Create and Start CDK 3.2+ server adapter using newest CDK (v3.5.0)
2. Preferences -> Openshift 3 -> add path to oc 3.11
3. Add new application into running OS3 connection (nodejs)
4. Create new server adapter for this app
5. Adapter is created and started succesfully
Actual result: Adapter is started, but I got this error:
!Screenshot_20180719_150025.png|thumbnail!
> Server adapter: Error occurred during starting server adapter for nodejs app
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26223
> URL: https://issues.jboss.org/browse/JBIDE-26223
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Labels: oc_binary, rsync, server_adapter
> Fix For: 4.9.x
>
> Attachments: Screenshot_20180719_150025.png
>
>
> I have encounter rsync error during starting up server adapter while trying out https://github.com/jbosstools/jbosstools-openshift/pull/1774 together with oc 3.11 built from source.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26180 at 8/29/18 4:35 PM:
-------------------------------------------------------------
When simrel 2018-09 M3 is out with new TM 4.5.0 build [1], we'll have to update these manifests to ref the latest TM/rse bits:
* ./jbosstools-forge/plugins/org.jboss.tools.forge.ui/META-INF/MANIFEST.MF
* ./jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.rse.core/META-INF/MANIFEST.MF
* ./jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.rse.ui/META-INF/MANIFEST.MF
* ./jbosstools-server/as/tests/org.jboss.tools.as.test.core/META-INF/MANIFEST.MF
* ./jbosstools-server/as/features/org.jboss.ide.eclipse.as.server.rse.integration.feature/feature.xml
* ./jbosstools-server/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/feature.xml
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=536507
was (Author: nickboldt):
[checkUnresolvedIssues.py] Slip to fixversion = *4.9.x*
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months