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

Exception when opening cockpit on mysql/wildfly

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Won't Fix
    • L3 - Default
    • None
    • 7.7.0
    • cockpit
    • None
    • Wildfly 10, RHEL7, MariaDb 10.2, Java 8

    Description

      When opening the cockpit in Wildfly an exception is thrown:

      [...]
      java.sql.SQLException: XAER_OUTSIDE: Some work is done outside global transaction.
      [....]
      ### The error may exist in org/camunda/bpm/engine/impl/mapping/entity/ProcessDefinition.xml
      ### The error may involve org.camunda.bpm.engine.impl.persistence.entity.ProcessDefinitionEntity.selectProcessDefinition
      ### The error occurred while executing a query
      

      It seems that the cockpit is misbehaving and running local transactions that conflicts with some xa-transactions. The problem may also involve autocommits and the jdbc driver? This problem in general is discussed here: http://forum.spring.io/forum/spring-projects/data/50569-jta-transaction-issue-with-mysql

      The problem has been reproduced with the standalone wildfly distribution and the configuration (standalone.xml) is attached along with the complete stack trace.

      The exception goes away if we add <no-tx-separate-pools /> to the pools config, but we don't want to do that as it creates another pool on the server.

      I have also found another user seeing the same problem with version 7.5:
      https://stackoverflow.com/questions/42384335/xa-datasource-and-cockpit

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1. camunda.log
            98 kB
            Egil Risvoll Sørensen
          2. standalone.xml
            26 kB
            Egil Risvoll Sørensen

          Activity

            People

              Unassigned Unassigned
              egil Egil Risvoll Sørensen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce