Ok. I still don't quite understand what's going on. The scenario I'm having trouble with is:
start app (which starts workers) using bundle exec trinidad --threadsafe --config config/trinidad.yml
make some changes
problem: workers either don't restart or crash, same with quartz-scheduler (which seems to mostly crash)
I tried using jruby-rack-worker and trinidad_worker_extension instead, unfortunately that doesn't seem to work either, on first start the workers boot up,
on touch tmp/restart.txt:
[org.kares.jruby.rack.DefaultWorkerManager] no worker script to execute - configure one using 'jruby.worker.script' or 'jruby.worker.script.path' parameter (or see previous errors if already configured) !
So basically it now claims there is no path to the startup script for the workers... I didn't change the config or anything.
Also a weird thing about trinidad_worker_extension was that bundler complained about jruby-rack-worker not "in any sources". I had to "gem install jruby-rack-worker" to get it to run, didn't matter if I put
jruby-rack-worker in the gem file or no.