-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tenant is not switched in Active Job #102
Comments
Thank you for reporting. Will take a look at your sample app ASAP. |
Hi @holidayworking! Are you using Apartment::Activejob - https://github.com/rails-on-services/apartment-activejob? |
Sorry for my absence. It's been very difficult for me to follow up with everything. |
I've looked at the original gem and some people were complaining about it as well. I'll try to play a bit with this solution and have a workaround to make it cleaner |
@rpbaltazar I'm experiencing the problem from influitive/apartment-sidekiq#27 (comment) myself, even though I followed everything that was recommended there, in passing in the args - I'm stuck with running sidekiq with only 1 concurrent job at a time, something that is going to be affecting scaling. As this will affect us as we scale, I'm able to spend time troubleshooting as well - and happy to contribute.
|
Steps to reproduce
I need to run a job like the one below for each tenant.
Therefore,
config/initializers/active_job.rb
is as follows.I created a sample app to report this issue.
If you execute the following with this app, it will be reproduced.
Expected behavior
A tenant is switched in Active Job.
Actual behavior
The following is output to the
log/development.log
, and it seems that a tenant is not switched.System configuration
config/initializers/apartment.rb
or so):use_schemas
:true
The text was updated successfully, but these errors were encountered: