[omniORB] Oddities in running OmniOrb client/server
Judy Anderson
yduj@harlequin.com
Wed, 24 Feb 99 15:01:17 EST
From: boris@imagine-sw.com (Boris Khanales)
Date: Wed, 24 Feb 1999 14:44:06 -0500
I did this some time ago. Few things to keep in mind:
1. In orbix, by default, all clients served by the same thread.
In omni - thread per client
2. It could be memory/references.
Thanks for that idea; perhaps I should run the whole thing through
purify.
I just thought of another thing that I forgot to tell people: my
machine is a dual processor. Perhaps I should try rebooting into
single processor mode, and seeing if the problem disappears.
Can you show an example?
One of my next plans for debugging this is to in fact create a small
example and see if I can reproduce the behavior. I'm afraid that my
current application is quite unwieldy, and would not serve as an
example. Hopefully, while creating the example, I will either
replicate the problem, or discover what I have done that caused in the
first place. This often happens.
Judy Anderson "yduJ"
yduJ@harlequin.com
617-374-2547