Defect #31363
closed500 Internal Server Error
0%
Description
The number of users is about 40. So the [ActionMailer::DeliveryJob] will send lots of mails when a user commit an issuse.
The web will display "500 Internal Server Error",but the committing action is taking effect.
Files
Related issues
Updated by haobin li over 5 years ago
From version 4.0.0 to v4.0.3,the issue always exist.
Updated by bill auger over 5 years ago
this look like the same issue i reported a few weeks ago
Updated by haobin li over 5 years ago
- File production 3.log production 3.log added
ActiveRecord::ConnectionTimeoutError (could not obtain a connection from the pool within 5.000 seconds (waited 5.000 seconds); all pooled connections were in use):
5 secconds is too short.Which file/parameter couled be setted about this timer?
Updated by Go MAEDA over 5 years ago
Could you paste the environment information? You can find it on admin/info page.
Updated by haobin li over 5 years ago
Go MAEDA wrote:
Could you paste the environment information? You can find it on admin/info page.
Information
Redmine 4.0.3.stable
Default administrator account changed
Attachments directory writable
Plugin assets directory writable (./public/plugin_assets)
RMagick available (optional)
ImageMagick convert available (optional)
Environment: Redmine version 4.0.3.stable Ruby version 2.6.0-p0 (2018-12-25) [x86_64-linux] Rails version 5.2.2.1 Environment production Database adapter Mysql2 Mailer queue ActiveJob::QueueAdapters::AsyncAdapter Mailer delivery smtp SCM: Subversion 1.7.14 Git 1.8.3.1 Filesystem Redmine plugins: no plugin installed
Updated by pasquale [:dedalus] about 5 years ago
It sound the same issue of #32314 where I have detected the magic number equals to 30
Updated by jianmin Zhang over 4 years ago
Have you solved this problem? I have the same problem when I use:
Completed 500 Internal Server Error in 5004ms (ActiveRecord: 0.0ms)
ActiveRecord::ConnectionTimeoutError (could not obtain a connection from the pool within 5.000 seconds (waited 5.003 seconds); all pooled connections were in use):
Updated by bill auger over 4 years ago
i have no solution; but instead, i have changed the 500 page to read: "sorry, server is overloaded - please wait while we reconnect you ..."; and added a meta-refresh - it is super tacky; but it has stopped the complaints for now
Updated by bill auger over 4 years ago
FWIW - i just noticed this ticket is categorized as "Email notifications"; while my ticket #31241 is categorized "Database" - these are almost certainly duplicates though
Updated by Marius BĂLTEANU over 4 years ago
- Is duplicate of Defect #31241: intermittent 500s ActiveRecord::ConnectionTimeoutError added
Updated by Marius BĂLTEANU over 4 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
I'm closing this in the favour of #31241, I've added some notes there.