-
Notifications
You must be signed in to change notification settings - Fork 188
Core dumps with Sidekiq + Sequel w/TinyTDS #129
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
Comments
Can you install v0.6.0.rc1 and let me know how that works? |
I'm seeing the same errors in an Azure-hosted Rails app connecting to Azure SQ and v0.6.1. We don't see the error with older versions. |
Than your issue is likely due to work done in #121 it will take me some time before I can round back to that area. |
I have a patch to fix this landing very soon. |
From my testing, this should be fixed by #133 |
Closing this one then. |
Hello, TinyTDS team, I've been using your library for a few years now, with no issue, but recently ran into a problem with an application in which I moved our job scedule from a processed based Resque setup to a thread based Sidekiq setup. After running through some tests, I began to get CFP errors and core dumps. I've discusses this with both the Sidekiq and Sequel camps and they suggested I venture here. Below is a repost of the original issue I opened with Sidekiq:
Hi guys, replaced Resque with Sidekiq on two applications now and things have been running great for a few weeks.
Last night, I encountered an issue on one application that processes CSV files and stores them to a MS-SQL Server DB (connecting by using Sequel+TinyTDS). Everything has been working swimmingly until some jobs fired off that had to parse fairly large files (8+ MB). Once these jobs began, they would get about 1800 rows in and then dump core. This occurred on Ruby 1.9.3p448 - I then tested with Ruby 2.0.0p247 with the same result. Operating system is Linux 3.2.0-23, Ubuntu 12.04 distribution.
After tweaking, lowering thread pool to 4, standing on my head, etc, I unfortunately had to revert and move this application back to Resque. The crashes ceased once I went this route.
Below is the backtrace that fired off, I hope it can provide some insight on the issue, I'm eager to move back to Sidekiq.
I've also attached excerpts from two other traces that fired off slightly different errors.
The text was updated successfully, but these errors were encountered: