apache/flink · error · RuntimeException

Jar file %s does not exist

Error message

Jar file %s does not exist

What it means

Error "Jar file %s does not exist" thrown in apache/flink.

Source

Thrown at flink-clients/src/main/java/org/apache/flink/client/deployment/application/PackagedProgramApplicationEntry.java:101

        this.handleFatalError = handleFatalError;
        this.submitFailedJobOnApplicationError = submitFailedJobOnApplicationError;
        this.shutDownOnFinish = shutDownOnFinish;
    }

    @Override
    public AbstractApplication getApplication(
            PermanentBlobService blobService,
            Collection<JobInfo> recoveredJobInfos,
            Collection<JobInfo> recoveredTerminalJobInfos) {
        File jarFile;
        try {
            jarFile = blobService.getFile(applicationId, userJarInfo.getJarBlobKey());
        } catch (Exception e) {
            throw new RuntimeException("Failed to get user jar file from blob", e);
        }

        if (!jarFile.exists()) {
            throw new RuntimeException(String.format("Jar file %s does not exist", jarFile));
        }

        PackagedProgram program;
        try {
            program =
                    PackagedProgram.newBuilder()
                            .setJarFile(jarFile)
                            .setEntryPointClassName(entryClass)
                            .setConfiguration(configuration)
                            .setUserClassPaths(getClasspaths())
                            .setArguments(programArgs)
                            .build();
        } catch (Exception e) {
            throw new RuntimeException(
                    String.format(
                            "Failed to create PackagedProgram for application %s", applicationId),
                    e);
        }

View on GitHub (pinned to 2f3c205e92)

Solutions

1. Address the cause reported by the error message: Jar file the reported value does not exist
2. Verify the inputs, configuration values, and classpath/dependency setup related to this operation, then retry.

Example fix

Correct the condition described ("Jar file the reported value does not exist") and rerun the job or command.

When it happens

Trigger: Triggered at runtime when the operation fails because: Jar file the reported value does not exist.

Common situations: Commonly caused by misconfiguration, missing dependencies or files, unsupported types or operations, or invalid user input leading to: Jar file the reported value does not exist.

AI-assisted analysis of apache/flink@2f3c205e92 (2026-08-14). Data as JSON: /api/errors/7ff03a05a4ed67f9. Report an issue: GitHub.