Support for JBoss EAP 8 #4142

tasso94 · 2024-03-01T15:49:27Z

User Story (Required on creation)

As an operations engineer, I can run a shared Camunda engine and its webapps on JBoss EAP 8.

Functional Requirements (Required before implementation)

JBoss EAP 8 is a supported environment.

Technical Requirements (Required before implementation)

The Camunda WildFly subsystem is compatible with JBoss EAP 8. Revert incompatible API in WildFly subsystem (CE)
Covered by engine and webapps integration testing
- add CI stages
- add integration-tests-engine-jakarta module
- add jbosseap8 maven profiles
Documentation is updated
Optional: Update deprecated javax module descriptor usages in qa modules

Limitations of Scope

Hints

https://developers.redhat.com/articles/2024/02/05/whats-new-jboss-enterprise-application-platform-8
~~Todo~~: create an infra ticket to add vanilla JBoss EAP 8 ZIP to Artifactory (similarly to JBoss EAP 7.4). - done, see below

Links

https://github.com/camunda/team-infrastructure/issues/585

Breakdown

Pull Requests

Give feedback

https://github.com/camunda/camunda-bpm-platform-ee/pull/939/
chore(wildfly): revert deprecated API usage to add support for jbosseap 8 #4392

ci:jbosseap ci:skipTests ci:webapp-integration ci:wildfly
https://github.com/camunda/camunda-bpm-platform-ee/pull/948
feat(installation): add JBoss EAP 8 support camunda-docs-manual#1645
Update deprecated javax module descriptor usages in qa modules #4424

2 of 2

type:subtask version:7.22.0 version:7.22.0-alpha3
feat(update): mention JBoss EAP 8 in the migration guide camunda-docs-manual#1654
Options

Dev2QA handover

Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

The text was updated successfully, but these errors were encountered:

yanavasileva · 2024-03-12T12:18:05Z

Requested upload to Artifactory from Infra: https://camunda.slack.com/archives/C5AHF1D8T/p1710245806426399

Edit: Distro is available now, check Intra ticket. In case of issue open a new slack thread in #ask-infra.

yanavasileva · 2024-05-28T13:22:37Z

yanavasileva · 2024-05-29T08:18:16Z

TODO:

security is incorrect here: https://docs.camunda.org/manual/7.21/installation/full/jboss/manual/#create-a-datasource. Should be <security user-name="sa" password="sa"/>
javax.* descriptor usages in qa modules related to Update deprecated javax module descriptor usages #3588
2024-05-30 20:18:20,162 WARN [org.jboss.as.connector] (MSC service thread 1-5) {} WFLYJCA0091: -ds.xml file deployments are deprecated. Support may be removed in a future version. - occurs in the previous versions too. We use it to easily switch between databases, h2 and postgresql.
* Alternatives? I didn't find alternatives but found that these deployments are only for development purposes so we have been using the feature correctly. Source: https://developer.jboss.org/message/949441#949441
Do we want to test JBoss EAP 8 in domain and servlet mode? It's currently tested only for WildFly 27+. What do we gain if we add such stages? Do we claim support for it in docs?

Details

Disclaimer: I don't see different between servlet and default WildFly profiles.

Docs
- https://docs.camunda.org/manual/7.21/user-guide/process-applications/the-process-application-class/

Should we use transformation for qa/integration-tests-engine-jakarta/pom.xml?

yanavasileva · 2024-05-29T11:12:58Z

WildFly 31 uses wildfly-core version 23.
JBossEAP 8 uses redhat version of wildfly-core version 21.

#getServiceTarget() deprecation and the new services adjustments are introduced in wildfly-core version 22. (https://issues.redhat.com/browse/WFCORE-6397, https://issues.redhat.com/browse/WFCORE-6400)
=> revert made changes for adoption of the new API.

Example exceptions

