QA Test engine-cdi and Tomcat 10 deployment manually

[psavidis]

Acceptance Criteria (Required on creation)

The Tomcat 10 manually re-created scenarios of all the failing tests pass successfully.

Hints

• Build the latest Tomcat 10 distro from camunda-bpm-platform:7.22-SNAPSHOT
• Use the Examples / Simple Servlet Process Application as blueprint to deploy a servlet application to $CATALINA_HOME/webapps
  • Replace all the javax dependencies / imports with the jakarta equivalent

Analytical Failing Tests against Tomcat 10 - List

• CallActivityContextSwitchTest
• TestMultipleClasspathRoots
• TestResourceName
• TestWarDeploymentDeployChangedOnlyWithJarAsLib
• TestWarDeploymentWithDiagram
• TestWarDeploymentWithoutDiagram
• TestWarDeploymentWithoutProcessDefinitions
• TestWarDeploymentWithoutProcessesXml
• CdiBeanCallActivityResolutionTest
• CdiBeanCaseTaskResolutionTest
• CallActivityContextSwitchTest
• FailingJobBoundaryTimerWithDelegateVariablesTest
• SignalEventCatchBoundaryWithVariablesTest
• TimerRecalculationTest
• CdiProcessApplicationEventSupportTest

Links

• Support Tomcat 10 #2471

Breakdown

Pull Requests

Beta Give feedback

No tasks being tracked yet.

Dev2QA handover

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

[psavidis]

Testing Notes

• If the ARQ-2234 is fixed prior to the 7.22 release, this ticket can be closed without testing
• If all of the above tests do not pass successfully, we need to update the Documentation to mention the scenarios that do not work.

[psavidis]

Update

✔ The jakartified camunda-quickstart-servlet-pa-1.0-SNAPSHOT.war deployment succeeds and the message Service Task Example ServiceTask is invoked! is displayed in the console after deployment.

[psavidis]

TimerRecalculationTest Manual Test

Context: TimerRecalculationTest

Steps followed

• Unzip the Tomcat 10 distro
• Deploy camunda-quickstart-servlet-pa
• Got the test.war created from the TimerRecalculationTest programmatically (Shrinkwrap)
• Deploy it manually to Tomcat 10 distro
• Start a process instance from the process definition called TimerRecalculationProcess with a variable timerExpression: PT10S using the UI, similar to how the TimerRecalculationTest does.

Expected: The process starts as in the test
Outcome: The process cannot be started and a failure is returned (see screenshot below)

Screenshot

Root-cause: The WeldConstruct class cannot be loaded and java.lang.NoClassDefFoundError: org/jboss/weld/proxy/WeldConstruct. Same as the the error of the test (see respective investigation thread)

[psavidis]

Update Note

Context:The tests were fixed by adding weld-servlet-shaded to the $CATALINA_HOME/lib.

Problem Root cause: Classes of weld-servlet-shaded are not loaded from WEB-INF/lib folder in scenarios that involve multi-archive deployments and weld 5.

Since a solution was found, this task can be closed.