Re: Digest for kogito-development@googlegroups.com - 1 update in 1 topic

[Enrique Gonzalez Martinez]

Yeah. Set to false the parameter and you will get the old behaviour during codegen.

This parameter is intend to keep the consistency of the process state. That is the reason of this behaviour. Before persistence it was ok not no have it but due to the sheer number of ways to modify the process state during activity execution we decided to go back to the jbpm v8 way.

Saludos, Enrique González Martínez :)

El sáb, 19 jul 2025, 9:40, <kogito-de...@googlegroups.com> escribió:

kogito-de...@googlegroups.com

Google Groups

Topic digest
View all topics

• Kogito 10.1.0 - Transactions enabled for BPMN applications - 1 Update

Kogito 10.1.0 - Transactions enabled for BPMN applications

Ioanna Bekiari <jbek...@gmail.com>: Jul 18 02:55AM -0700 Hello,   After the kogito 10.1.0 release announcement, we started to migrate our applications from kogito 10.0.0 - compact architecture to kogito 10.1.0 and quarkus 3.8.4 to 3.15.3.1.   During the tests we found that the implementation of the exception handling is different in kogito 10.1.0.   A new metadata parameter:   *jbpm.transactions.enable*   has been introduced in 10.1.0, that is always true for the BPMN applications and changes the exception handling.   We cannot modify the “jbpm.transactions.enable” parameter because it is generated during codegen.   When this param is set, any node error throws a ProcessInstanceExecutionException and the process is not written in the database.   Could you explain us what is the use of this parameter and how can we handle the related functionality?   Is there a way to modify its value to “false” without changing the “BPMN” application type ?   Thanks,BR,   Ioanna

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to kogito-developm...@googlegroups.com.

[Ioanna Bekiari]

Hello,

thanks for the description you sent.

Our problem is that we cannot set the "jbpm.transactions.enable" to false.

We added it as a metadata attribute with value "false" of our processes but still during codegen the java code is produced with

jbpm.transactions.enable=true.

How can we modify it??

BR,

Ioanna

--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kogito-development/CAFDLxqfwap94fHkyKndVNGAHKAphNsxm_JHNbkftFChHroR67Q%40mail.gmail.com.

[Jaime Izuzquiza]

Hello Ioanna,

try with kogito.transactionEnabled=false in application.properties.

Best regards,

Jaime

[Jaime Izuzquiza]

Hi Ioanna,

try with kogito.transactionEnabled=false in application.properties.

Best regards,

Jaime

El lunes, 21 de julio de 2025 a las 8:08:33 UTC+2, Ioanna Bekiari escribió:

[Ioanna Bekiari]

Hello Jaime,

i tried with the parameter you suggested in application.properties and it is ok now.

Thanks for the support.

BR,

Ioanna

To view this discussion visit https://groups.google.com/d/msgid/kogito-development/fadb92e5-c8af-49d0-9db2-973c5f64bdbcn%40googlegroups.com.