[JBoss JIRA] (ERT-537) Update to com.spotify.docker.client 8.9.2 [EBZ#522659]
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-537?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg updated ERT-537:
--------------------------------
Description:
This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources.
(/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2)
(/) Confirm the changes made should allow Docker Tooling to function
(/) Create CQs, ATO CQs for JNR stack update
(/) Update JNR stack, along with docker-client in Orbit
(?) Push all changes necessary to Docker Tooling
was:
This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources.
(/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2)
(/) Confirm the changes made should allow Docker Tooling to function
(/) Create CQs, ATO CQs for JNR stack update
(?) Update JNR stack, along with docker-client in Orbit
(?) Push all changes necessary to Docker Tooling
> Update to com.spotify.docker.client 8.9.2 [EBZ#522659]
> ------------------------------------------------------
>
> Key: ERT-537
> URL: https://issues.jboss.org/browse/ERT-537
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Roland Grunberg
> Labels: Docker, bzira
>
> This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources.
> (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2)
> (/) Confirm the changes made should allow Docker Tooling to function
> (/) Create CQs, ATO CQs for JNR stack update
> (/) Update JNR stack, along with docker-client in Orbit
> (?) Push all changes necessary to Docker Tooling
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25446 at 2/8/18 9:52 AM:
---------------------------------------------------------------
I have reproduced the issue in this pipeline job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud.... Though, it really seems to be connected with another process, aka starting or building different job, or so.
was (Author: odockal):
I have reproduced the issue in this pipeline job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud.... Though, it really seems to be connected with another process, aka starting of building different job, or so.
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: jenkins
> Fix For: 4.5.3.AM1, 4.5.x
>
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov edited comment on JBIDE-25696 at 2/8/18 6:55 AM:
--------------------------------------------------------------------
bq. Affects Version/s
I always forget where to find thee overall version of JBoss Tools and not just one of the components'.
was (Author: vsevolodgolovanov):
bq. Affects Version/s
I always forget where to find thee overall version of JBoss Tools.
> Deadlock when running JBoss Tools Project Validator on startup
> --------------------------------------------------------------
>
> Key: JBIDE-25696
> URL: https://issues.jboss.org/browse/JBIDE-25696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
> Reporter: Vsevolod Golovanov
> Attachments: lockedup.png, threaddump-1518088511239.tdump
>
>
> The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
> When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
> Here's what it looks like: !lockedup.png|thumbnail!
> This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
> It always shows JBoss Tools Project Validator in the Progress view when this happens.
> VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
> I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov commented on JBIDE-25696:
--------------------------------------------
bq. Affects Version/s
I always forget where to find thee overall version of JBoss Tools.
> Deadlock when running JBoss Tools Project Validator on startup
> --------------------------------------------------------------
>
> Key: JBIDE-25696
> URL: https://issues.jboss.org/browse/JBIDE-25696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
> Reporter: Vsevolod Golovanov
> Attachments: lockedup.png, threaddump-1518088511239.tdump
>
>
> The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
> When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
> Here's what it looks like: !lockedup.png|thumbnail!
> This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
> It always shows JBoss Tools Project Validator in the Progress view when this happens.
> VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
> I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov updated JBIDE-25696:
---------------------------------------
Description:
The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
Here's what it looks like: !lockedup.png|thumbnail!
This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
It always shows JBoss Tools Project Validator in the Progress view when this happens.
VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
was:
The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
Here's what it looks like: !lockedup.png|thumbnail!
This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
It's always running JBoss Tools Project Validator when this happens.
VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
> Deadlock when running JBoss Tools Project Validator on startup
> --------------------------------------------------------------
>
> Key: JBIDE-25696
> URL: https://issues.jboss.org/browse/JBIDE-25696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
> Reporter: Vsevolod Golovanov
> Attachments: lockedup.png, threaddump-1518088511239.tdump
>
>
> The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
> When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
> Here's what it looks like: !lockedup.png|thumbnail!
> This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
> It always shows JBoss Tools Project Validator in the Progress view when this happens.
> VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
> I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by Vsevolod Golovanov (JIRA)
Vsevolod Golovanov created JBIDE-25696:
------------------------------------------
Summary: Deadlock when running JBoss Tools Project Validator on startup
Key: JBIDE-25696
URL: https://issues.jboss.org/browse/JBIDE-25696
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
Reporter: Vsevolod Golovanov
Attachments: lockedup.png, threaddump-1518088511239.tdump
The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
Here's what it looks like: !lockedup.png|thumbnail!
This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
It's always running JBoss Tools Project Validator when this happens.
VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25446:
---------------------------------------
I have reproduced the issue in this pipeline job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud.... Though, it really seems to be connected with another process, aka starting of building different job, or so.
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: jenkins
> Fix For: 4.5.3.AM1, 4.5.x
>
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years