[jbosstools-issues] [JBoss JIRA] (ERT-178) Search for tags of docker image with plenty of tags results to an error [EBZ#493005]

Jeff Johnston (JIRA) issues at jboss.org
Mon Jan 9 17:47:00 EST 2017


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

Jeff Johnston updated ERT-178:
------------------------------
    Sprint: devex #125 December 2016


> Search for tags of docker image with plenty of tags results to an error [EBZ#493005]
> ------------------------------------------------------------------------------------
>
>                 Key: ERT-178
>                 URL: https://issues.jboss.org/browse/ERT-178
>             Project: Eclipse Release Train
>          Issue Type: Task
>          Components: Linux Tools
>            Reporter: Friendly Jira Robot
>            Assignee: Jeff Johnston
>              Labels: Docker, bzira
>
> When trying to search for "php" image in Search and pull a Docker Image wizard and attempt to get its tags result to an exception. This happens right after I click on Next button in the wizard and Searching tags... job is running. I observed it happens on image with plenty of tags (but may not be the real cause). Then wizard page with image tags is shown but table where tags are supposed to be is empty.
> Stack trace:
> javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out
> java.util.concurrent.ExecutionException: javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out
> 	at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
> 	at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
> 	at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> 	at org.eclipse.linuxtools.internal.docker.core.DockerHubRegistry.getTags(DockerHubRegistry.java:79)
> 	at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageTagSelectionPage$1.run(ImageTagSelectionPage.java:97)
> 	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out
> 	at org.glassfish.jersey.client.JerseyInvocation.createExceptionForFamily(JerseyInvocation.java:994)
> 	at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:975)
> 	at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:855)
> 	at org.glassfish.jersey.client.JerseyInvocation.access$600(JerseyInvocation.java:91)
> 	at org.glassfish.jersey.client.JerseyInvocation$6.completed(JerseyInvocation.java:815)
> 	at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:189)
> 	at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:74)
> 	at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:171)
> 	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> 	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> 	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:267)
> 	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
> 	at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)



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


More information about the jbosstools-issues mailing list