apache/pulsar · error · IllegalArgumentException

${paramName} cannot be greater than ${maxValue}!

Error message

${paramName} cannot be greater than ${maxValue}!

What it means

Upper-bound check in CmdUtils.maxValueCheck: a CLI parameter exceeded its permitted maximum (maxValue), commonly a percentage or limit capped by the tool; paramName and the option value are the faulty inputs.

Source

Thrown at pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/utils/CmdUtils.java:68

                        invalidFormatException.getLocation().getColumnNr());

                throw new IllegalArgumentException(exceptionMessage);
            } else {
                throw new IllegalArgumentException(ex.getMessage());
            }
        }
    }

    public static boolean positiveCheck(String paramName, long value) {
        if (value <= 0) {
            throw new IllegalArgumentException(paramName + " cannot be less than or equal to 0!");
        }
        return true;
    }

    public static boolean maxValueCheck(String paramName, long value, long maxValue) {
        if (value > maxValue) {
            throw new IllegalArgumentException(paramName + " cannot be greater than " + maxValue + "!");
        }
        return true;
    }
}

View on GitHub (pinned to 820761864e)

Solutions

1. Lower the parameter value to at most the stated maximum

When it happens

Trigger: Thrown at pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/utils/CmdUtils.java:68 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of apache/pulsar@820761864e (2026-09-06). Data as JSON: /api/errors/d1a9cc859c769a32. Report an issue: GitHub.