On Thu, Jul 26, 2007 at 09:57:32AM +0200, Izit Izit wrote:
> Maybe this is a way to the solution: Observers.
> 
> for my problem model 'Mutation' I also have configured an observer. With 
> the observer defined and remote set to true in the model, DRB server 
> does not start. If I remove the observer statement, the DRB server 
> starts without a problem.
> 
> This may also explain why mongrel has the AAF log messages during 
> startup because it is accessing the Model because of the observer 
> statement.

Yeah this problem is known - when the model gets loaded during rails
startup (the DRb server runs in a full Rails environment) and therefore
before the server itself is started, aaf inside the model has no way to
know it is running inside the server and so tries to connect to the
server which of course isn't there yet. However recent aaf (0.4.1 or
trunk) should not have this problem, it uses an environment variable set
in script/ferret_start to tell aaf it shouldn't try to connect to DRb.

Jens

-- 
Jens Krämer
webit! Gesellschaft für neue Medien mbH
Schnorrstraße 76 | 01069 Dresden
Telefon +49 351 46766-0 | Telefax +49 351 46766-66
[EMAIL PROTECTED] | www.webit.de
 
Amtsgericht Dresden | HRB 15422
GF Sven Haubold, Hagen Malessa
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to