Displaying 3 results from an estimated 3 matches for "mon_exit".
Did you mean:
on_exit
2007 Jun 28
1
ThreadError from DRb server
...occurred in person#search:
current thread not owner
(druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in
`mon_check_owner''
(druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in
`mon_check_owner''
(druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:220:in
`mon_exit''
(druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:240:in
`synchronize''
(druby:/localhost:9010)
/var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:8:in
`synchrolock''
(druby:/localhost:9010)
/var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:267:in...
2008 Dec 26
4
''stack level too deep'' error
...ror? I see it once in 2-3 days and it goes away
when I restart backgroundrb. Quoted below is
my backgroundrb_server_11007.log file. Can I do anything to avoid this?
Thanks,
Raghu
==================================================================================
/usr/lib/ruby/1.8/monitor.rb:224:in `mon_exit'': stack level too deep
(SystemStackError)
from /usr/lib/ruby/1.8/monitor.rb:244:in `synchronize''
from /usr/lib/ruby/1.8/logger.rb:496:in `write''
from /usr/lib/ruby/1.8/logger.rb:326:in `add''
from /usr/lib/ruby/1.8/logger.rb:374:in `inf...
2007 Sep 18
10
Routes
hi all,
I want to move some routing tasks out of the router and into the
controller. The goal is to make Merb feel less like mod_rewrite and
give the user more control at the controller. The new Router is
simple: it takes the path_info (not the whole request) then outputs a
controller class and some parameters from the path matching. The rest
of the routing would be done at the controller level.