[JIRA] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Garron Kramer commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Hi Guys, FYI, I'm seeing the same issue with v1.572 Thanks, g This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Michael Küller commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Hey, just wanted to add that I'm seeing this issue with as well. Running v. 1.566. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Carl Molinari commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. We are seeing an issue when calls to the jenkins-cli.jar from node leave a socket open each time it is called. We use these calls to update the external resource plugin and this can lead to hundreds of file descriptors leaked every day. The only way to free them up is to restart Jenkins. lsof shows the unclosed socket as: java 4222 tomcat6 804u sock0,60t0 230747605 can't identify protocol This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Carl Molinari edited a comment on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. We are seeing an issue when calls to the jenkins-cli.jar from node leave a socket open each time it is called. We use these calls to update the external resource plugin and this can lead to hundreds of file descriptors leaked every day. The only way to free them up is to restart Jenkins. lsof shows the unclosed socket as: java 4222 tomcat6 804u sock0,60t0 230747605 can't identify protocol This is with Version 1.573 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Kanstantsin Shautsou commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. It maybe useful to wrote a test case and run automated bisect http://java.dzone.com/articles/automated-bug-finding-git ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Kohsuke Kawaguchi assigned JENKINS-23248 to Kohsuke Kawaguchi CLI: get-job calls are causing file descriptor leaks. Change By: Kohsuke Kawaguchi (29/Jul/14 12:03 AM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Kohsuke Kawaguchi commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Confirmed. Based on the output from lsof, TCP connections are leaking. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/SocketChannelStream.java http://jenkins-ci.org/commit/remoting/6c7d4d110362106cf897fef6485b80dbd3755d4c Log: JENKINS-23248 Making the close method more robust Unlike the usual close() method, shutdownInput/Output throws an exception for the 2nd invocation. It's better to silently do nothing instead of dying with IOException. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon resolved JENKINS-23248 as Fixed CLI: get-job calls are causing file descriptor leaks. Change By: SCM/JIRA link daemon (29/Jul/14 1:00 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/SocketChannelStream.java http://jenkins-ci.org/commit/remoting/c90fc463923cc7f4a8907a0b352204f3d561cc55 Log: FIXED JENKINS-23248 Seeing strange "Transport endpoint is not connected" exception s.shutdownInput() fails with the following exception, even though s.isInputShutdown() is reporting false: java.net.SocketException: Transport endpoint is not connected at sun.nio.ch.SocketChannelImpl.shutdown(Native Method) at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:667) at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:378) at hudson.remoting.SocketChannelStream$1.close(SocketChannelStream.java:39) at sun.nio.ch.ChannelInputStream.close(ChannelInputStream.java:113) at javax.crypto.CipherInputStream.close(CipherInputStream.java:296) at java.io.BufferedInputStream.close(BufferedInputStream.java:468) at hudson.remoting.FlightRecorderInputStream.close(FlightRecorderInputStream.java:112) at hudson.remoting.ChunkedInputStream.close(ChunkedInputStream.java:102) at hudson.remoting.ChunkedCommandTransport.closeRead(ChunkedCommandTransport.java:50) at hudson.remoting.Channel.terminate(Channel.java:795) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) This bug report may be related: http://bugs.java.com/view_bug.do?bug_id=4516760 If we fail to call s.close(), a socket will leak, so swallowing this exception and have the code execute "s.close()" Compare: https://github.com/jenkinsci/remoting/compare/d1905acf329e...c90fc463923c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ChunkedInputStream.java src/main/java/hudson/remoting/ChunkedOutputStream.java http://jenkins-ci.org/commit/remoting/fc5cf1a6a91d255333eff4ec936d55e5719e773c Log: JENKINS-23248 ChunkcedInputStream.close() wasn't closing the underlying stream This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Damon G commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Hi Daniel, so are you all set with help? Matt pinpointed the version of the remoting library. Looks like there was a pretty major refactoring done between 2.37 and 2.38. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Daniel Beck commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. I pinged Kohsuke about it, but he was busy with something else at the time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Daniel Beck updated JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Change By: Daniel Beck (01/Jul/14 7:06 PM) Labels: jenkins remoting Component/s: core Component/s: cli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Daniel Beck commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Adjusted issue metadata based on Matthew Reiter's comment. Damon G: If you could try doing the same to confirm you're seeing the same issue would be helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Matthew Reiter commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Damon and I are working on the same system, so I can confirm he is seeing the same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
