[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated JENKINS-56625 Thanks to Adam BH and Oleg Nenashev Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Status: Fixed but Unreleased Resolved Released As: v2.0.1 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated JENKINS-56625 Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Status: Open Fixed but Unreleased Assignee: Antonio Muñiz Thomas Döring Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring commented on JENKINS-56625 Re: Too many open file descriptors from embedded build status usage Adam BH Thank you. I just merged your pull request. A v2.0.1 bugfix release will be released any time soon. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated an issue Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Labels: embeddable-build-status plugin v2.0.1 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Adam BH commented on JENKINS-56625 Re: Too many open file descriptors from embedded build status usage This has become higher priority for us so I made the fix required and tested a SNAPSHOT hpi https://github.com/jenkinsci/embeddable-build-status-plugin/pull/42 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Oleg Nenashev commented on JENKINS-56625 Re: Too many open file descriptors from embedded build status usage I believe it comes from here: https://github.com/jenkinsci/embeddable-build-status-plugin/blob/ac894bdf0953c82bbd193005f9e9cff121b77ae2/src/main/java/org/jenkinsci/plugins/badge/StatusImage.java#L182-L198 . Indeed streams are not handled correctly there when baseUrl fomes from a file . 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title
Adam BH updated an issue
Jenkins / JENKINS-56625
Too many open file descriptors from embedded build status usage
Change By:
Adam BH
We have some users with many Jenkins Jobs they monitor using a custom HTML dashboard full of 100+ embedded build status links, refreshing once a minute. After upgrading from Build status 1.9 to 2.0 we started seeing tomcat/jenkins running into a lot of "too many open files" errors like the following: ``` {code:java} Mar 19, 2019 6:25:55 AM org.apache.tomcat.util.net.NioEndpoint$Acceptor runSEVERE: Socket accept failedjava.io.IOException: Too many open filesat sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482)at java.lang.Thread.run(Thread.java:748)Mar 19, 2019 6:25:56 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoopWARNING: RMI TCP Accept-9009: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=9009] throwsjava.net.SocketException: Too many open files (Accept failed)at java.net.PlainSocketImpl.socketAccept(Native Method)at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)at java.net.ServerSocket.implAccept(ServerSocket.java:545)at java.net.ServerSocket.accept(ServerSocket.java:513)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)at java.lang.Thread.run(Thread.java:748) ``` {code} We looked into the tomcat process's open FDs using lsof and found [ fonts/verdana.ttf]( https://github.com/jenkinsci/embeddable-build-status-plugin/blob/240917ee3884de43faaab6f12453f52830c12b17/src/main/java/org/jenkinsci/plugins/badge/StatusImage.java#L184 ) |http://example.com] is the thing getting accessed so much ``` {code:java} # lsof -p $(pgrep java) | awk '{ print $9 }' | sort | uniq -c | sort -n | tail 2 /usr/java/jre1.8.0_202/lib/ext/sunjce_provider.jar 2 /usr/java/jre1.8.0_202/lib/ext/sunpkcs11.jar 2 /usr/java/jre1.8.0_202/lib/jce.jar 2 /usr/java/jre1.8.0_202/lib/jsse.jar 2 /usr/java/jre1.8.0_202/lib/resources.jar 2 /usr/java/jre1.8.0_202/lib/rt.jar 5 /dev/urandom 8 anon_inode 16 pipe836 /srv/jenkins/plugins/embeddable-build-status/fonts/verdana.ttf ``` {code} This is a lower example, we did see up to 6200 open verdana.ttf file descriptors out of the 8192 tomcat & system wide limits.To reproduce this I used a test jenkins system which didn't have any of the verdana open FDs, wrote a quick loop to hammer a buildStatus link and watched the tomcat total file descriptors shoot up. I downgraded the plugin 1.9 and confirmed it didn't have this problem, so this is new behavior in 2.0, probably due to the custom text fea
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title
Adam BH updated an issue
Jenkins / JENKINS-56625
Too many open file descriptors from embedded build status usage
Change By:
Adam BH
We have some users with many Jenkins Jobs they monitor using a custom HTML dashboard full of 100+ embedded build status links, refreshing once a minute. After upgrading from Build status 1.9 to 2.0 we started seeing tomcat/jenkins running into a lot of "too many open files" errors like the following:{code:java}Mar 19, 2019 6:25:55 AM org.apache.tomcat.util.net.NioEndpoint$Acceptor runSEVERE: Socket accept failedjava.io.IOException: Too many open filesat sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482)at java.lang.Thread.run(Thread.java:748)Mar 19, 2019 6:25:56 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoopWARNING: RMI TCP Accept-9009: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=9009] throwsjava.net.SocketException: Too many open files (Accept failed)at java.net.PlainSocketImpl.socketAccept(Native Method)at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)at java.net.ServerSocket.implAccept(ServerSocket.java:545)at java.net.ServerSocket.accept(ServerSocket.java:513)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)at java.lang.Thread.run(Thread.java:748){code}We looked into the tomcat process's open FDs using lsof and found [ /srv/jenkins/plugins/embeddable-build-status/fonts/verdana.ttf| https://github.com/jenkinsci/embeddable-build-status-plugin/blob/240917ee3884de43faaab6f12453f52830c12b17/src/main/java/org/jenkinsci/plugins/badge/StatusImage.java#L184 |http://example.com ] is the thing getting accessed so much{code:java}# lsof -p $(pgrep java) | awk '{ print $9 }' | sort | uniq -c | sort -n | tail 2 /usr/java/jre1.8.0_202/lib/ext/sunjce_provider.jar 2 /usr/java/jre1.8.0_202/lib/ext/sunpkcs11.jar 2 /usr/java/jre1.8.0_202/lib/jce.jar 2 /usr/java/jre1.8.0_202/lib/jsse.jar 2 /usr/java/jre1.8.0_202/lib/resources.jar 2 /usr/java/jre1.8.0_202/lib/rt.jar 5 /dev/urandom 8 anon_inode 16 pipe836 /srv/jenkins/plugins/embeddable-build-status/fonts/verdana.ttf{code}This is a lower example, we did see up to 6200 open verdana.ttf file descriptors out of the 8192 tomcat & system wide limits.To reproduce this I used a test jenkins system which didn't have any of the verdana open FDs, wrote a quick loop to hammer a buildStatus link and watched the tomcat total file descriptors shoot up. I downgraded the plugin 1.9 and confirmed it didn't have this problem, so this is new behavior in 2.0, probably due to the
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title
Adam BH updated an issue
Jenkins / JENKINS-56625
Too many open file descriptors from embedded build status usage
Change By:
Adam BH
We have some users with many Jenkins Jobs they monitor using a custom HTML dashboard full of 100+ embedded build status links, refreshing once a minute. After upgrading from Build status 1.9 to 2.0 we started seeing tomcat/jenkins running into a lot of "too many open files" errors like the following: ``` {code:java} Mar 19, 2019 6:25:55 AM org.apache.tomcat.util.net.NioEndpoint$Acceptor runSEVERE: Socket accept failedjava.io.IOException: Too many open filesat sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482)at java.lang.Thread.run(Thread.java:748)Mar 19, 2019 6:25:56 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoopWARNING: RMI TCP Accept-9009: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=9009] throwsjava.net.SocketException: Too many open files (Accept failed)at java.net.PlainSocketImpl.socketAccept(Native Method)at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)at java.net.ServerSocket.implAccept(ServerSocket.java:545)at java.net.ServerSocket.accept(ServerSocket.java:513)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)at java.lang.Thread.run(Thread.java:748) ``` {code} We looked into the tomcat process's open FDs using lsof and found [ fonts/verdana.ttf]( https://github.com/jenkinsci/embeddable-build-status-plugin/blob/240917ee3884de43faaab6f12453f52830c12b17/src/main/java/org/jenkinsci/plugins/badge/StatusImage.java#L184 ) |http://example.com] is the thing getting accessed so much ``` {code:java} # lsof -p $(pgrep java) | awk '{ print $9 }' | sort | uniq -c | sort -n | tail 2 /usr/java/jre1.8.0_202/lib/ext/sunjce_provider.jar 2 /usr/java/jre1.8.0_202/lib/ext/sunpkcs11.jar 2 /usr/java/jre1.8.0_202/lib/jce.jar 2 /usr/java/jre1.8.0_202/lib/jsse.jar 2 /usr/java/jre1.8.0_202/lib/resources.jar 2 /usr/java/jre1.8.0_202/lib/rt.jar 5 /dev/urandom 8 anon_inode 16 pipe836 /srv/jenkins/plugins/embeddable-build-status/fonts/verdana.ttf ``` {code} This is a lower example, we did see up to 6200 open verdana.ttf file descriptors out of the 8192 tomcat & system wide limits.To reproduce this I used a test jenkins system which didn't have any of the verdana open FDs, wrote a quick loop to hammer a buildStatus link and watched the tomcat total file descriptors shoot up. I downgraded the plugin 1.9 and confirmed it didn't have this problem, so this is new behavior in 2.0, probably due to the custom text fea
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Adam BH created an issue Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Issue Type: Bug Assignee: Antonio Muñiz Components: embeddable-build-status-plugin Created: 2019-03-19 18:50 Environment: Jenkins ver. 2.164.1 Embeddable Build Status 2.0 Labels: plugin embeddable-build-status Priority: Major Reporter: Adam BH We have some users with many Jenkins Jobs they monitor using a custom HTML dashboard full of 100+ embedded build status links, refreshing once a minute. After upgrading from Build status 1.9 to 2.0 we started seeing tomcat/jenkins running into a lot of "too many open files" errors like the following: ``` Mar 19, 2019 6:25:55 AM org.apache.tomcat.util.net.NioEndpoint$Acceptor run SEVERE: Socket accept failed java.io.IOException: Too many open files at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482) at java.lang.Thread.run(Thread.java:748) Mar 19, 2019 6:25:56 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoop WARNING: RMI TCP Accept-9009: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=9009] throws java.net.SocketException: Too many open files (Accept failed) at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) at java.net.ServerSocket.implAccept
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Adam BH created an issue Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Issue Type: Bug Assignee: Antonio Muñiz Components: embeddable-build-status-plugin Created: 2019-03-19 18:50 Environment: Jenkins ver. 2.164.1 Embeddable Build Status 2.0 Labels: plugin embeddable-build-status Priority: Major Reporter: Adam BH We have some users with many Jenkins Jobs they monitor using a custom HTML dashboard full of 100+ embedded build status links, refreshing once a minute. After upgrading from Build status 1.9 to 2.0 we started seeing tomcat/jenkins running into a lot of "too many open files" errors like the following: ``` Mar 19, 2019 6:25:55 AM org.apache.tomcat.util.net.NioEndpoint$Acceptor run SEVERE: Socket accept failed java.io.IOException: Too many open files at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482) at java.lang.Thread.run(Thread.java:748) Mar 19, 2019 6:25:56 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoop WARNING: RMI TCP Accept-9009: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=9009] throws java.net.SocketException: Too many open files (Accept failed) at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) at java.net.ServerSocket.implAccept
