Hi Mandy,
Isn't this kind of change risky? With static initialization you know
that once the VM gets up and running then everything is in place. But
with lazy-initialization (and using reflection no less!) there's a
danger that when you try to initialize you're more likely to fail due to
lack
Changeset: 850869f70213
Author:mcimadamore
Date: 2009-03-05 17:24 +
URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/850869f70213
6467183: javac fails to raise unchecked warning on cast of parameterized
generic subclass
Summary: cleanup code for generating unchecked cast w
> Date: Thu, 05 Mar 2009 16:05:52 +
> From: alan.bate...@sun.com
>... The issue will
> likely come down to the meaning of the value passed to the
> MaxDirectMemorySize option. Would I be correct to say that the original
> intention was to lim
Changeset: da9d0283a496
Author:valeriep
Date: 2009-03-03 19:50 -0800
URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/da9d0283a496
6812738: SSL stress test with GF leads to 32 bit max process size in less than
5 minutes with PCKS11 provider
Summary: Removed finalize() and add more e
Mark Reinhold wrote:
:
The original intent was to limit the total capacity, measured in bytes,
of all direct buffers. Additional memory allocated due to rounding the
size of each direct buffer up to the nearest page size was not to be
counted.
We assumed that large pages wouldn't be an issue --
On 03/05/09 04:18, David Holmes - Sun Microsystems wrote:
Hi Mandy,
Isn't this kind of change risky? With static initialization you know
that once the VM gets up and running then everything is in place. But
with lazy-initialization (and using reflection no less!) there's a
danger that when yo
Hi Mandy,
Note that my main concern is the use of reflection. If the class
involved has not previously had it's reflection objects initialized then
getDeclaredMethod can lead to a lot of native and Java-level allocation
(I'm assuming this hasn't changed a great deal from the Java 5 code).
Ev
