RFR: 7159567 - inconsistent configuration of MemoryHandler (original) (raw)

Mandy Chung mandy.chung at oracle.com
Thu Sep 27 02:44:28 UTC 2012

Hi Jim,

On 9/26/2012 2:19 PM, Jim Gish wrote:

Please review http://cr.openjdk.java.net/~jgish/Bug7159567-set-MemoryHandler-target/ <http://cr.openjdk.java.net/%7Ejgish/Bug7159567-set-MemoryHandler-target/>

Overview - currently you can sub-class java.util.logging.MemoryHandler and specify its configuration in a logging.properties file via the classname. For example, if com.foo.MyMemoryHandler extends MemoryHandler, you can have: logging.properties: com.foo.MyMemoryHandler.push=WARNING com.foo.MyMemoryHandler.level=FINEST The current implementation does use the.* properties. However I couldn't find it from the j.u.logging specification. Did I miss any javadoc that mentions this?

Per the j.u.l.MemoryHandler specification, it only reads "java.util.logging.MemoryHandler.*" properties but not the properties with the subclass name.

*Configuration:

I looked at the change history and found that the change to read property using the classname as the prefix (rather than j.u.l.MemoryHandler) was done in JDK 5 in the fix for 4635817.

This isn't related to the bug you're fixing but I think this deserves to investigate whether this was an intended spec change at that time; if so, a spec update to clarify this behavior would be good.

Thanks Mandy

More information about the core-libs-dev mailing list