[JIRA] (JENKINS-43199) Credentials Binding plugin causes File Descriptor leak

2017-03-29 Thread ebut...@sourceallies.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliott Butler commented on  JENKINS-43199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials Binding plugin causes File Descriptor leak   
 

  
 
 
 
 

 
 This may potentially cause the same issue for the pipeline variant, but is not used by us at this time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-43199) Credentials Binding plugin causes File Descriptor leak

2017-03-29 Thread ebut...@sourceallies.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliott Butler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43199  
 
 
  Credentials Binding plugin causes File Descriptor leak   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2017/Mar/29 6:14 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Elliott Butler  
 

  
 
 
 
 

 
 Our deployment of Jenkins with this plugin is currently on an NFS share. In testing a job with this plugin, a file descriptor was apparently left open. We found this out when attempting to delete the test job after it ran. (It was a simple echo job to make sure masking worked as expected, nothing else) The issue appears to be related to the anonymous sub-class of the LineTransformationOutputStream class returned by the Wrapper class and similar to the bug resolved in JENKINS-28409 for EnvInject. The sub-class needs to clean up it's parent outputstream and the super class on close.   

 

@Override
 public void close() throws IOException {
 super.close();
 out.close();
 }