Time ago I setup a camunda-bpmn engine via docker. Starting the composer-file I added the following configuration-line to the camunda-configs:
<property name="jobExecutorActivate">true</property>
Unfortunalty I run into two failures:
- The Workers don’t pull up any ServiceTasks (http-connector). It seems that they suddenly stop working
- After some time the engine responds with an “500”-Error Code
Error in persistance layer
I connected into the container to have a look into the log files, but can’t find any error logs.
Do I need to configure camunda to write error logs? What can I do, to find (and fix) the root cause?
following my current composer-file:
version: "3"
services:
camunda:
image: camunda/camunda-bpm-platform:7.16.0-alpha5
environment:
- DB_DRIVER=com.mysql.cj.jdbc.Driver
- DB_URL=jdbc:mysql://mysql:3306/process-engine?sendFractionalSeconds=false
- DB_USERNAME=camunda
- DB_PASSWORD=camunda
- WAIT_FOR=mysql:3306
links:
- mysql
ports:
- "8080:8080"
restart: unless-stopped
volumes:
- $PWD/bpm-platform.xml:/camunda/conf/bpm-platform.xml
mysql:
image: mysql:5.7
environment:
- MYSQL_ROOT_PASSWORD=camunda
- MYSQL_USER=camunda
- MYSQL_PASSWORD=camunda
- MYSQL_DATABASE=process-engine
ports:
- "3306:3306"
and the configuration file:
<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform xmlns="http://www.camunda.org/schema/1.0/BpmPlatform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.camunda.org/schema/1.0/BpmPlatform http://www.camunda.org/schema/1.0/BpmPlatform ">
<job-executor>
<job-acquisition name="default" />
</job-executor>
<process-engine name="default">
<job-acquisition>default</job-acquisition>
<configuration>org.camunda.bpm.engine.impl.cfg.StandaloneProcessEngineConfiguration</configuration>
<datasource>java:jdbc/ProcessEngine</datasource>
<properties>
<property name="history">full</property>
<property name="databaseSchemaUpdate">true</property>
<property name="authorizationEnabled">true</property>
<property name="jobExecutorDeploymentAware">true</property>
<property name="historyCleanupBatchWindowStartTime">00:01</property>
<property name="jobExecutorActivate">true</property>
</properties>
<plugins>
<!-- plugin enabling Process Application event listener support -->
<plugin>
<class>org.camunda.bpm.application.impl.event.ProcessApplicationEventListenerPlugin</class>
</plugin>
<!-- plugin enabling integration of camunda Spin -->
<plugin>
<class>org.camunda.spin.plugin.impl.SpinProcessEnginePlugin</class>
</plugin>
<!-- plugin enabling connect support -->
<plugin>
<class>org.camunda.connect.plugin.impl.ConnectProcessEnginePlugin</class>
</plugin>
<!-- LDAP CONFIGURATION -->
<!-- Uncomment this section in order to enable LDAP support for this process engine -->
<!-- Adjust configuration, see ( http://docs.camunda.org/latest/guides/user-guide/#process-engine-identity-service-the-ldap-identity-service ) -->
<!--
<plugin>
<class>org.camunda.bpm.identity.impl.ldap.plugin.LdapIdentityProviderPlugin</class>
<properties>
<property name="serverUrl">ldaps://localhost:4334/</property>
<property name="acceptUntrustedCertificates">false</property>
<property name="managerDn">uid=jonny,ou=office-berlin,o=camunda,c=org</property>
<property name="managerPassword">s3cr3t</property>
<property name="baseDn">o=camunda,c=org</property>
<property name="userSearchBase"></property>
<property name="userSearchFilter">(objectclass=person)</property>
<property name="userIdAttribute">uid</property>
<property name="userFirstnameAttribute">cn</property>
<property name="userLastnameAttribute">sn</property>
<property name="userEmailAttribute">mail</property>
<property name="userPasswordAttribute">userpassword</property>
<property name="groupSearchBase"></property>
<property name="groupSearchFilter">(objectclass=groupOfNames)</property>
<property name="groupIdAttribute">cn</property>
<property name="groupNameAttribute">cn</property>
<property name="groupMemberAttribute">member</property>
<property name="sortControlSupported">false</property>
</properties>
</plugin>
-->
<!-- LDAP CONFIGURATION -->
<!-- The following plugin allows you to grant administrator authorizations to an existing LDAP user -->
<!--
<plugin>
<class>org.camunda.bpm.engine.impl.plugin.AdministratorAuthorizationPlugin</class>
<properties>
<property name="administratorUserName">admin</property>
</properties>
</plugin>
-->
</plugins>
</process-engine>
</bpm-platform>