[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23470:
----------------------------------------
Steps to Reproduce:
# ASSERT: have a CDK >= 25th of October
# 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
{code}
Assignee: (was: Dmitrii Bocharov)
> 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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ]
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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ]
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
Created new window in existing browser session.
{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!
> 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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ]
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!
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!
> 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: server-adapter-stuck-starting.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (ERT-446) DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-446:
---------------------------------------
Summary: DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143]
Key: ERT-446
URL: https://issues.jboss.org/browse/ERT-446
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
The following problem was reported via the automated error reporting:
Message: The 'docker-machine' command could not be located in '/usr/local/bin'
org.eclipse.linuxtools.docker.core.DockerException: The 'docker-machine' command could not be located in '/usr/local/bin'
at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:96)
at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:88)
at org.eclipse.linuxtools.internal.docker.core.ProcessUtils.processBuilder(ProcessUtils.java:69)
at org.eclipse.linuxtools.internal.docker.core.DockerMachine.getNames(DockerMachine.java:45)
at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.retrieveDockerMachineNames(NewDockerConnectionPage.java:806)
at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.widgetSelected(NewDockerConnectionPage.java:714)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
Bundles:
| org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 |
| org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
| org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 |
Operating Systems:
| Linux | 4.4.0 | 4.4.0 |
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5813b... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months