[ https://issues.apache.org/jira/browse/HADOOP-11674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348578#comment-14348578 ]
Hudson commented on HADOOP-11674: --------------------------------- FAILURE: Integrated in Hadoop-Yarn-trunk #857 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/857/]) HADOOP-11674. oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static. (Sean Busbey via yliu) (yliu: rev 5e9b8144d54f586803212a0bdd8b1c25bdbb1e97) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/CryptoInputStream.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/CryptoOutputStream.java > oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static > --------------------------------------------------------------------------- > > Key: HADOOP-11674 > URL: https://issues.apache.org/jira/browse/HADOOP-11674 > Project: Hadoop Common > Issue Type: Bug > Components: io > Affects Versions: 2.6.0 > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Critical > Fix For: 2.7.0 > > Attachments: HADOOP-11674.1.patch > > > A common optimization in the io classes for Input/Output Streams is to save a > single length-1 byte array to use in single byte read/write calls. > CryptoInputStream and CryptoOutputStream both attempt to follow this practice > but mistakenly mark the array as static. That means that only a single > instance of each can be present in a JVM safely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)