Reviewed-by: serb, anthony

Reviewed-by: serb, anthony

Reviewed-by: serb, flar

Reviewed-by: serb, azvegint

8031701: java/lang/management/ThreadMXBean/Locks.java: Thread WaitingThread is expected to wait on Object but got null Thread.State = RUNNABLE
Reviewed-by: mchung, dsamersoff

8032678: [TESTBUG] sun/misc/Version/Version.java doesn't understand two-digit HotSpot minor version numbers
Reviewed-by: kvn

Reviewed-by: dholmes, jbachorik

Reviewed-by: ksrini, sherman

6309226: TEST: java/lang/management/ThreadMXBean/SynchronizationStatistics.java didn't check Thread.sleep
Reviewed-by: dholmes, mchung

8031502: JSR292: IncompatibleClassChangeError in LambdaForm for CharSequence.toString() method handle type converter
Reviewed-by: sundar, lagergren, drchase

Reviewed-by: darcy

Reviewed-by: alanb

Summary: updated files with 2011, 2012 and 2013 years according to the file's last updated date
Reviewed-by: tbell, lancea, chegar

Reviewed-by: art, serb

Summary: setLevel(INFO) was called too early on root logger, causing the value found in configuration file to be later ignored.
Reviewed-by: mchung

Reviewed-by: mduigou, psandoz

Reviewed-by: okutsu, mfang

Reviewed-by: sherman, chegar, scolebourne

Reviewed-by: dfuchs, lancea, ulfzibis

Reviewed-by: weijun, mullan, wetmore

Reviewed-by: mchung

Reviewed-by: dholmes

Reviewed-by: dfuchs, sla

Reviewed-by: sla

Reviewed-by: dholmes, sla, mchung

8031420: sun/management/jmxremote/bootstrap/CustomLauncherTest.java fails on some platforms: Unable to locate 'libjvm.so'
Reviewed-by: sla, chegar, sjiang

8029263: user's default browser can not launch after we click the button, and there is an IOException shown in the log text (java.io.IOException)
Reviewed-by: anthony, serb

8029809: sun/management/jmxremote/bootstrap/CustomLauncherTest.java fails intermittently with "Operation not permitted"
Reviewed-by: sla

8029890: java/lang/management/ThreadMXBean/ThreadBlockedCount.java fails: Blocked thread has 4 blocked counts. Expected 3
Reviewed-by: sla

Summary: The test needs to keep a strong reference on its loggers otherwise the modification of the logger level may only be transient.
Reviewed-by: chegar

8031068: java/util/logging/ParentLoggersTest.java: checkLoggers: getLoggerNames() returned unexpected loggers
Summary: The test was not keeping any strong reference on the loggers it created allowing for them to be garbage collected too early.
Reviewed-by: mchung, chegar

Summary: adds a new test for the deadlock found in JDK-8027670 and fixed in JDK-8029281.
Reviewed-by: mchung

Reviewed-by: alexp, alexsch

8030187: TEST_BUG: java/util/logging/Logger/setResourceBundle/TestSetResourceBundle.java failing again
Summary: Yet another issue with Loggers being gc'ed too early.
Reviewed-by: mchung

Summary: This is a test bug - loggers held in local variables can be arbitrarily gc'ed if that variable is no longer used. The fix makes sure that the loggers won't be arbitrarily gc'ed before the test is complete.
Reviewed-by: mchung

Reviewed-by: okutsu

Reviewed-by: psandoz

Reviewed-by: alanb

Reviewed-by: mullan

Reviewed-by: pchelko, serb