Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-9177

History level "auto" does not work because of incorrect initialization order

    Details

    • Type: Bug Report
    • Status: Open
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: 7.9.0
    • Fix Version/s: None
    • Component/s: engine
    • Labels:
      None

      Description

      When setting ProcessEngineConfiguration.history to "auto", the actual history level is resolved to late, causing for example the BpmnParseListener to still reference a null history level.

      • ProcessEngineConfigurationImpl.buildProcessEngine calls init
      • init calls initDeployers, which creates a BpmnDeployer with the default parse listeners, including HistoryParseListener
      • ProcessEngineConfiguration.history is still null, which gets passed to the HistoryParseListener
      • After init finishes, ProcessEngineImpl constructor is invoked, this resolves the history level by calling executeSchemaOperations
      • Starting a process the fails with
      ERROR [2018-07-04 14:56:00,857] io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request: 06459bb31fde9d91
      ! java.lang.NullPointerException: null
      ! at org.camunda.bpm.engine.impl.history.parser.HistoryParseListener.addActivityHandlers(HistoryParseListener.java:233)
      ! at org.camunda.bpm.engine.impl.history.parser.HistoryParseListener.parseStartEvent(HistoryParseListener.java:142)
      ! at org.camunda.bpm.engine.impl.bpmn.parser.BpmnParse.parseStartEvents(BpmnParse.java:855)
      

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            jhorstmann Jörn Horstmann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development