[
https://issues.jboss.org/browse/JBIDE-25588?page=com.atlassian.jira.plugi...
]
Ondrej Dockal commented on JBIDE-25588:
---------------------------------------
Server adapter does not hang anymore, instead, it got started but OS is unreachable, see
output from /.metadata/.log:
{code}
!SESSION 2019-01-03 12:50:49.249 -----------------------------------------------
eclipse.buildId=12.10.0.AM1-v20190102-1151-B3740
java.version=9.0.4
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: -os linux -ws gtk -arch x86_64 -product
com.jboss.devstudio.core.product
!ENTRY org.eclipse.jface.text 2 0 2019-01-03 12:54:30.412
!MESSAGE Duplicate template id: 'org.eclipse.wst.xslt.templates.xpath.boolean'
!ENTRY org.jboss.tools.openshift.cdk.server 4 0 2019-01-03 13:08:33.949
!MESSAGE Error contacting OpenShift
!STACK 0
org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException:
The CDK VM is up and running, but OpenShift is unreachable at url
https://192.168.42.221:8443. The VM may not have been registered successfully. Please
check your console output for more information
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
!ENTRY org.eclipse.core.jobs 4 2 2019-01-03 13:08:35.103
!MESSAGE An internal error occurred during: "Inspecting CDK environment...".
!STACK 0
com.openshift.restclient.OpenShiftException: Unable to read endpoint
https://192.168.42.221:8443/api
at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:192)
at
com.openshift.internal.restclient.ApiTypeMapper.getLegacyGroups(ApiTypeMapper.java:177)
at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:122)
at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:82)
at
com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:148)
at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:293)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:274)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:238)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:219)
at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:400)
at
com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
at
org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:115)
at
org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:73)
at
org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:60)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: okhttp3.internal.http2.ConnectionShutdownException
at okhttp3.internal.http2.Http2Connection.newStream(Http2Connection.java:247)
at okhttp3.internal.http2.Http2Connection.newStream(Http2Connection.java:230)
at okhttp3.internal.http2.Http2Codec.writeRequestHeaders(Http2Codec.java:113)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:50)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at com.openshift.restclient.ClientBuilder$1.intercept(ClientBuilder.java:241)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at
com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
at okhttp3.RealCall.execute(RealCall.java:77)
at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:189)
... 17 more
{code}
CDK server adapter timeouts during starting with JDK9
-----------------------------------------------------
Key: JBIDE-25588
URL:
https://issues.jboss.org/browse/JBIDE-25588
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.5.2.Final
Environment: Fedora 26
java-9-openjdk-9.0.1.11-4.fc26.x86_64
Reporter: Ondrej Dockal
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.11.x
CDK server adapter remains in state starting after CDK is started properly (in console
you can see all steps passed without problem), one can connect to openshift via browser.
Also, SSL untrusted certificate was accepted. There is running job: Starting Container
Developer Environment 3.2+ Preparing launch delegate...: Launching delegate...
Adapter will just timeout eventually.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)