For reproducing the issue the following example can be used:   1) clone the following repository https://github.com/wmedvede/kogito-examples and switch to the branch KOGITO-6640 -postgresql-issue-reproducer   2) the following directory contains the example application. serverless-workflow-qas-service-showcase   3) Please build the directory by using the postgresql maven profile   cd serverless-workflow-qas-service-showcase mvn clean install -Dpostgresql     4) two applications will be generated   query-service query-answer-service     5) Ensure kafka is running locally   6) Ensure a postgresql database is running locally   7) start the query-service application with: java -jar target/quarkus-app/quarkus-run.jar After this step a webapp will be started in http://localhost:8280   8) start the query-answer-service with:  (this application contains the SW) java -jar target/quarkus-app/quarkus-run.jar   to configure the postgresql database see the application.properties file.   9) create a process instance by using the swagger-ui use the POST qaservice method and pass the json bellow as parameter.   11) By querying the postgresql DB we can verify that the process instance was created and property saved in database.   12) Open a browser window in the url http://localhost:8280 and answer the formulated query by using the webapp   11) When the send button is pressed a Kafka event is produced and sent to the SW. At this point the SW receives the event and the reported exception is produced. See the Jira description. And we can verify that the process was not completed.       NOTE: If we build the project by NOT using the postgresql profile (process instances stored in memory) and reproduce all the steps, we can see that the SW works fine. In the console we can see the logs and that the process has finished, etc.