[jbosstools-issues] [JBoss JIRA] (ERT-508) Docker Explorer shows error upon showing connection for the 1st time (after creation, eclipse startup, etc) [EBZ#517061]

Friendly Jira Robot (JIRA) issues at jboss.org
Mon May 22 06:35:00 EDT 2017


Friendly Jira Robot created ERT-508:
---------------------------------------

             Summary: Docker Explorer shows error upon showing connection for the 1st time (after creation, eclipse startup, etc) [EBZ#517061]
                 Key: ERT-508
                 URL: https://issues.jboss.org/browse/ERT-508
             Project: Eclipse Release Train
          Issue Type: Task
          Components: Linux Tools
            Reporter: Friendly Jira Robot


Created attachment 268500
error upon the connection showing up in the "Docker Explorer"

steps to reproduce:
1. ASSERT: make sure that you have "Docker Explorer" opened
2. EXE: create a new docker connection (ex. to your local docker daemon)

Result:
The docker connection is then created and listed in the "Docker Explorer" but on the 1st appearance an error shows up:
java.lang.IllegalStateException: Entity input stream has already been closed.
	at org.glassfish.jersey.message.internal.EntityInputStream.ensureNotClosed(EntityInputStream.java:228)
	at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:854)
	at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:808)
	at org.glassfish.jersey.client.ClientResponse.readEntity(ClientResponse.java:326)
	at org.glassfish.jersey.client.InboundJaxrsResponse$1.call(InboundJaxrsResponse.java:115)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:419)
	at org.glassfish.jersey.client.InboundJaxrsResponse.runInScopeIfPossible(InboundJaxrsResponse.java:267)
	at org.glassfish.jersey.client.InboundJaxrsResponse.readEntity(InboundJaxrsResponse.java:112)
	at com.spotify.docker.client.DefaultDockerClient.message(DefaultDockerClient.java:2097)
	at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
	at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2013)
	at com.spotify.docker.client.DefaultDockerClient.listContainers(DefaultDockerClient.java:471)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:706)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:587)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.setState(DockerConnection.java:326)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.ping(DockerConnection.java:343)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:280)
	at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:205)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
see docker-explorer-connection-error.png for the screenshot of the error



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


More information about the jbosstools-issues mailing list