Bug #822

tmqueue restart with empty prepared transactions, causes tmqueue failure to boot

Added by Lauris 4 months ago. Updated 4 months ago.

Status:ClosedStart date:01/19/2024
Priority:Normal (Code 4)Due date:
Assignee:-% Done:

100%

Category:-
Target version:-

Description

1) If empty transactions (with static XA driver) have happened on tmqueue Q space, and Q space was just restarted after it was prepared (the first phase of 2pc was executed), the tmqueue fails to parse such transactions state and process fails to boot.

2) If non Q space-related messages were found in data directory, the file descriptors might leak for such files.

History

#1 Updated by Lauris 4 months ago

  • Description updated (diff)

#2 Updated by Lauris 4 months ago

Release notes

Fixed the tmqueue process, so that dummy-prepared transactions can be resumed after the restart.

Fixed memory leak, in case during the startup, the transaction file was found from a different tmqueue instance. However, normally such a memory leak does not occur, as the recommendation is an individual queue space directory on disk for each of the tmqueue instances.

Available from Enduro/X release 8.0.12+.

#3 Updated by Lauris 4 months ago

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

#4 Updated by Lauris 4 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF