Error starting process in Camunda BPM 7.4.2-ee JBoss that starts in 7.4.0-ee

[mp4...@att.com]

I have a process that will not deploy to into the 7.4.2-ee JBoss distribution, but does deploy into the 7.4.0-ee JBoss distribution. I've searched for resolutions to the error, but cannot find any that reference this specifically.

This error occurs both on a Linux instance as well as a local instance running under Windows.

Project was built with 7.4.2 parent BOM.

Configuration of JBoss in the 7.4.2 instance is similar to that of 7.4.0. However, I did notice differences in the default standalone.xml file that comes with the distribution and the same file after startup. However, the post startup standalone.xml file is materially consistent with the same file of the 7.4.0 distribution.

Any help would be appreciated. Thanks.

The stack trace:

12:04:55,294 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC00001: Failed to start service org.camunda.bpm.platform.process-application-module."deployment.processs1-standalone-0.0.1-SNAPSHOT.war:main".START: org.jboss.msc.service.StartException in service org.camunda.bpm.platform.
process-application-module."deployment.process1-standalone-0.0.1-SNAPSHOT.war:main".START: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
Caused by: java.lang.ExceptionInInitializerError
at org.camunda.spin.impl.xml.dom.format.DomXmlDataFormat.<clinit>(DomXmlDataFormat.java:35)
at org.camunda.spin.impl.xml.dom.format.DomXmlDataFormatProvider.createInstance(DomXmlDataFormatProvider.java:32)
at org.camunda.spin.DataFormats.registerProvider(DataFormats.java:152)
at org.camunda.spin.DataFormats.registerCustomDataFormats(DataFormats.java:140)
at org.camunda.spin.DataFormats.registerDataFormats(DataFormats.java:124)
at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.lookupSpinSerializers(SpinBpmPlatformPlugin.java:59)
at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.initializeVariableSerializers(SpinBpmPlatformPlugin.java:51)
at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.postProcessApplicationDeploy(SpinBpmPlatformPlugin.java:36)
at org.camunda.bpm.container.impl.jboss.service.ProcessApplicationStartService.notifyBpmPlatformPlugins(ProcessApplicationStartService.java:173)
at org.camunda.bpm.container.impl.jboss.service.ProcessApplicationStartService.start(ProcessApplicationStartService.java:146)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
... 3 more
Caused by: java.lang.ClassCastException: org.camunda.spin.impl.xml.dom.DomXmlLogger cannot be cast to org.camunda.commons.logging.BaseLogger
at org.camunda.commons.logging.BaseLogger.createLogger(BaseLogger.java:88)
at org.camunda.spin.impl.xml.dom.DomXmlLogger.<clinit>(DomXmlLogger.java:35)
... 15 more

