I am working on a Ruby on Rails v2.3.8 real estate application. I wrote a rake to pull out lists of properties and photos. The application uses rets4r (specifically josephholsten-rets4r) to talk to the RETS server, and Paperclip is used to manage property photos and push them to S3.
The problem I see is that the rake task never completes. At one point, it will always spin, and it will never be in one place. Once it crashed 45 minutes after some minor changes (added a few start / rescue blocks to try to track the error), it seems that it works longer (2-12 hours), but it still crashes.
The error I get is always "Rake aborted" and then "thread [memory address] tried to join itself." Searching the logs helps nothing. Only standard Paperclip log messages. I'm also not intentionally trying to do something multithreaded in a rake task.
Update . I used gem version 1.1.17 from rets4r. However, I notice on the Github page for the project, there have been many commits since this version was flagged. One of those commits is talking about removing thread usage.
Jared source
share