[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU

[joerg.rene.saut...@gmail.com (JIRA)]

Title: Message Title

Jörg Sautter commented on JENKINS-56581   Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Hi, a small update on this issue, we change the type the disk is mounted in the VM. This made everything even worse, so we decided to build the remoting jar of jenkins and modfy the logging. It seems like the selector.select() method doesn't block, adding a timeout did not change the behaviour. The call returns after ~3000ns with 0 items, no call to selector.wakeup is done and the selector thread is not interrupted at this point. I don't understand why the select call returns here ... We now set the priority of the selectorThread to Thread.MIN_PRIORITY and call Thread.yield if wantSelectNow is fals and selected is 0. Lets see if this helps ...   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.23.1563982620324%40Atlassian.JIRA.