12:04:55,330 ERROR [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "process1-standalone-0.0.1-SNAPSHOT.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"org.camunda.bpm.platform.process-application-module.\"deployment.process1-standalone-0.0.1-SNAPSHOT.war:main\".START" => "org.jboss.msc.service.StartException in service org.camunda.bpm.platform.process-application-module.\"deployment.process1-standalone-0
.0.1-SNAPSHOT.war:main\".START: Failed to start service
Caused by: java.lang.ExceptionInInitializerError
Caused by: java.lang.ClassCastException: org.camunda.spin.impl.xml.dom.DomXmlLogger cannot be cast to org.camunda.commons.logging.BaseLogger"}}
12:04:55,333 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018224: Unregister web context: /process1-standalone-0.0.1-SNAPSHOT
12:04:56,612 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015877: Stopped deployment process1-standalone-0.0.1-SNAPSHOT.war (runtime-name: process1-standalone-0.0.1-SNAPSHOT.war) in 1284ms

[Sebastian Menski]

Hi,

I assume you started with a fresh 7.4.2 Distro or updated the libraries of the 7.4.0 Distro. Can you share the project which causes this exception?

Cheers,

Sebastian

[venkataraju...@gmail.com]

Hi,

Am trying to deploy the spring application in .... camunda-bpm-jboss-7.5.0-alpha2....and getting the given below errors

It was deployed and running successfully in the older jboss 7.4.0-alpha2 version.

16:09:30,192 INFO  [org.camunda.bpm.container.impl.jboss.service.ProcessAppli

ionDeploymentService] (ServerService Thread Pool -- 71) Deployment summary fo

rocess archive 'UpgradeDf-Process' of process application 'UpgradeDfApplicati

App':

        UpgradeDf.bpmn

        UpgradeDf.png

16:09:30,269 INFO  [org.camunda.bpm.application] (ServerService Thread Pool -

1) ENGINE-07021 ProcessApplication 'UpgradeDfApplication App' registered for

deployments [980ce54c-e44b-11e5-9854-887120524153]. Will execute process defi

ions

        UpgradeDf-Process[version: 1, id: UpgradeDf-Process:1:981103ff-e44b-1

-9854-887120524153]

Deployment does not provide any case definitions.

16:09:30,292 INFO  [org.camunda.spin] (MSC service thread 1-3) SPIN-01010 Dis

ered Spin data format provider: org.camunda.spin.impl.json.jackson.format.Jac

nJsonDataFormatProvider[name = application/json]

16:09:30,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0

1: Failed to start service org.camunda.bpm.platform.process-application-modul

deployment.UpgradeDf-0.1.0-SNAPSHOT.war:main".START: org.jboss.msc.service.St

Exception in service org.camunda.bpm.platform.process-application-module."dep

ment.UpgradeDf-0.1.0-SNAPSHOT.war:main".START: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceC

rollerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecut

java:1145) [rt.jar:1.7.0_51]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecu

.java:615) [rt.jar:1.7.0_51]

        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

Caused by: java.lang.ExceptionInInitializerError

        at org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormat.<c

it>(JacksonJsonDataFormat.java:54)

        at org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormatPro

