Reason for startTransaction service putting outside of SEQUENCE step in flow service ??

, ,
1

Hi,

Recently I was going through the documentation of Jdbc adapter(6.5), I have found that SAG doesn’t recommend putting ‘pub.art.transaction:startTransaction’ in SEQUENCE step. I am unable to find out the reason behind it.

Can you anyone know about the exact reason?

Thanks in advance !!

Regards,
Tanveer

2

The reason for it should be outside of the sequence step is the transactionName can be always there in the pipeline even in the case of catch block errors scenario and the rollback situation does get work as expected making the transactionName available if any hard errors.

HTH,
RMG

3

Hi,

Calling StartTransaction simply means u r using LocalTransaction as a Transaction Type and for this we have to put in a transaction Boundary.
Say inside main U cant call because control will come out after getting first success, yes you can call inside try block but this is not our best practice.

so best to use the first step inside a flow service.

Thanks,
Vicky

4

Another valid point brought up…thanks Vicky for Chime in:

5

Hi,

Thank you all !! This is what I was looking for ! The Actual Reason !!

Regards,
Tanveer

6

Glad you got the info that you are looking for:)