| Hi,
I can't offer any help, but I'm seeing the same thing on OpenVMS OBB V2.7.
I would guess that this is a legacy behaviour from post V2.5A. What OBB
used to do was to 'pick a favorite' server process when there were
multiple servers offering the same implementation. So you might see several
servers (I should server processes) created but only one would be used.
I believe an improvement to V2.6 was to 'round robin' requests amongst
the servers so that the workload would be more evenly shared. At the time
this was a good idea for my application.
Then the rules about Initial Object References and Server Creation were
tightened up - but I bet the round robin code (which ought to be archaic)
was left in. I had a server running debug and one created by the Agent, requests
were sent to these in turn (no randomness).
I don't really mind if the 'round robin' server allocation stays, as I could
make good use of it. I would rather not depend on it though if it is
going to get 'fixed' in a future release.
Mark
|
| If the objects are statically bound, then the clients should only
go to one server.
When does the client go to a different server - on the first invoke
of the root factory object or on the invokes on statically bound
objects ? Please post a trace of the client with trace flags
of RINV.
Do you want one client per server with each client going to
the same server each time ? If so, then a factory implementation
(server per method) that returns a statically bound object
to the real implementation is the easiest way.
|