On Aug 29, 2:09 am, Rui Ma <[email protected]> wrote:
> Hello Enrico,
>
> Your client code (Ruote code in your rails app) should not need to be
> changed. They should work exactly the way they are in the single-process
> server setup.
>
> undefined method `new' for #<DRb::DRbUnknown:0x114b7b0> means some of your
> objects at the remote engine server didn't get instantiated successfully.
> Similar to a nil.new error. One thing you can do is to run your app in debug
> mode. Calling the ruote engine code at the breakpoint might give you some
> more info.
>
> Please notice that there is a config/ruote_environment. Make sure you
> include all the plugins/classes you need in tha file as well.
Yeah, I noticed that the first time I tried to start it all up. I had
to bring a whole bunch of config.gem statements into there.
>
> *How would those participants then access the application models?*
>
> A "remote" engine doesn't interact with "local" models. In my case,
> ActiveRecord models' ids are carried by workitem fields. Particiapnts
> re-instantiate models on the remote engine side and process them.
Yeah, I do the same thing. Non-trivial ActiveRecord models don't
serialize particularly well.
>
> hard to tell why any expressions that use the scheduler didn't fired. More
> details are helpful.
Unfortunately, I have little in the way of details right now, though I
could dig around some more. The problem is that nothing is being put
into the ProcessError log for these expressions. I'll check over the
process history and see if anything shows up there, too.
Thanks,
Enrico
>
> -Rui
>
> On Fri, Aug 28, 2009 at 9:25 PM, John Mettraux <[email protected]>wrote:
>
>
>
>
>
> > On Sat, Aug 29, 2009 at 2:56 AM, Enrico Bianco<[email protected]> wrote:
> > > On Aug 28, 12:30 pm, John Mettraux <[email protected]> wrote:
>
> > >> Do I guess correctly when I say that the error occurs on the remote
> > >> (engine) side ?
>
> > > Unfortunately, I can't get a full stack-trace. That was inside the
> > > ProcessError log entry. But I think your guess is correct.
>
> > Hello Enrico,
>
> > the "inside the ProcessError log" is a capital piece of information ;)
>
> > >> > I know that this particular participant never instantiates any new
> > >> > objects, so I think this might be happening when the participant
> > >> > itself is being instantiated and passed the workitem by ruote.
>
> > >> Participants are instantiated at registration time.
>
> > > Strange, because if that's the case then why did the error occur
> > > during the process? *puzzled*
>
> > Maybe the "participant was trying to instantiate something" and not
> > "something was trying to instantiate the participant". You gave us no
> > stacktrace, no real info about the target of the "new" method ;)
>
> > > But in good news, I did get the participants to work, in the end. I
> > > shuffled code around so that the DRb process was defining and
> > > registering them instead of the application. Somehow that "Just
> > > Works." Now I'm just finding that any expressions that use the
> > > scheduler are not getting fired.
>
> > Ouch. Kind of a edgy setup that you have.
>
> > Well done !
>
> > --
> > John Mettraux - http://jmettraux.wordpress.com
--~--~---------~--~----~------------~-------~--~----~
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---
