|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/main/java/hudson/remoting/ProxyOutputStream.java
src/main/java/hudson/remoting/ProxyWriter.java
http://jenkins-ci.org/commit/remoting/96c670de534de269bcde729a932655842a3aea2a
Log:
[FIXED JENKINS-20769]
When ProxyWriter is finalized, it should attempt to release a remote reference count,
but it shouldn't try to close the stream. For one, the other side that had exported
the writer might be still using it (imagine exporting System.out), and secondly, the
said object could have already been unexported, for example if the closure that brought
ProxyWriter to this side has already returned, since RemoteWriter is auto-unexporting.
Compare ProxyOutputStream impl vs ProxyWriter impl and the difference becomes clearer.