Upgrade camunda from 7.11 to 7.15 in Wildfly23

Camunda 7 Topics Discussion & Questions
1

Hi,

I am upgrading camunda to latest 7.16. But it is not working in WildFly-23.
Here is the error in startup log:

1

5:59:44,739 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0002: Error booting the container: java.lang.IllegalAccessError: class org.camunda.bpm.container.impl.jboss.util.FixedObjectTypeAttributeDefinition$Builder tried to access private field org.jboss.as.controller.AbstractAttributeDefinitionBuilder.validator (org.camunda.bpm.container.impl.jboss.util.FixedObjectTypeAttributeDefinition$Builder is in unnamed module of loader 'org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0' @691d1148; org.jboss.as.controller.AbstractAttributeDefinitionBuilder is in unnamed module of loader 'org.jboss.as.controller@15.0.1.Final' @17497425)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.util.FixedObjectTypeAttributeDefinition$Builder.build(FixedObjectTypeAttributeDefinition.java:105)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.SubsystemAttributeDefinitons.<clinit>(SubsystemAttributeDefinitons.java:144)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.Attribute.<clinit>(Attribute.java:35)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.BpmPlatformParser1_1$1.<clinit>(BpmPlatformParser1_1.java:93)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.BpmPlatformParser1_1.parse(BpmPlatformParser1_1.java:51)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.BpmPlatformParser1_1$BpmPlatformSubsystemParser.readElement(BpmPlatformParser1_1.java:404)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.16.0//org.camunda.bpm.container.impl.jboss.extension.BpmPlatformParser1_1$BpmPlatformSubsystemParser.readElement(BpmPlatformParser1_1.java:377)
        at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
        at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.parsing.StandaloneXml_18.parseServerProfile(StandaloneXml_18.java:660)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.parsing.StandaloneXml_18.readServerElement(StandaloneXml_18.java:238)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.parsing.StandaloneXml_18.readElement(StandaloneXml_18.java:139)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:150)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
        at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
        at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
        at org.jboss.as.controller@15.0.1.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
        at org.jboss.as.server@15.0.1.Final//org.jboss.as.server.ServerService.boot(ServerService.java:400)
        at org.jboss.as.controller@15.0.1.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:417)
        at java.base/java.lang.Thread.run(Thread.java:834)

Standalone.xml file looks like this

<subsystem xmlns="urn:org.camunda.bpm.jboss:1.1">
            <process-engines>
                <process-engine name="default" default="true">
                    <datasource>java:/jdbc/Modeling</datasource>
                    <history-level>audit</history-level>
                    <properties>
            <property name="jobExecutorAcquisitionName">default</property>
            <property name="isAutoSchemaUpdate"> false </property>
            <property name="authorizationEnabled"> true  </property>
            <property name="jobExecutorDeploymentAware"> false</property>
            <property name="jobExecutorActivate">false  </property>
            <property name="defaultSerializationFormat"> application/json</property>
            <property name="authorizationCheckRevokes"> never </property>
            <property name="defaultUserPermissionNameForTask"> TASK_WORK </property>
            <property name="dbMetricsReporterActivate">  false  </property>
			</properties>
                </process-engine>
            </process-engines>
            <job-executor>
        <core-threads>200</core-threads>
        <max-threads>700</max-threads>
        <queue-length>200</queue-length>
        <keepalive-time>100</keepalive-time>
        <job-acquisitions>
            <job-acquisition name="default">
                <acquisition-strategy>SEQUENTIAL</acquisition-strategy>
                <properties>
                    <property name="lockTimeInMillis"> 300000 </property>
                    <property name="waitTimeInMillis">  5000 </property>
                    <property name="maxJobsPerAcquisition">  1000 </property>
                </properties>
            </job-acquisition>
        </job-acquisitions>
</job-executor>
        </subsystem>

Followed this link Introduction | docs.camunda.org and updated the db details as per page Patch Level Update | docs.camunda.org. Got complication issues resolved by going the same above page
Any idea how to resolve this issue.

2

HI @pbaddi

Please format your post, so that it’s easier to read :slight_smile:

Also - give more details about the process of upgrading you went through.

3

Thx @Niall , updated my comments inline.

4

Did you go through each minor update one by one?
7.11 → 7.12 → 7.13 etc?

5

Yes i did, 7.11–> 7.12–>7.13–>7.14–>7.15–7.16.

6

Was there a specific version update that made thing stop working?

7

I looks from the the logs you posted that some things components are 7.15 and others are 7.16

8

Wildfly 23 with 7.16.
Server is not coming up.
If any db or any other issues is there, then it should occur during the run time of camunda flow. But here server itself is not coming up.

9

7.16 only I am using

10

It might help to compare it against the wildfly distro that we provide
https://downloads.camunda.cloud/release/camunda-bpm/wildfly/7.16/

Seems like it’s likely to be missing or wrong setting in the wildfly configuration

11

I copy pasted the all the files from above link to my local. Same issue.