General query on transaction management.
Environment
Red Hat JBoss BPM Suite
6.2.0
Issue
What problem/issue/behavior are you having trouble with? What do you expect to see?
We have an application team that used jbpm 5.3.1 in the embedded mode. Now they will be migrating to 6.2. They wanted to let you know the best practices that could be followed on transaction management between application database and jbpm database.
Say there is a process that is to be started. Before and after the process has been successfully started they have to update multiple number of tables.
If there is any issue in updating application database tables or creating process instances they want a complete rollback of db tables including created process instances to be rolled back.
Is there any cleaner way to achieve it. They are looking for best practices from you on how this could be achieved.
If there is any sample on cleaner transaction management, it would be helpful. Also another criterial here is there are thoussands of processes that get created and the load is much higher. So the solution should also not be affecting their performance in any way.
Where are you experiencing the behavior? What environment?
Development
When does the behavior occur? Frequently? Repeatedly? At certain times?
At certain times
What information can you provide around timeframes and urgency?
NA
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
