Getting "undefined method `Exit' for nil:NilClass" from therubyracer in Sidekiq

41 views
Skip to first unread message

Jack Royal-Gordon

unread,
Nov 1, 2015, 5:42:22 PM11/1/15
to sid...@googlegroups.com
I’m intermittently getting "undefined method `Exit' for nil:NilClass” when running therubyracer in Sidekiq on MRI 2.0. I found this page which indicates that only one instance of therubyracer can run per VM thread. So this leads we to wonder "Are separate Sidekiq Worker threads in the same VM thread, or in different VM threads?” Do I need to ensure that only one is running per worker process at any time?

Mike Perham

unread,
Nov 1, 2015, 6:27:03 PM11/1/15
to sid...@googlegroups.com
Therubyracer is not thread safe. No guarantees what it will do in sidekiq. 

On Nov 1, 2015, at 14:42, Jack Royal-Gordon <ja...@groundbreakingsoftware.com> wrote:

I’m intermittently getting "undefined method `Exit' for nil:NilClass” when running therubyracer in Sidekiq on MRI 2.0. I found this page which indicates that only one instance of therubyracer can run per VM thread. So this leads we to wonder "Are separate Sidekiq Worker threads in the same VM thread, or in different VM threads?” Do I need to ensure that only one is running per worker process at any time?

--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/B5627599-0CF7-4416-97AD-89A1CAB6F860%40GroundbreakingSoftware.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages