Alex Kogan · Apr 26, 2021

TSTART Connection lost and transaction does not rollback


I have a quick question regarding TSTART, however not certain if there is an answer.

If I am inside the transaction and I loose connection - I always assumed that transaction would TROLLBACK, however it does not.

Is there anything special I need to set up with my TSTART, in order for this transaction to safely rollback?


As example: Let's say I am inside the TSTART and setting up / altering some data and my VPN connection got disconnected.  I kind of expect all the data to be rolled back.  

Thank you,



Product version: IRIS 2020.1
2 0 6 130
Log in or sign up to continue

It’s connected with a process, until it’s alive, transaction will be open. When process will be finished by any reasons, it should rollback any transactions left open.

I thought so too, but it clearly does not work. Maybe it's a bug in TROLLBACK.

my exact steps to reproduce:

1.Open up terminal session. 


3. Set any simple global to test: S ^AKTEST=123

4. Disconnect VPN

5. Reconnect VPN

6. Open up new Terminal Session

7. Look up that global - It is still there with my setting.

Hello Alex,

Have you confirmed that the original transaction process goes away when the VPN disconnects? How are you opening the terminal in the first place?

If disconnecting the VPN leaves the original process around, it won't have a chance to rollback the transaction.

edit: perhaps this is related to your Journal Freeze on error setting?

Are you sure, that the process was terminated?

You should check cconsole.log/messages.log

journal records, you should find there where transaction was started, you changed the data, check if change was really in transaction and any other records within the process, it should be commit or rollback. 
In any case, when restart Cache, it should terminate any unfinished processes and rollback data.

Thank you yes, I thought the process is done, once I disconnect the VPN and terminal says Inactive, but I figured out that if I reconnect my VPN, go to studio - the process is still there, so once I terminate it - TROLLBACK works fine.

Thank you

The O.S. process associated with the terminal was still running, in READ state, unaware that the terminal had disconnected.  Once we found it and terminated it (we used the System Management Portal for that), the transaction was properly rolled back.