Backgroundrb devel - Aug 2006 - Ezra....allow_concurrency = false?

In a previous email you wrote this:

	Glad you''re getting some use out of the plugin ;) ActiveRecord does
have some issues with threading and concurrency that can sometimes
cause that error you are seeing. Open up your script/backgroundrb/
start  file and comment out the following line:

ActiveRecord::Base.allow_concurrency = true

	Make sure you do that up in your main app script folder and not in
the plugin. Well you can do it in the plugin as well to keep it
consistent. Then you need to restart the drb server. Give this a shot
and see if it gets rid of your problem. Also I am curious about using
this plugin on textdrive. Did they give you an extra port number to
run it on? If you run into problems with running the drb server on a
port then let me know and I can show you how to use a unix domain
socket file instead so you don''t take up an extra port.

You wrote that in response to getting rid of the MySQL server has  
gone away error. Why would you comment it out in the app and not in  
the start script? Wouldn''t you want to comment it out in the plugin  
start script?

Thank You,
Ben Johnson
E: bjohnson at contuitive.com
O: 800-341-6826
M: 817-229-4258



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060818/aeeedef5/attachment.html

On Aug 18, 2006, at 3:14 PM, Ben Johnson wrote:
> In a previous email you wrote this:
>
> 	Glad you''re getting some use out of the plugin ;) ActiveRecord
does
> have some issues with threading and concurrency that can sometimes
> cause that error you are seeing. Open up your script/backgroundrb/
> start  file and comment out the following line:
>
> ActiveRecord::Base.allow_concurrency = true
>
> 	Make sure you do that up in your main app script folder and not in
> the plugin. Well you can do it in the plugin as well to keep it
> consistent. Then you need to restart the drb server. Give this a shot
> and see if it gets rid of your problem. Also I am curious about using
> this plugin on textdrive. Did they give you an extra port number to
> run it on? If you run into problems with running the drb server on a
> port then let me know and I can show you how to use a unix domain
> socket file instead so you don''t take up an extra port.
>
> You wrote that in response to getting rid of the MySQL server has  
> gone away error. Why would you comment it out in the app and not in  
> the start script? Wouldn''t you want to comment it out in the
plugin
> start script?
>
> Thank You,
> Ben Johnson
> E: bjohnson at contuitive.com
> O: 800-341-6826
> M: 817-229-4258
	When you run the rake backgroundrb:setup task it copies the start  
script up into your apps script directory. So you need to make the  
change up there. Or you can make the change in the plugin and then  
rerun the setup task if you like. Either way its the same thing. You  
need to make the changes to the start script that is in the script/ 
backgroundrb directory of your rails app in order for them to be used.

	Does that answer your question?

-Ezra
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060818/4988b2ed/attachment.html