[omniORB] omniORB python supplier apparently disconnecting external consumer from event channel?

[Duncan Grisby]

On Friday 23 June, "K. Workman" wrote:

[...]
> 1) When the Python supplier sends the message, the Python consumer
> sees the message, but the Java consumer does NOT.
> 2) Going forward, messages sent by the Java supplier can no longer be
> seen by the Java consumer. However, the Python consumer can see the
> messages sent by the Java supplier.
> 3) When I restart the Java consumer, it can see the messages sent by
> the Java supplier. Until, that is, I send a message from my Python
> supplier.

It sounds to me as though whatever the problem is, it's with the event
channel implementation, rather than any other part of the system. You
say that you are using TAO's event service. I know that TAO has lots of
debugging options, similar to omniORB's traceLevel, so you might try
activating that and seeing what gets logged. I don't know the details of
how you do that for TAO.

What happens if you do not register the Python consumer, but just send
messages from the Python supplier?  Does that also break the Java
consumer?

Are the producers and consumers in the same process as each other?

Do you see anything interesting if you run the omniORB code with
-ORBtraceLevel 25 -ORBtraceInvocations 1 -ORBtraceThreadId 1

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --