From b08d45f1e070cdb3fdceccf0b5432c927378b7a3 Mon Sep 17 00:00:00 2001
From: ysuenaga <unknown>
Date: Fri, 23 Nov 2018 16:36:07 +0900
Subject: [PATCH] 8213015: Inconsistent settings between JFR.configure and
 -XX:FlightRecorderOptions Reviewed-by: mgronlun, egahlin

---
 test/jdk/jfr/jcmd/TestJcmdConfigure.java | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/test/jdk/jfr/jcmd/TestJcmdConfigure.java b/test/jdk/jfr/jcmd/TestJcmdConfigure.java
index 81146d9f3..c77bf2fbc 100644
--- a/test/jdk/jfr/jcmd/TestJcmdConfigure.java
+++ b/test/jdk/jfr/jcmd/TestJcmdConfigure.java
@@ -99,9 +99,7 @@ public class TestJcmdConfigure {
 
     private static void testNegative(String configName, Object value) {
         try {
-            // Syntactically invalid arguments are catched by the JCMD framework where an error code of 1 is returned.
-            // Syntactically valid arguments that are semantically invalid (invalid value ranges for example) are handled by JFR code, it will always return a value of 0.
-            JcmdHelper.jcmd(configName.equals(UNSUPPORTED_OPTION) ? 1 : 0, "JFR.configure", configName + "=" + value);
+            JcmdHelper.jcmd(1, "JFR.configure", configName + "=" + value);
         } catch(Exception e) {
             testExceptions.add(e);
         }
-- 
GitLab