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

[K. Workman]

Actually, I've not tried only registering the python supplier (not the
python consumer). That is an interesting idea, I'll give it a shot.

The Java producer and consumer are in different processes. However, the
python producer and consumer are in the same process.
I took a look at the logs last night, but there was alot of information
to wade through. I'll pull them apart more carefully, tonight.

The whole issue is just so strange. Why the applications work as
expected on my office PC, but not on my laptop has got me intrigued.
Particularly, in the manner of failure. Why it would partially work on
my laptop, until I brought the python supplier in the loop is even more
strange.

However, I definitely like the idea of not registering the python
consumer. and seeing what happens.

Thanks for the input!

Duncan Grisby wrote:
> 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.
>
>