commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-253) Test Failures using IBM JDK
Date Sun, 17 Oct 2010 22:59:22 GMT

    [ https://issues.apache.org/jira/browse/IO-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921916#action_12921916
] 

Niall Pemberton commented on IO-253:
------------------------------------

I managed to download IBM's 1.6 JDK version (eclipse bundle, which is the only windows one
available for me) from the following location:

    * https://www.ibm.com/developerworks/java/jdk/

I can reproduce the problem with the UTF16 test in WriterOutputStream handling. From debugging,
the last call to CharsetDecoder's  decode(decoderIn, decoderOut, endOfInput) method where
the *endOfInput* parameter is *true* (called by the close() method) causes the CharBuffer's
position to be reset to zero. As a result the flushOutput() method does nothing.

Why this happens only for UTF-16 I don't know. The source code for the IBM JDK is not available
and so it is not possible to determine what exactly its doing. WriterOutputStream is correctly
implementing the contract with CharsetDecoder by calling the decode() method a final time,
indicating endOfInput and so my conclusion is this is a bug in the IBM JDK.

I don't have access to IBM's JDK 1.5 and so theres nothing I can do to look at the failing
FileCleaningTracker tests. These tests though fill up memory to try and get the garbage collector
to reclaim some PhantomReferences. Once the garbage collector does that, then the tests check
the functionality of FileCleaningTracker. The test failing with an OutOfMemory error means
that the test is not operating properly and never getting to the point of actually testing
FileCleaningTracker. Therefore it doesn't tell us anything about whether FileCleaningTracker
works or not on IBM's JDK 1.5.


> Test Failures using IBM JDK
> ---------------------------
>
>                 Key: IO-253
>                 URL: https://issues.apache.org/jira/browse/IO-253
>             Project: Commons IO
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Niall Pemberton
>            Priority: Minor
>
> Jörg Schaible reports the following test failures in RC5 of Commons IO 2.0
>     * http://markmail.org/message/eoo5bk6n3pfsvfwk
> "IBM JDK 1.5 does not like the OOME handling in the FileCleanerTestCase and FileCleanerTrackingTestCase,
while IBM JDK 1.6 has problems with the WriterOutputStream handling UTF16."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message