-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b37
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8085123 | emb-9 | Daniel Fuchs | P4 | Resolved | Fixed | team |
FileHandler defines 'limit' as an int - which doesn't allow more than ~ 2^31 bytes (~ 2 gb) in a log. But this is impaired by a bug that can let MeteredStream.written overflow and prevents the log from wrapping.
The proposal is to allow for 'long' limits and detect properly if/when MeteredStream.written overflows.
See http://mail.openjdk.java.net/pipermail/core-libs-dev/2014-August/028280.html
The proposal is to allow for 'long' limits and detect properly if/when MeteredStream.written overflows.
See http://mail.openjdk.java.net/pipermail/core-libs-dev/2014-August/028280.html
- backported by
-
JDK-8085123 FileHandler should allow 'long' limits and handle overflow of MeteredStream.written.
-
- Resolved
-
- duplicates
-
JDK-8028786 FileHandler.MeteredStream inner class could be made static (and final?)
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-