[jbosstools-issues] [JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

Mon Nov 7 08:49:00 EST 2016

     [ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-23470:
-------------------------------------
    Steps to Reproduce: 
# ASSERT: have a nodejs application (with pods and service) running
# ASSERT: have the project for the application imported to your workspace
# ASSERT: have a server adapter for the nodejs application
# ASSERT: have the server adapter [Started, Synchronized]
# EXEC: pick "Restart in Debug" in the context menu of your server adapter

Result:
The server adapter wont get up, it gets stuck in [Starting, Synchronized]
In the progress view you'll see that the job that the adapter is waiting for is "Updating Deployment Configuration"
!server-adapter-stuck-starting.png!
After some time the starting process stops with the following error:
!failed-to-detect-pod.png!

In the Eclipse log you'll spot the following:
{code}
!ENTRY org.jboss.tools.openshift.ui 4 0 2016-11-07 14:18:29.615
!MESSAGE Unable to read endpoint https://10.1.1.2:8443/api
!STACK 0
com.openshift.restclient.OpenShiftException: Unable to read endpoint https://10.1.1.2:8443/api
	at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:205)
	at com.openshift.internal.restclient.ApiTypeMapper.getLegacyGroups(ApiTypeMapper.java:188)
	at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:128)
	at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:116)
	at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:145)
	at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:132)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
	at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:291)
	at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:65)
	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.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:343)
	at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:448)
	at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.net.SocketTimeoutException: connect timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at okhttp3.internal.Platform.connectSocket(Platform.java:121)
	at okhttp3.internal.io.RealConnection.connectSocket(RealConnection.java:185)
	at okhttp3.internal.io.RealConnection.buildConnection(RealConnection.java:170)
	at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
	at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:187)
	at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:123)
	at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:93)
	at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:296)
	at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
	at okhttp3.RealCall.getResponse(RealCall.java:243)
	at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:54)
	at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
	at okhttp3.RealCall.execute(RealCall.java:57)
	at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:202)
	... 16 more
{code}

  was:
# ASSERT: have a nodejs application (with pods and service) running
# ASSERT: have the project for the application imported to your workspace
# ASSERT: have a server adapter for the nodejs application
# ASSERT: have the server adapter [Started, Synchronized]
# EXEC: pick "Restart in Debug" in the context menu of your server adapter

Result:
The server adapter wont get up, it gets stuck in [Starting, Synchronized]
In the progress view you'll see that the job that the adapter is waiting for is "Updating Deployment Configuration"
!server-adapter-stuck-starting.png!
After some time the starting process stops with the following error:
!failed-to-detect-pod.png!

In the Eclipse log you'll spot the following:
{code}
!ENTRY org.jboss.tools.openshift.ui 4 0 2016-11-07 14:18:29.615
!MESSAGE Unable to read endpoint https://10.1.1.2:8443/api
!STACK 0
com.openshift.restclient.OpenShiftException: Unable to read endpoint https://10.1.1.2:8443/api
	at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:205)
	at com.openshift.internal.restclient.ApiTypeMapper.getLegacyGroups(ApiTypeMapper.java:188)
	at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:128)
	at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:116)
	at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:145)
	at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:132)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
	at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:291)
	at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:65)
	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.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:343)
	at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:448)
	at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.net.SocketTimeoutException: connect timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at okhttp3.internal.Platform.connectSocket(Platform.java:121)
	at okhttp3.internal.io.RealConnection.connectSocket(RealConnection.java:185)
	at okhttp3.internal.io.RealConnection.buildConnection(RealConnection.java:170)
	at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
	at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:187)
	at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:123)
	at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:93)
	at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:296)
	at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
	at okhttp3.RealCall.getResponse(RealCall.java:243)
	at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:54)
	at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
	at okhttp3.RealCall.execute(RealCall.java:57)
	at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:202)
	... 16 more
Created new window in existing browser session.
{code}

> Server Adapter: stuck restarting in debug mode
> ----------------------------------------------
>
>                 Key: JBIDE-23470
>                 URL: https://issues.jboss.org/browse/JBIDE-23470
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM3
>            Reporter: Andre Dietisheim
>            Priority: Critical
>         Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png
>
>

--
This message was sent by Atlassian JIRA
(v7.2.3#72005)