11:56:38,544 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 75) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "camunda-bpm-platform"),
    ("process-engines" => "default")
]): java.lang.NoSuchMethodError: org.jboss.as.controller.CapabilityServiceTarget.addService(Lorg/jboss/msc/service/ServiceName;)Lorg/jboss/as/controller/CapabilityServiceBuilder;
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.22.0-SNAPSHOT//org.camunda.bpm.container.impl.jboss.extension.handler.ProcessEngineAdd.installService(ProcessEngineAdd.java:66)
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.22.0-SNAPSHOT//org.camunda.bpm.container.impl.jboss.extension.handler.ProcessEngineAdd.performRuntime(ProcessEngineAdd.java:58)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:284)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:105)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1057)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:778)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:469)
        at org.jboss.as.controller@21.0.5.Final-redhat-00001//org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
        at java.base/java.lang.Thread.run(Thread.java:834)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.JBossThread.run(JBossThread.java:513)
...
12:04:52,778 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war"
        at org.jboss.as.server@21.0.5.Final-redhat-00001//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
        at org.jboss.msc@1.5.1.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
        at org.jboss.msc@1.5.1.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
        at org.jboss.msc@1.5.1.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.NoSuchMethodError: org.jboss.as.server.deployment.DeploymentPhaseContext.getRequirementServiceTarget()Lorg/jboss/as/controller/RequirementServiceTarget;
        at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.22.0-SNAPSHOT//org.camunda.bpm.container.impl.jboss.deployment.processor.ProcessApplicationDeploymentProcessor.deploy(ProcessApplicationDeploymentProcessor.java:142)
        at org.jboss.as.server@21.0.5.Final-redhat-00001//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
        ... 8 more
...
12:04:56,832 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"camunda-example-invoice-jakarta-7.22.0-20240527.164435-21.war\"
    Caused by: java.lang.NoSuchMethodError: org.jboss.as.server.deployment.DeploymentPhaseContext.getRequirementServiceTarget()Lorg/jboss/as/controller/RequirementServiceTarget;"}}

yanavasileva · 2024-06-03T07:31:51Z

Current progress 2024-05-31

Server can't start

engine-IT and webapps-IT can't run as server doesn't find the right java:jboss/datasources/ProcessEngine datasource. During standalone.xml parsing, the process engine information is undefined so the default ExampleDS datasource is used instead.

Example exceptions

