Bug #730

tmqueue / forward transaction/XATMI call timeout

Added by Lauris about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:09/18/2021
Priority:Normal (Code 4)Due date:
Assignee:-% Done:

100%

Category:-
Target version:-

Description

Current for automatic queues, forward process for service calls uses default NDRX_TOUT setting, thought services might use txtout or default transaction timeout value which might be greater than XATMI ipc timeout. Thus forwarder thread would time-out and rollback the transaction, even the destination service is still doing normal processing.

History

#1 Updated by Lauris about 2 years ago

Release notes

Updated tmqueue forward thread processing so that:

  • If autoq=y is used and destination service will do auto-transaction, the XATMI service call to destination service would use the same transaction timeout value for tpcall() timeout. For local transaction completion (counter updates/delete/error enqueue, etc.) transaction/xatmi timeout is used as: txtout setting from q def, or -t setting from tmqueue.
  • If autoq=T is used or autoq=y and destination service will not do auto-transaction, transaction/xatmi timeout is used during the processing is txtout setting from q def, or -t setting from tmqueue.

Available from Enduro/X version 7.5.34+.

#2 Updated by Lauris about 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#3 Updated by Lauris about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF