| There are 14 comments on this blog. |
|
|
Yup
|
|
|
Same here. Closing some tabs seems to help.
|
|
|
They don't necessarily need to be HX tabs, it could be any tab.
|
|
|
Yes, I got that message a couple of times.
|
|
|
Yep
Just walked away for 30 min and came back and it worked fine
|
|
|
I believe it's from logging in at the same time
|
|
|
From us all logging in at the same time
(Sorry.. voice to text)
|
|
|
So I think we can use this error message as some kind of “horniness index.” Whenever we encounter it, there must be a spike of horny guys & gals all trying to log in.
|
|
|
It happens at 1:30pm PST. Normally it lasts less than eight minutes.
|
|
|
I only get that error earmy in the AM. It usually goes away after an hour.
|
|
|
Happens all the time.
|
|
|
I've encountered this error multiple times throughout my career, working with different companies. The issue arises because software applications typically have a limit on database connections, set by their configuration. In this case, the application has run out of available connections for a new session.
Given that the error is related to connecting to the database, it's likely that the application isn't using connection pooling. Instead, it’s establishing new connections on demand. While this isn’t a critical issue, it can make things a bit slower for users, as each new connection takes time to establish.
Example:
Imagine the database is configured to allow only 100 simultaneous users. As long as those 100 connections are open, if a new user (let's say User 101) tries to log in, they’ll hit the connection limit and see this error.
Common Causes:
Too many active connections: The system hits its connection limit.
Connections not closing automatically: Connections remain open longer than necessary.
Processes holding connections: Some processes might be stuck, preventing connections from being released.
Resolution:
If the software does not not resolve itself, a admin needs to log into, kiss processes, kill sessions, or restart the application.
|
|
|
Pretty sure Scotty is dead on here. I also think Butthead is Akari correct, because I notice this issue in the last week a few times between 1 and 2 PM.
My guess is either more people are logged in at this time, or more likely there is a backup process or something else in the background that requires extra database connections (or temporarily limits the number of available connections). It usually clears up within 5 minutes and you don't have to log back on...just refresh the page.
|
|
|
1:28 pm PST today. 7 minutes later back on.
|
| There are 14 comments on this blog. |
