Marcel Herrguth

**Warning** This is a behavior change and thus might be a potential breaking change.

I'm unable to reproduce the issue you're discribing.

Note sure if this applies to database connections as well, I currently am watching these kind of issues: scheduler_err.log: ``` # terminated with exception (report_on_exception is true): /opt/zammad/lib/sessions.rb:780:in `rescue in...

I'm currently seeing about 5 instances (no matter if SaaS or package installation) per week that are affected by this issue.

By now it's 10+ instances.

Yes, just appeared on a current stable 5.0.2!

Fresh sample: ``` # terminated with exception (report_on_exception is true): /opt/zammad/lib/sessions.rb:603:in `rescue in thread_client': STOP thread_client for client .642600 after 10 tries (RuntimeError) from /opt/zammad/lib/sessions.rb:578:in `thread_client' from /opt/zammad/lib/sessions.rb:534:in `block (3...

Found this in production.log today on a 4.0: ``` E, [2022-01-12T17:10:18.460731 #27246-69867880158340] ERROR -- : thread_client 47189514724960 exited with error # E, [2022-01-12T17:10:18.464578 #27246-69867880158340] ERROR -- : /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4.6/lib/active_support/cache/file_store.rb:91:in `delete' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4.6/lib/active_support/cache/file_store.rb:91:in...

> @MrGeneration is this still a thing with recent cache changes and Redis? What cache changes? Could you please expect me not to know every little code change in every...

If not already and you're sure this is a bug please do create an issue to it.