/usr/share/backgroundrb/doc/content/faq/faq.txt is in libbackgroundrb-ruby1.8 1.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | <div id="content">
%(entry-title)<a name="faq"> Frequently asked Questions </a>%
*(content_list) *How does it work with ActiveRecord in multi-threaded environment?*<br/>
You can use _BackgrounDRb_'s inbuilt thread pool for executing tasks
concurrently. We are using @allow_concurrency = true@ for @ActiveRecord@
models, which is known to create problem with Oracle database adapters, if
you are using Oracle db, you can turn it off, by removing @allow_concurrency = true@.
* *Whats the deal with persistent job queues?*<br />
Well, its used for persisting tasks to the table, so as later
then can be inspected for status and results. Before using this feature.You should
run @rake backgroundrb:setup@ and run @rake db:migrate@ for creation of required
table.
* *My worker dies silently*<br />
First,make sure you have logging enabled (Meaning, you are not using @:debug_log false@
in your config file).Second, if a worker dies, the backtrace should be written to the
file @RAILS_ROOT/log/backgroundrb_debug_xxxx.log@. Third, You should not pass
entire @ActiveRecord@ model's around, this could cause hard to debug problems.AR objects
don't serialize well across tcp sockets. If none of this helps, hit us on the mailing list.
* *Master server died silently*<br/>
If _BackgrounDRb_ master server dies, its definetely a bug in _BackgrounDRb_, exception
should be still logged in same @RAILS_ROOT/log/backgroundrb_debug_xxxx.log@ file. Copy
the exception and file a bug report.
* *Where do I file bug reports?* <br />
You can submit bug reports at: "http://backgroundrb.devjavu.com/report/":http://backgroundrb.devjavu.com/report/.
* *Result caching is not working properly* <br />
Switch to memcache for storing results. More information "here:"http://localhost:3000/workers/#result_caching.
* *Dynamically started workers through @new_worker@ are not working* <br />
Use, the worker key that was used for accessing dynamically started workers.
* *BackgrounDRb server is not starting*<br />
Make sure, you have latest version of chronic and packet gems installed.After
that, clone the git repository (or download a snapshot from github) and run
@rake backgroundrb:setup@. If you are upgrading make sure, that older
autogenerated scripts namely, @load_worker_env.rb@ and @backgroundrb@
are removed from script directory of your rails application before running
rake task.If you are upgrading to 1.1, check if @scheduled_at@ column
is there in @bdrb_job_queues@ table.
</div>
|