Project

General

Profile

Feature #100

refactor write back

Added by Josip Almasi over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Josip Almasi
Start date:
01/19/2022
Due date:
% Done:

0%

Estimated time:

Description

Current implementation of WriteBack starts own thread. But other database access comes from websocket session context, whatever thread tomcat and/or spring starts.
Database sessions are not thread-safe, and that causes deadlocks every now and then.
So write back needs to be executed in session context. ThreadLocal?

History

#1

Updated by Josip Almasi over 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Josip Almasi

ThreadLocal alright.
Pushed, deployed, we'll see.

#2

Updated by Josip Almasi over 2 years ago

ThreadLocal causes deleted objects to reappear :)
Refactored one writeback per client - this ensures right context regardless of thread pool.

#3

Updated by Josip Almasi about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF