apache/beam · error · IllegalStateException

SolaceIO.Write.UnboundedSolaceWriter.Context: No context pro

Error message

SolaceIO.Write.UnboundedSolaceWriter.Context: No context provided

What it means

UnboundedSolaceWriter requires an active pipeline context (either a ProcessContext for streaming output or a FinishBundleContext with a BoundedWindow) to emit elements downstream. When neither is set on the writer's Context object, output() cannot route the message and throws this IllegalStateException. It signals an internal lifecycle/configuration error rather than a user data problem.

Source

Thrown at sdks/java/io/solace/src/main/java/org/apache/beam/sdk/io/solace/write/UnboundedSolaceWriter.java:368

        T output,
        @Nullable Instant timestamp, // Not required for windowed context
        @Nullable BoundedWindow window) { // Not required for windowed context
      if (windowedContext != null) {
        windowedContext.output(tag, output);
      } else if (finishBundleContext != null) {
        if (timestamp == null) {
          throw new IllegalStateException(
              "SolaceIO.Write.UnboundedSolaceWriter.Context: Timestamp is required for a"
                  + " FinishBundleContext.");
        }
        if (window == null) {
          throw new IllegalStateException(
              "SolaceIO.Write.UnboundedSolaceWriter.Context: BoundedWindow is required for a"
                  + " FinishBundleContext.");
        }
        finishBundleContext.output(tag, output, timestamp, window);
      } else {
        throw new IllegalStateException(
            "SolaceIO.Write.UnboundedSolaceWriter.Context: No context provided");
      }
    }
  }
}

View on GitHub (pinned to 12126d8942)

Solutions

1. Ensure the writer Context is populated with a ProcessContext (streaming path) or a FinishBundleContext plus BoundedWindow (batch/finish-bundle path) before calling output()
2. Upgrade the SolaceIO connector and Beam SDK to matching supported versions so lifecycle contexts are injected correctly
3. If running on a custom runner, verify it invokes FinishBundle with a BoundedWindow as SolaceIO expects
4. In tests, use Beam's TestPipeline / DoFnTester so contexts are provided rather than constructing the writer manually

Example fix

// before
UnboundedSolaceWriter.Context ctx = new UnboundedSolaceWriter.Context();
writer.publishResults(element, ctx); // no context set -> IllegalStateException
// after
UnboundedSolaceWriter.Context ctx = new UnboundedSolaceWriter.Context()
    .withFinishBundleContext(finishBundleContext, outputTag, boundedWindow);
writer.publishResults(element, ctx);

if (ctx.getProcessContext() == null && ctx.getFinishBundleContext() == null) {
  throw new IllegalStateException("Solace writer context not initialized before output");
}

When it happens

Trigger: The writer's Context was constructed without calling either withProcessContext or withFinishBundleContext (with a BoundedWindow) before publishResults invokes output(); typically a mis-wired custom writer setup or a Beam runner lifecycle change that skips bundle finalization context injection.

Common situations: Custom or forked Beam runners that do not supply a FinishBundleContext; unit tests instantiating UnboundedSolaceWriter directly without populating its Context; regressions after Beam core changes to DoFn lifecycle context propagation.

Understand the failure class

Background: "is required", "must be set", "missing required field": configuration validation errors across open-source libraries — this error's family across 36 libraries.

Related errors

• Illegal access to pipeline after visitor traversal was compl
• One or more ErrorHandlers aren't closed, and this pipeline c
• Error collections cannot be added after Error Handler is clo
• ErrorHandler must be finalized before the output can be retu
• Output coders were already specified

AI-assisted analysis of apache/beam@12126d8942 (2026-09-13). Data as JSON: /api/errors/5ca0fbe33d6628d3. Report an issue: GitHub.