langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #21726] Release db.session connection before workflow new thread long time operation #29732

New Issue
Closed
opened 2026-02-21 20:46:08 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:46:08 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/21726

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fixes #21176

In workflow/app_generator.py, although db.session.close() is called within _generate_worker.WorkflowAppRunner.run, the method call of self._generate_worker occurs in a new thread, causing the database connection to remain invalidly occupied before the call to self._generate_worker. Therefore, db.session.close() is also called once before starting the new thread to release the connection.

Screenshots

Before
150 concurret requests result. (A simple workflow with a node that executes time.sleep(5) code.)
image

After
150 concurret requests result. not perfect, but solve some problems
image

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/21726 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 2. Ensure there is an associated issue and you have been assigned to it > 3. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary Fixes #21176 In `workflow/app_generator.py`, although `db.session.close()` is called within `_generate_worker.WorkflowAppRunner.run`, the method call of `self._generate_worker` occurs in a new thread, causing the database connection to remain invalidly occupied before the call to `self._generate_worker`. Therefore, `db.session.close()` is also called once before starting the new thread to release the connection. ## Screenshots Before 150 concurret requests result. (A simple workflow with a node that executes time.sleep(5) code.) ![image](https://github.com/user-attachments/assets/d94c009f-edb4-4527-bb4e-5afb59ec27eb) After 150 concurret requests result. not perfect, but solve some problems ![image](https://github.com/user-attachments/assets/f365a931-9491-49a5-ae5c-b79307e21783) ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:46:08 -05:00
yindo closed this issue 2026-02-21 20:46:08 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#29732
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?