Skip to content

Deadlock when creating HistoryEvents from many connections simultaneously #2374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ryzheboka opened this issue Sep 7, 2023 · 0 comments
Closed

Deadlock when creating HistoryEvents from many connections simultaneously #2374

ryzheboka opened this issue Sep 7, 2023 · 0 comments
Labels
bug
Milestone
v.8.2.0

Comments

@ryzheboka
Copy link
Contributor

Example:

  • The connection pool has 10 connections
  • The method createTask is called 10 times simultaneously
  • 10 connections are occupied
  • First Task is added to the database
  • A history event needs to be written before the transaction can end
  • The history event waits for a free connection
  • No connection can be freed because no history events can be written
    ==> Deadlock
@ryzheboka ryzheboka added the bug label Sep 7, 2023
@ryzheboka ryzheboka moved this from Todo to Integrated in TASKANA Kanban Board Sep 29, 2023
@gitgoodjhe gitgoodjhe moved this from Integrated to In Progress in TASKANA Kanban Board Sep 29, 2023
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Oct 24, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
116daee 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Oct 24, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
d8c7374 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Oct 24, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
106bef2 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Oct 25, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
a92a988 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Nov 2, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
7dd865d 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Nov 2, 2023
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
52e2007 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
-Read operations are still performed by the TaskanaHistoryEngine
@ryzheboka ryzheboka moved this from In Progress to Review in TASKANA Kanban Board Jan 30, 2024
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Jul 30, 2024
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
a20d09f 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Jul 30, 2024
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
f96f420 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
gitgoodjhe pushed a commit to gitgoodjhe/taskana that referenced this issue Jul 30, 2024
Closes Taskana#2374: Deadlock when creating HistoryEvents from many c…
34c060e 
…onnections simultaneously

-Write operations are now performed with the regular TaskanEngine and its' SqlSession and TransactionFactory which provides the needed transactionality and doesn't open multiple connections
@gitgoodjhe gitgoodjhe added this to the v.8.2.0 milestone Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
TASKANA Kanban Board
Status: Released
Milestone
v.8.2.0
Development

No branches or pull requests
2 participants
@ryzheboka @gitgoodjhe