&amp#27;[0m&amp#27;[31m16:41:12,282 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) {} WFLYCTL0013: Operation ("internal-model-validation") failed - address: ([]) - failure description: "WFLYCTL0172: core-threads is required"
&amp#27;[0m&amp#27;[31m16:41:12,286 FATAL [org.jboss.as.server] (Controller Boot Thread) {} WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone.xml
&amp#27;[0m&amp#27;[0m16:41:12,298 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) {} WFLYJCA0010: Unbound data source [java:jboss/datasources/ProcessEngine]
&amp#27;[0m&amp#27;[31m16:41:12,403 ERROR [org.camunda.bpm.engine.context] (pool-9-thread-1) {} ENGINE-16004 Exception while closing command context: An exception occurred in the persistence layer. Please check the server logs for a detailed message and the entire exception stack trace.: org.camunda.bpm.engine.ProcessEnginePersistenceException: An exception occurred in the persistence layer. Please check the server logs for a detailed message and the entire exception stack trace.
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.util.ExceptionUtil.wrapPersistenceException(ExceptionUtil.java:379)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.util.ExceptionUtil.doWithExceptionWrapper(ExceptionUtil.java:374)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.sql.DbSqlSession.executeSelectList(DbSqlSession.java:112)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.sql.DbSqlSession.selectList(DbSqlSession.java:104)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.selectListWithRawParameter(DbEntityManager.java:180)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.selectList(DbEntityManager.java:172)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.selectList(DbEntityManager.java:168)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.selectList(DbEntityManager.java:157)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.persistence.entity.JobManager.findNextJobsToExecute(JobManager.java:245)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.cmd.AcquireJobsCmd.execute(AcquireJobsCmd.java:65)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.cmd.AcquireJobsCmd.execute(AcquireJobsCmd.java:43)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:28)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:111)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.AbstractTransactionInterceptor.execute(AbstractTransactionInterceptor.java:54)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:70)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.CommandCounterInterceptor.execute(CommandCounterInterceptor.java:34)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.interceptor.ExceptionCodeInterceptor.execute(ExceptionCodeInterceptor.java:55)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable.acquireJobs(SequentialJobAcquisitionRunnable.java:164)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable.run(SequentialJobAcquisitionRunnable.java:80)
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
	at java.base/java.lang.Thread.run(Thread.java:834)
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: org.apache.ibatis.exceptions.PersistenceException: 
### Error querying database.  Cause: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-214]
### The error may exist in org/camunda/bpm/engine/impl/mapping/entity/Job.xml
### The error may involve org.camunda.bpm.engine.impl.persistence.entity.JobEntity.selectNextJobsToExecute
### The error occurred while executing a query
### SQL: select RES.ID_,       RES.REV_,       RES.DUEDATE_,             RES.PROCESS_INSTANCE_ID_,       RES.EXCLUSIVE_          from ACT_RU_JOB RES      where (RES.RETRIES_ > 0)       and (                   RES.DUEDATE_ is null or                   RES.DUEDATE_ <= ?       )       and (RES.LOCK_OWNER_ is null or RES.LOCK_EXP_TIME_ < ?)       and RES.SUSPENSION_STATE_ = 1                                  and (      (      RES.EXCLUSIVE_ = true           and not exists(             select J2.ID_             from ACT_RU_JOB J2                              where J2.PROCESS_INSTANCE_ID_ = RES.PROCESS_INSTANCE_ID_                                         and (J2.EXCLUSIVE_ = true)                                                                               -- also exclusive             and (J2.LOCK_OWNER_ is not null and J2.LOCK_EXP_TIME_ >= ?)                   -- in progress             )    )     or           RES.EXCLUSIVE_ = false        )                     LIMIT ? OFFSET ?
### Cause: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-214]
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:156)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:147)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:142)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.db.sql.DbSqlSession.lambda$executeSelectList$1(DbSqlSession.java:112)
	at org.camunda.bpm.camunda-engine@7.22.0-SNAPSHOT//org.camunda.bpm.engine.impl.util.ExceptionUtil.doWithExceptionWrapper(ExceptionUtil.java:372)
	... 24 more
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-214]
	at com.h2database.h2@2.1.214//org.h2.message.DbException.getJdbcSQLException(DbException.java:678)
	at com.h2database.h2@2.1.214//org.h2.message.DbException.getJdbcSQLException(DbException.java:477)
	at com.h2database.h2@2.1.214//org.h2.message.DbException.get(DbException.java:223)
	at com.h2database.h2@2.1.214//org.h2.message.DbException.get(DbException.java:199)
	at com.h2database.h2@2.1.214//org.h2.message.DbException.get(DbException.java:188)
	at com.h2database.h2@2.1.214//org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1375)
	at com.h2database.h2@2.1.214//org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:637)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:790)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:776)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.WrappedConnection$4.produce(WrappedConnection.java:478)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.WrappedConnection$4.produce(WrappedConnection.java:476)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.SecurityActions.executeInTccl(SecurityActions.java:103)
	at org.jboss.ironjacamar.jdbcadapters@3.0.2.Final-redhat-00002//org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:476)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.statement.PreparedStatementHandler.instantiateStatement(PreparedStatementHandler.java:88)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.statement.BaseStatementHandler.prepare(BaseStatementHandler.java:90)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.statement.RoutingStatementHandler.prepare(RoutingStatementHandler.java:60)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.BatchExecutor.doQuery(BatchExecutor.java:92)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:336)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:158)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:110)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:90)
	at org.mybatis.mybatis@3.5.15//org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:154)
	... 28 more
&amp#27;[0m&amp#27;[0m16:41:12,410 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) {} WFLYJCA0019: Stopped Driver service with driver-name = postgresql

Root cause

wildfly-core 21 still relies on specifying via AttributeDefinition arguments in constructor. The latter was deleted in the WildFly 31 Camunda subsystem cleanup. After returing the mentioned constructor (0b3c23b) the issue is resolved.

yanavasileva · 2024-06-07T11:54:17Z

Current progress 2024-06-07

engine-IT and webapps-IT green for new version and the existing ones
Next:
- check open questions
- regression testing
- prepare and schedule Kickoff

yanavasileva · 2024-06-10T07:13:51Z

Kickoff

JBoss EAP 8

Supports JDK 11/17, Java 11 will be removed in next versions
Implementation details - JBoss EAP 8 is based on WildFly 28.
- Notable changes: adoption of Jakarta.
- Therefore we can use WildFly subsystem 27+ (31 at the moment). Only minimal change will be required due to new API not present in JBoss (check Support for JBoss EAP 8 #4142 (comment) and Support for JBoss EAP 8 #4142 (comment) root causing).
- No need of adding JBoss distribution as this is enterprise server.

Server	WildFly-core
WildFly 31	`wildfly-subsystem-23`
JBoss EAP 8	based on `wildfly-subsystem-21`

Proposal

Use Camunda WildFly subsystem 31
- Revert API that is not part of wildfly-core-21 - #getServiceTarget() and constructor AttributeDefinition
- pros - minimal maintenance efforts, when we adopt higher JBoss version that uses more recent WildFly core version, we can drop the usage of deprecated API.
Add integration tests coverage for the application server
- Introduce qa-integration-tests-ee-jakarta module
  - transformation
    - pros - no duplication and consistency with qa modules in platform repository (community)
  - alternative: no transformation
    - pros - easier to drop non-jakarta module afterwards as there won't be a dependency to it
- don't add domain mode test coverage. The mode is tested with WildFly 27+ and we don't expect difference between the servers. Failures with the mode have been reported to it only related to test infrastructure (Arquillian) and bug in WildFly.
  - pros - less code, less maintenance efforts. We can add it later if there's any need.
- don't add servlet profile as it seems the same as the default profile. I don't see benefit for it as of today.
- (Optional) remove javax.* descriptor usages in qa modules
Adjust docs
Regression testing of a manual installation of the server.

Expected S-size effort (2 weeks)

Decisions:

Proposal accepted.
- We won't introduce domain or servlet profiles for testing.

Breakdown

Revert incompatible API in WildFly subsystem (CE)
Add test coverage (EE)
- add CI stages
- add qa-integration-tests-ee-jakarta module using transformation
- add jbosseap8 maven profiles
Update docs
Optional: remove javax.* descriptor usages in qa modules - Update deprecated javax module descriptor usages in qa modules #4424

yanavasileva · 2024-06-13T08:48:05Z

Re qa-integration-tests-ee-jakarta module

the files needed for JBossEAP are TestConstants.java, TestContainer.java, and arquillian.xml
there is already unpack operation for the qa-integration-tests-jakarta that brings the rest of the resources
=>
Decision: code length wise and complexity, it will be better to have another unpack operation (for transformation) and just add the needed files to the new module

…EAP 8 (#4392) * revert getServiceTarget changes * revert deprecated AbstractAddStepHandler constructor with attributes #4142

yanavasileva · 2024-06-18T11:18:01Z

Dev2QA handover

Perform standard regression test of a server application with a manual installation: JBoss EAP 8.0
You can pair it with database: Oracle 19

Download

Link can be found here.

Documentation

Manual installation: https://docs.camunda.org/manual/develop/installation/full/jboss/manual/ (look for WildFly ≥27 / JBoss EAP 8).

gbetances089 · 2024-06-25T11:35:36Z

Tested on
application-server": { "vendor": "JBoss EAP", "version": "JBoss EAP 8.0.0.GA (WildFly Core 21.0.5.Final-redhat-00001) - 2.3.10.SP3-redhat-00001" },

with oracle19 as db and the webapps/API worked as expected.

camunda/camunda-bpm-platform#4142

tasso94 added type:feature Issues that add a new user feature to the project. potential:7.21.0 labels Mar 1, 2024

yanavasileva self-assigned this Mar 12, 2024

engineering-issue-sync-app bot mentioned this issue Mar 12, 2024

Support for JBoss EAP 8 camunda/issues#582

Closed

tasso94 unassigned yanavasileva Mar 12, 2024

tasso94 added version:7.22.0 and removed potential:7.21.0 labels Mar 22, 2024

yanavasileva self-assigned this May 27, 2024

yanavasileva mentioned this issue Jun 7, 2024

feat(installation): add JBoss EAP 8 support camunda/camunda-docs-manual#1645

Merged

yanavasileva assigned joaquinfelici and unassigned yanavasileva Jun 13, 2024

joaquinfelici assigned yanavasileva and unassigned joaquinfelici Jun 17, 2024

yanavasileva added a commit that referenced this issue Jun 18, 2024

chore(wildfly): revert deprecated API usage to add support for JCoss …

daa8141

…EAP 8 (#4392) * revert getServiceTarget changes * revert deprecated AbstractAddStepHandler constructor with attributes #4142

yanavasileva assigned gbetances089 and unassigned yanavasileva Jun 18, 2024

gbetances089 closed this as completed Jun 25, 2024

yanavasileva added a commit to camunda/camunda-docs-manual that referenced this issue Jun 27, 2024

feat(update): mention JBoss EAP 8 in the migration guide

64a7996

camunda/camunda-bpm-platform#4142

yanavasileva mentioned this issue Jun 27, 2024

feat(update): mention JBoss EAP 8 in the migration guide camunda/camunda-docs-manual#1654

Merged

yanavasileva reopened this Jun 27, 2024

yanavasileva assigned joaquinfelici and unassigned gbetances089 Jun 27, 2024

joaquinfelici assigned yanavasileva and unassigned joaquinfelici Jun 28, 2024

yanavasileva added a commit to camunda/camunda-docs-manual that referenced this issue Jun 28, 2024

feat(update): mention JBoss EAP 8 in the migration guide (#1654)

a0260de

camunda/camunda-bpm-platform#4142

yanavasileva closed this as completed Jun 28, 2024

danielkelemen added the version:7.22.0-alpha3 label Jun 28, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support for JBoss EAP 8 #4142

Support for JBoss EAP 8 #4142

tasso94 commented Mar 1, 2024 •

edited by yanavasileva

Loading

Pull Requests

yanavasileva commented Mar 12, 2024 •

edited

Loading

yanavasileva commented May 28, 2024

yanavasileva commented May 29, 2024 •

edited

Loading

yanavasileva commented May 29, 2024

yanavasileva commented Jun 3, 2024 •

edited

Loading

yanavasileva commented Jun 7, 2024

yanavasileva commented Jun 10, 2024 •

edited

Loading

JBoss EAP 8

yanavasileva commented Jun 13, 2024 •

edited

Loading

yanavasileva commented Jun 18, 2024 •

edited

Loading

gbetances089 commented Jun 25, 2024

Support for JBoss EAP 8 #4142

Support for JBoss EAP 8 #4142

Comments

tasso94 commented Mar 1, 2024 • edited by yanavasileva Loading

User Story (Required on creation)

Functional Requirements (Required before implementation)

Technical Requirements (Required before implementation)

Limitations of Scope

Hints

Links

Breakdown

Pull Requests

Dev2QA handover

yanavasileva commented Mar 12, 2024 • edited Loading

yanavasileva commented May 28, 2024

yanavasileva commented May 29, 2024 • edited Loading

yanavasileva commented May 29, 2024

yanavasileva commented Jun 3, 2024 • edited Loading

Current progress 2024-05-31

Server can't start

Root cause

yanavasileva commented Jun 7, 2024

Current progress 2024-06-07

yanavasileva commented Jun 10, 2024 • edited Loading

Kickoff

JBoss EAP 8

Proposal

Decisions:

Breakdown

yanavasileva commented Jun 13, 2024 • edited Loading

yanavasileva commented Jun 18, 2024 • edited Loading

Dev2QA handover

Download

Documentation

gbetances089 commented Jun 25, 2024

tasso94 commented Mar 1, 2024 •

edited by yanavasileva

Loading

yanavasileva commented Mar 12, 2024 •

edited

Loading

yanavasileva commented May 29, 2024 •

edited

Loading

yanavasileva commented Jun 3, 2024 •

edited

Loading

yanavasileva commented Jun 10, 2024 •

edited

Loading

yanavasileva commented Jun 13, 2024 •

edited

Loading

yanavasileva commented Jun 18, 2024 •

edited

Loading