Skript-db creating too many SQL connections #19
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Limework/skript-db#19
Loading…
Reference in New Issue
Block a user
No description provided.
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?
One user reported that skript-db created 150 connections in 5 minutes that stay without closing. There may be a leak?
In addition to that, we should add configuration option for max connections at any given time.
yea same for me.
i got a lot of connections, so that my website doesn't work anymore..
maybe it's because i open multiple databases at a time
Could you share more details on your setup? I cannot reproduce this issue on my own network, so I need your sql server configuration, your queries and how often they are done.
Usually increasing max connections limit in your sql server configuration should help.
Also make sure you have not saved sql connections into persistent variables (those would end up starting on server startup)
which variables should I use then? How should they look?
{_sql} wouldn't work in other skripts right?
{-variables}
you can enable them with (?!-).* variable pattern in config.SK database settings
doesn't change anything..
there are just a lot of sleep connections. If you kill them, the plugin sends warnings that is has to recreate them
how much is a lot?
always the max connections limit
i think the connections get saved somewhere else and then always reconnected or they just don't get right closed.
variables.CSV file would be the only somewhere else place it may save to
I finally took time to debug this issue and found the cause to be that I removed thread-pool-size config option many updates ago, I have now re-added it in skript-db 1.3.9 and it should be fixed. (Release soon)