flowable/flowable-engine · error · FlowableException

Expecting a SpringProcessEngineConfiguration for the Camel m

Error message

Expecting a SpringProcessEngineConfiguration for the Camel module.

What it means

SpringCamelBehavior.resolveCamelContext requires the process engine configuration to be a SpringProcessEngineConfiguration so it can access the Spring ApplicationContext and resolve the CamelContext bean. Flowable throws this FlowableException when the configuration is of another type (or the lookup otherwise fails), wrapped as cause when an exception occurs during resolution.

Source

Thrown at modules/flowable-camel/src/main/java/org/flowable/camel/SpringCamelBehavior.java:85

            return (CamelContext) compatibilityHandler.getCamelContextObject(camelContextValue);

        } else {
            // Convert it to a SpringProcessEngineConfiguration. If this doesn't work, throw a RuntimeException.
            try {
                SpringProcessEngineConfiguration springConfiguration = (SpringProcessEngineConfiguration) engineConfiguration;
                if (StringUtils.isEmpty(camelContextValue)) {
                    camelContextValue = springConfiguration.getDefaultCamelContext();
                }

                // Get the CamelContext object and set the super's member variable.
                Object ctx = springConfiguration.getApplicationContext().getBean(camelContextValue);
                if (!(ctx instanceof SpringCamelContext)) {
                    throw new FlowableException("Could not find CamelContext named " + camelContextValue + ".");
                }
                return (SpringCamelContext) ctx;

            } catch (Exception e) {
                throw new FlowableException("Expecting a SpringProcessEngineConfiguration for the Camel module.", e);
            }
        }
    }

    
}

View on GitHub (pinned to d6d39ce1c6)

Solutions

1. Use SpringProcessEngineConfiguration to build the process engine when integrating with the flowable-camel module.
2. If running standalone, register the CamelContext directly on the camel behavior instead of relying on Spring lookup (or use the non-Spring CamelBehavior).
3. Verify the engine initialization path: in Spring, declare the engine via processEngineConfiguration bean so the Spring config type is used.
4. Inspect the wrapped cause exception in the FlowableException for the underlying lookup failure.

Example fix

// before
ProcessEngineConfiguration cfg = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration();
// after
SpringProcessEngineConfiguration cfg = new SpringProcessEngineConfiguration();
cfg.setApplicationContext(applicationContext);

if (!(processEngineConfiguration instanceof SpringProcessEngineConfiguration)) {
    throw new IllegalStateException("flowable-camel requires SpringProcessEngineConfiguration");
}

if (cfg instanceof org.flowable.engine.spring.SpringProcessEngineConfiguration springCfg) { /* Spring lookup available */ }

try {
    return springCamelBehavior.getCamelContext();
} catch (FlowableException e) {
    if (e.getMessage().contains("Expecting a SpringProcessEngineConfiguration")) {
        // rebuild engine with SpringProcessEngineConfiguration
    }
    throw e;
}

When it happens

Trigger: Running the flowable-camel module with a standalone (non-Spring) ProcessEngineConfiguration, e.g. ProcessEngineConfigurationImpl built programmatically or via default engine bootstrap, while camel behavior tries to resolve a Spring-managed CamelContext.

Common situations: Bootstrapping the engine outside of Spring (tests, plain Java main) but using the Spring camel behavior; engine built by a non-Spring activiti/flowable configuration class; migrating from Spring setup to standalone without switching camel context resolution.

Related errors

• Could not find CamelContext named ${camelContextValue}.
• no org.flowable.app.engine.AppEngine defined in the applicat
• transactionManager is required property for SpringAppEngineC
• Initiator header '${processInitiatorHeaderName}': Value must
• Consumer not defined for ${endpointUri}

AI-assisted analysis of flowable/flowable-engine@d6d39ce1c6 (2026-09-11). Data as JSON: /api/errors/35f6a44931a82a5a. Report an issue: GitHub.