er.createInstance(JacksonJsonDataFormatProvider.java:37)

        at org.camunda.spin.DataFormats.registerProvider(DataFormats.java:152

        at org.camunda.spin.DataFormats.registerCustomDataFormats(DataFormats

va:140)

        at org.camunda.spin.DataFormats.registerDataFormats(DataFormats.java:

)

        at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.lookupSpinSeria

ers(SpinBpmPlatformPlugin.java:60)

        at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.initializeVaria

Serializers(SpinBpmPlatformPlugin.java:52)

        at org.camunda.spin.plugin.impl.SpinBpmPlatformPlugin.postProcessAppl

tionDeploy(SpinBpmPlatformPlugin.java:37)

        at org.camunda.bpm.container.impl.jboss.service.ProcessApplicationSta

ervice.notifyBpmPlatformPlugins(ProcessApplicationStartService.java:173)

        at org.camunda.bpm.container.impl.jboss.service.ProcessApplicationSta

ervice.start(ProcessApplicationStartService.java:146)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService

rviceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceC

rollerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

        ... 3 more

Caused by: java.lang.ClassCastException: org.camunda.spin.impl.json.jackson.J

sonJsonLogger cannot be cast to org.camunda.commons.logging.BaseLogger

        at org.camunda.commons.logging.BaseLogger.createLogger(BaseLogger.jav

8)

        at org.camunda.spin.impl.json.jackson.JacksonJsonLogger.<clinit>(Jack

JsonLogger.java:35)

        ... 15 more

16:09:30,486 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS

870: Deploy of deployment "UpgradeDf-0.1.0-SNAPSHOT.war" was rolled back with

e following failure message:

{"JBAS014671: Failed services" => {"org.camunda.bpm.platform.process-applicat

-module.\"deployment.UpgradeDf-0.1.0-SNAPSHOT.war:main\".START" => "org.jboss

c.service.StartException in service org.camunda.bpm.platform.process-applicat

-module.\"deployment.UpgradeDf-0.1.0-SNAPSHOT.war:main\".START: Failed to sta

service

    Caused by: java.lang.ExceptionInInitializerError

    Caused by: java.lang.ClassCastException: org.camunda.spin.impl.json.jacks

JacksonJsonLogger cannot be cast to org.camunda.commons.logging.BaseLogger"}}

16:09:30,517 INFO  [org.jboss.web] (ServerService Thread Pool -- 71) JBAS0182

 Unregister web context: /UpgradeDf-0.1.0-SNAPSHOT

16:09:30,647 INFO  [org.apache.catalina.core.ContainerBase.[jboss.web].[defau

host].[/UpgradeDf-0.1.0-SNAPSHOT]] (ServerService Thread Pool -- 71) Closing

ing root WebApplicationContext

16:09:30,655 INFO  [org.springframework.web.context.support.XmlWebApplication

text] (ServerService Thread Pool -- 71) Closing Root WebApplicationContext: s

tup date [Mon Mar 07 16:09:28 IST 2016]; root of context hierarchy

16:09:30,665 INFO  [org.springframework.beans.factory.support.DefaultListable

nFactory] (ServerService Thread Pool -- 71) Destroying singletons in org.spri

ramework.beans.factory.support.DefaultListableBeanFactory@1f71fda7: defining

ns [dataSource,transactionManager,processEngineConfiguration,processEngineSer

e,processEngine,repositoryService,runtimeService,taskService,historyService,m

gementService,org.springframework.context.annotation.internalConfigurationAnn

tionProcessor,org.springframework.context.annotation.internalAutowiredAnnotat

Processor,org.springframework.context.annotation.internalRequiredAnnotationPr

ssor,org.springframework.context.annotation.internalCommonAnnotationProcessor

g.springframework.context.annotation.internalPersistenceAnnotationProcessor,c

att.oce.bpm.camunda.Starter#0,upgradeDfProcessService,org.springframework.con

t.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0];

ot of factory hierarchy

16:09:30,831 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6)

S015877: Stopped deployment UpgradeDf-0.1.0-SNAPSHOT.war (runtime-name: Upgra

f-0.1.0-SNAPSHOT.war) in 348ms

Thanks,

VenkataRaju

9941316666

[thorben....@camunda.com]

Hi,

Don't include the Spin libraries in your application but set a module dependency to the org.camunda.spin.camunda-spin-dataformat-json-jackson module.

Cheers,
Thorben

[venkataraju...@gmail.com]

Hi,

Here is the POM details... and If I deploy it in JBOSS 7.4.0-alpha2, working well. If I deploy in 7.5.0-alpha2, getting the service errors as shown in previous posts.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <groupId>com.att.oce.bpm.camunda</groupId>

  <artifactId>UpgradeDf</artifactId>

  <version>0.1.0-SNAPSHOT</version>

  <packaging>war</packaging>

  <name>UpgradeDf</name>

<properties>

   <camunda.version>7.4.0</camunda.version>

   <spring.version>3.1.2.RELEASE</spring.version>

   <skipTests>true</skipTests>

  <camunda.version75>7.5.0-alpha2</camunda.version75>

   <spring.version323>3.2.3.RELEASE</spring.version323>

</properties>

 <!-- import Camunda BOM to ensure correct versions of Camunda projects -->

  <dependencyManagement>

    <dependencies>

      <dependency>

        <groupId>org.camunda.bpm</groupId>

        <artifactId>camunda-bom</artifactId>

        <version>${camunda.version}</version>

        <scope>import</scope>

        <type>pom</type>

      </dependency>

    </dependencies>

  </dependencyManagement>

  <dependencies>

    <dependency>

      <groupId>org.camunda.bpm</groupId>

      <artifactId>camunda-engine</artifactId>

      <version>${camunda.version}</version>

   <scope>provided</scope>

    </dependency>

    <dependency>

      <groupId>org.camunda.bpm</groupId>

      <artifactId>camunda-engine-spring</artifactId>

    </dependency>

    <dependency>

      <groupId>org.springframework</groupId>

      <artifactId>spring-web</artifactId>

      <version>${spring.version}</version>

    </dependency>

    

    <dependency>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

<version>4.11</version>

<scope>test</scope>

</dependency>

    

    <!-- Shared Process Engine (https://docs.camunda.org/get-started/spring/shared-process-engine/)

    Furthermore, you can delete the dependencies org.springframework:spring-jdbc, com.h2database:h2, and org.slf4j:slf4j-jdk14. 

    -->

    

  

    <dependency>

      <groupId>org.springframework</groupId>

      <artifactId>spring-jdbc</artifactId>

      <version>${spring.version}</version>

    </dependency>

    <dependency>

      <groupId>com.h2database</groupId>

      <artifactId>h2</artifactId>

      <version>1.3.171</version>

    </dependency>  

    <dependency>

      <groupId>org.slf4j</groupId>

      <artifactId>slf4j-jdk14</artifactId>

      <version>1.7.13</version>

    </dependency>

    

    <dependency>

      <groupId>javax.servlet</groupId>

      <artifactId>javax.servlet-api</artifactId>

      <version>3.0.1</version>

      <scope>provided</scope>

    </dependency>

    

    <dependency>

    <groupId>org.camunda.bpm.extension</groupId> 

        <artifactId>camunda-bpm-assert</artifactId> 

        <version>1.1</version>

    </dependency>

    <!-- OPTIONAL: spin process engine plugin -->

    <dependency>

      <groupId>org.camunda.bpm</groupId>

      <artifactId>camunda-engine-plugin-spin</artifactId>

    </dependency>

    <!-- OPTIONAL: spin dataformats -->

    <dependency>

      <groupId>org.camunda.spin</groupId>

      <artifactId>camunda-spin-dataformat-json-jackson</artifactId>

    </dependency>

    <dependency>

      <groupId>org.camunda.spin</groupId>

      <artifactId>camunda-spin-dataformat-xml-dom</artifactId>

    </dependency>

    

    

  </dependencies>

  <build>

    <plugins>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-war-plugin</artifactId>

        <version>2.3</version>

        <configuration>

          <failOnMissingWebXml>false</failOnMissingWebXml>

          <skipTests>${skipTests}</skipTests>

        </configuration>

      </plugin>

      <plugin>

    <artifactId>maven-compiler-plugin</artifactId>

    <executions>

      <execution>

       <id>default-testCompile</id>

       <phase>test-compile</phase>

       <goals>

         <goal>testCompile</goal>

       </goals>

       <configuration>

         <failOnError>false</failOnError>

       </configuration>

      </execution>

    </executions>

  </plugin>

  <plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-surefire-plugin</artifactId>

<version>2.12.4</version>

<configuration>

<skipTests>true</skipTests>

</configuration>

    </plugin>

    </plugins>

  </build>

</project>

Thanks,

VenkataRaju Nandam

9941316666

[thorben....@camunda.com]

Hi,

Why do you have a compile scope dependency to camunda-engine-plugin-spin, camunda-spin-dataformat-json-jackson, and camunda-spin-dataformat-xml-dom? You most likely do not need these in your application.

Cheers,
Thorben

[PEOPLES, MICHAEL P]

Sebastian mentioned the same thing to me and I modified the POM file to set those dependencies to “provided”.  I didn’t actually test it as I had other priorities, but I’m not sure why it would have made any difference.  It just made the war file larger and besides, the process worked in 7.4.0.

 

We have a problem with the 7.4.2 JBoss distribution that is not present in the 7.4.0 JBoss distribution because the exact same process works in 7.4.0.  What is interesting is that a colleague downloaded the exact same distribution that I did, created an extremely simple process and got the same errors.  Therefore, this is not related to my specific processes.  Our dependencies are resolved through an internal Maven (Nexus) repository which is supposedly synchronized to external repositories via proxy.

 

The process, by the way, consists of a start event, single service task with Java class that prints out “Hello, World”, and an end event.  If that process doesn’t work, I’m not sure what else would.  It’s unfortunate that it doesn’t work because when I tried to use Spin in 7.4.0, I had too many issues with it and abandoned it for something else.  I know that 7.4.2 features fixes to Spin which might have resolved these issues.

 

Michael