LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview: CORBA ORB problem

Dear LabVIEW gurus,

I'm currently writing a bridge (i.e. a binding) between our distributed control system and LabVIEW. This bridge is a visual C++ DLL (or a GCC .so under Linux) that makes use of other DLLs containing the CORBA implementation (omniORB). Everything works as far as I don't try to run the ORB in order to activate our CORBA event consumer. I mean: the pure CORBA client code works perfectly but running a CORBA servant causes problem.

It seems that the ORB�s threads remain blocked on their condition variable. They are never woken up by external requests. The strange thing is that the same scheme works when I replace LabVIEW with a home made application.

Is there something in LabVIEW that could explain this behavior? I ca
n explain why the socket activity is never dispatch to the ORB threads. Any idea? Thanks for your help.
NL.
0 Kudos
Message 1 of 3
(2,830 Views)
I obviously meant: "I CAN'T explain why the socket activity is never dispatch to the ORB threads". Sorry.
0 Kudos
Message 2 of 3
(2,826 Views)
Hello nl-soleil,

To respond to your question, I need to have more information about the problem :
1 - Have you a message error?
2 - You say : "The strange thing is that the same scheme works when I replace LabVIEW with a home made application.", so is it not only LV behavior?

Waiting for your response.

Sanaa TAZI
National Instruments

Sanaa T.
National Instruments France

0 Kudos
Message 3 of 3
(2,808 Views)