On Wed, 2008-03-05 at 13:42 +0000, Anthony Underwood wrote:
> Hi All
>
>
> I've been getting all kinds of problems since upgrading to 1.03
>
>
> Loads of crashes of the backgroundrb main script. script/backgroundrb
> stop fails to stop process so that script/background start fails due
> to the port already being bound
> example crash
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:32:in
> `load': undefined class/module Job (ArgumentError)
> from
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:32:in
> `receive_data'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_parser.rb:37:in
> `call'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_parser.rb:37:in
> `extract'
> from
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:31:in
> `receive_data'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:212:in
> `read_external_socket'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:204:in
> `handle_external_messages'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:178:in
> `handle_read_event'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in
> `each'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in
> `handle_read_event'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:130:in
> `start_reactor'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in
> `loop'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in
> `start_reactor'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:21:in
> `run'
> from
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:166:in
> `initialize'
> from script/backgroundrb:42:in `new'
> from script/backgroundrb:42
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_nbio.rb:25:in
> `read_data': Packet::DisconnectError (Packet::DisconnectError)
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_worker.rb:46:in
> `handle_internal_messages'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:176:in
> `handle_read_event'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in
> `each'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in
> `handle_read_event'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:130:in
> `start_reactor'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in
> `loop'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in
> `start_reactor'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_worker.rb:20:in
> `start_worker'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:133:in
> `fork_and_load'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:108:in
> `start_worker'
> from
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:169:in
> `initialize'
> from
> /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:19:in
> `run'
> from
> /home/f0/anthony/projects/minimum_snps/rails/minimum_snps/vendor/plugins/backgroundrb/server/lib/master_worker.rb:166:in
> `initialize'
> from script/backgroundrb:42:in `new'
> from script/backgroundrb:42
>
>
> The new api seems to be broken also
>
>
> MiddleMan.new_worker(:long_job_worker, :job_key => @job.job_key, :data
> => {:job => @job}) doesn't work reporting wrong number of arguments.
>
>
> Like the new web page but it seems that the documentation is not quite
> ready. For the moment I'll have to rollback to the old version which
> was working well.
>
However, 1.0.3 is fully backward compatible with old API, since new APIs
are nothing but syntatic sugar around older ones.
>
_______________________________________________
Backgroundrb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/backgroundrb-devel
