Changeset: 347349c981f2
Author:jjh
Date: 2011-06-09 09:13 -0700
URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/347349c981f2
7052782: Two langtools regression tests fail due to fix for 7034977 which
removed the invokeGeneric method
Summary: Change the tests to call invoke ins
Hi Chris,
Chris Hegarty said the following on 06/10/11 02:05:
I looks like this change may break the UID spec.
"# time, a long equal to a time (as returned by
System.currentTimeMillis()) at which the VM that this UID was generated
in was alive, or zero for a well-known UID "
'time' may no
On 09/06/2011 17:05, Chris Hegarty wrote:
I looks like this change may break the UID spec.
"# time, a long equal to a time (as returned by
System.currentTimeMillis()) at which the VM that this UID was
generated in was alive, or zero for a well-known UID "
'time' may no longer be equal to
I looks like this change may break the UID spec.
"# time, a long equal to a time (as returned by
System.currentTimeMillis()) at which the VM that this UID was generated
in was alive, or zero for a well-known UID "
'time' may no longer be equal to currentTimeMillis.
It looks like count is in
7049774 : UID construction appears to hang if time changed backwards
I'm looking for code review of above reported issue. If system clock goes
backwards on rmi server with active clients and 64k UID boundary is hit,
the server will wait until system time progresses past the time at
which UID cl
