I understand now where the executor is supposed to enter at (Gmanager) and it
is actually hitting it (in the ping Manager function) , it is not hitting
anything else in the GManager object (or GNode, ManagerContainer, Mexecutor,
MexecutorCollection or anything else as far as I can tell). I have break
points set up all over the place but the only thing that gets hit is the ping
method. When I look in the call stack, all it says is native to managed
transition. I can step through the code, but all it does is make a few log
entries then exits.
I would think it was the executor, but I have the manager running on another
computer(that manager is from the msi installer) and the executor can connect
to that one easily. If I step through the code, it does hit an area that
creates a stack trace object, but I cant seem to find any usefull info in
there. I tried working it backwards (as in starting the source with the
executorexec as the startup object) but the executor in source has problems of
its own that I havent even started to trace out.
Any ideas where I could look for the next clue?
________________________________
From: Richard Foreman <[email protected]>
To: [email protected]
Sent: Sun, April 3, 2011 7:08:37 AM
Subject: [Alchemi-users] Im back again
Hello again,
Heres a stupid little question I shouldve asked up front apparantly. Which
version of the source files are the msi installer packages built from? The
reason I ask is because I loaded the manager and executors from the installer
packages and had it working right off the bat, I could submit apps, the
executors ran the threads, fired the events, and returned data and looks like
it
runs great as far as it goes. Though truth be told, I did not verify the
returned data, however that is, the source I have (version 1.0.6 I believe,
whatever was listed as the latest) does not run.
Now, after playing around with it, I was able to get the manager up and
running, however, I cannot get anything to connect to the manager once it is
running. I dont know much about programming tcp, but think I have identified
at least the area I am stuck on. I believe it is supposed to work like this:
The executor sets up a tcp channel and registers it in the GNode object
(through the GetRemoteRef function) then communicates through that.
The manager sets up a tcp channel through the ManagerContainer object
(through
the Start function) then it registers a wellknown service (again through the
Start function) which I take to be the listener?
What I am not sure of is what causes the manager to react to something
happening on the channel? Im still reading up on the tcp service, but I would
think it would be responding to an event or something, but I have not found the
manager registering with a delegate to handle anything even remotely close to
that.
When I am trying this out, I am using the executor from the msi installer
package (which I know works as far as being able to connect and communicate
with the manager) and the source for the manager set with the managerexec
project as the start up project. I guess my main questions are is this the
correct configuration to start up the manager and what is supposed to be the
entry point for an executor when contacting the manager. I havent been able to
pin down the exact function that would get fired when the executor first
contacts the manager (or how that function would get fired).
I really am trying not to bug you too much, and am spending most of my time
reading up on the parts I do not understand clearly, but sometimes it helps to
be pointed in the right direction to get going.
Thanks,
Richard------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
alchemi-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alchemi-users
