[GH-ISSUE #61] Intermittent SQLITE_BUSY or Lock Contention when Multiple Sessions are Active (High Load) #43

New issue

Closed

opened 2026-02-27 10:25:35 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 10:25:35 +03:00

Owner

Originally created by @davidgoweb on GitHub (Nov 24, 2025).
Original GitHub issue: https://github.com/mimamch/wa-multi-session/issues/61

1. The Problem

As wa-multi-session scales up to manage many active sessions, the database is highly likely to encounter write contention (multiple sessions trying to save data simultaneously). This results in crippling SQLITE_BUSY errors, causing data loss and session instability.

The problem comes from frequent writes for logging messages and updating session status, not the infrequent creation/deletion of sessions.

2. The Solution: Critical Configurations

We need to proactively enforce the best practices for SQLite concurrency:

Use WAL (Write-Ahead Logging) Mode

Action: Set PRAGMA journal_mode = WAL; on the database connection.
Why: WAL allows unlimited readers to access the database while a single writer is active. This eliminates stalls and dramatically increases concurrency compared to the default journaling mode.

Originally created by @davidgoweb on GitHub (Nov 24, 2025). Original GitHub issue: https://github.com/mimamch/wa-multi-session/issues/61 ### 1. The Problem As `wa-multi-session` scales up to manage many active sessions, the database is highly likely to encounter **write contention** (multiple sessions trying to save data simultaneously). This results in crippling **`SQLITE_BUSY`** errors, causing data loss and session instability. The problem comes from frequent writes for logging messages and updating session status, not the infrequent creation/deletion of sessions. --- ### 2. The Solution: Critical Configurations We need to proactively enforce the best practices for SQLite concurrency: #### Use WAL (Write-Ahead Logging) Mode * **Action:** Set `PRAGMA journal_mode = WAL;` on the database connection. * **Why:** **WAL** allows unlimited **readers** to access the database while a single **writer** is active. This eliminates stalls and dramatically increases concurrency compared to the default journaling mode.

kerem closed this issue

2026-02-27 10:25:35 +03:00

kerem commented

2026-02-27 10:25:36 +03:00

Author

Owner

@mimamch commented on GitHub (Nov 24, 2025):

Hi @davidgoweb, thank you so much for your very helpful feedback. I will looking further about what you said above soon and write the update on this issue. 🔥

@mimamch commented on GitHub (Nov 24, 2025): Hi @davidgoweb, thank you so much for your very helpful feedback. I will looking further about what you said above soon and write the update on this issue. 🔥

kerem commented

2026-02-27 10:25:36 +03:00

Author

Owner

@mimamch commented on GitHub (Nov 25, 2025):

Thank you @davidgoweb, fixed on #62

@mimamch commented on GitHub (Nov 25, 2025): Thank you @davidgoweb, fixed on #62

kerem referenced this issue

2026-02-27 10:25:42 +03:00

[PR #43] [CLOSED] add whatsapp number check before sending a message #56