Let's break down why you're hitting this InvalidRequestException and how to fix it. The core issue is that the process engine you're creating programmatically isn't being registered with Camunda's global engine registry, or your configuration is missing critical details that prevent the engine from initializing properly.

1. Ensure Your Engine is Registered with Camunda's Registry #

When you create a process engine via the Java API, Camunda doesn't automatically track it unless you explicitly register it. Here's how to adjust your createProcessEngine() method to fix this:

import org.camunda.bpm.engine.ProcessEngine;
import org.camunda.bpm.engine.ProcessEngines;
import org.camunda.bpm.engine.impl.cfg.StandaloneProcessEngineConfiguration;
import org.camunda.bpm.application.ServletProcessApplication;
import org.camunda.bpm.application.annotation.ProcessApplication;

@ProcessApplication("MultiTenantProcessApp")
public class MultiTenantProcessApplicationEngine extends ServletProcessApplication {

  public ProcessEngine createProcessEngine() {
    // Configure MSSQL connection and engine settings
    StandaloneProcessEngineConfiguration config = new StandaloneProcessEngineConfiguration()
      // Match the engine name referenced in your error
      .setProcessEngineName("camundaProcessEngine")
      // MSSQL JDBC URL (adjust host/port if your DB is not local)
      .setJdbcUrl("jdbc:sqlserver://localhost:1433;databaseName=camunda2db;encrypt=false")
      .setJdbcUsername("camunda2")
      .setJdbcPassword("camunda2")
      .setJdbcDriver("com.microsoft.sqlserver.jdbc.SQLServerDriver")
      // Tell Camunda to use MSSQL schema handling
      .setDatabaseType("mssql")
      // Auto-create/update schema (only use in development!)
      .setDatabaseSchemaUpdate(StandaloneProcessEngineConfiguration.DB_SCHEMA_UPDATE_TRUE)
      // Enable multi-tenant support for your use case
      .setTenantCheckEnabled(true);

    // Build the engine instance
    ProcessEngine processEngine = config.buildProcessEngine();
    
    // Critical step: Register the engine with Camunda's global registry
    ProcessEngines.registerProcessEngine(processEngine);
    
    return processEngine;
  }
}

2. Verify Dependencies Are Correct #

Make sure your pom.xml includes the necessary MSSQL driver and Camunda core dependencies:

<!-- MSSQL JDBC Driver -->
<dependency>
  <groupId>com.microsoft.sqlserver</groupId>
  <artifactId>mssql-jdbc</artifactId>
  <version>12.4.2.jre11</version>
</dependency>

<!-- Camunda Engine (adjust version to match your setup) -->
<dependency>
  <groupId>org.camunda.bpm</groupId>
  <artifactId>camunda-engine</artifactId>
  <version>7.21.0</version>
</dependency>

<!-- Camunda Web Application (if you're using the web UI) -->
<dependency>
  <groupId>org.camunda.bpm.webapp</groupId>
  <artifactId>camunda-webapp</artifactId>
  <version>7.21.0</version>
  <type>war</type>
</dependency>

3. Confirm Your Process Application is Deployed Properly #

Since you're extending ServletProcessApplication, ensure your app is registered correctly:

• The @ProcessApplication annotation (added in the code above) tells Camunda to recognize this class as a process application.
• If you're using a traditional web.xml, add this servlet mapping to trigger the process application deployment:

  <servlet>
    <servlet-name>MultiTenantProcessApp</servlet-name>
    <servlet-class>org.camunda.bpm.application.impl.ServletProcessApplication</servlet-class>
    <init-param>
      <param-name>processApplicationClass</param-name>
      <param-value>your.package.name.MultiTenantProcessApplicationEngine</param-value>
    </init-param>
  </servlet>
  <servlet-mapping>
    <servlet-name>MultiTenantProcessApp</servlet-name>
    <url-pattern>/camunda/*</url-pattern>
  </servlet-mapping>
  

4. Check for Silent Initialization Failures #

If the engine fails to initialize (e.g., bad DB connection, missing driver), it won't be registered. Check your application logs for errors like:

• JDBC connection timeouts or authentication failures
• Missing database driver class
• Schema creation errors (if you enabled auto-update)

Key Notes #

• The processEngineName must exactly match the name you use to retrieve the engine later (in your error, it's camundaProcessEngine).
• Disable DB_SCHEMA_UPDATE_TRUE in production—use manual schema migrations instead.
• For multi-tenant workflows, ensure you deploy processes to specific tenants or configure tenant-aware queries after engine initialization.

内容的提问来源于stack exchange，提问作者cj devin