[jboss-jira] [JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung

[Filip Brychta (Jira)]

    [ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693956#comment-13693956 ] 

Filip Brychta commented on SWSQE-594:
-------------------------------------

There is also following error where the # of connections is increasing, maybe some pool gets full with incorrectly closed connections?
Feb 11, 2019 1:33:52 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (1/100): jenkins-slave-kiali-ui-tests-vxltp
Feb 11, 2019 1:33:53 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
WARNING: Connection #181 failed
java.io.EOFException
        at java.io.DataInputStream.readFully(DataInputStream.java:197)
        at java.io.DataInputStream.readFully(DataInputStream.java:169)
        at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:244)

Feb 11, 2019 1:33:53 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted JNLP4-connect connection #182 from /10.16.23.44:41946

> Jenkins Jobs Hung
> -----------------
>
>                 Key: SWSQE-594
>                 URL: https://issues.jboss.org/browse/SWSQE-594
>             Project: Kiali QE
>          Issue Type: Bug
>            Reporter: Matt Mahoney
>            Assignee: Filip Brychta
>            Priority: Major
>         Attachments: image-2019-02-11-16-35-41-783.png
>
>
> Jenkins jobs hung in the following state:
>  !image-2019-02-11-16-35-41-783.png|thumbnail! 
> After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)