From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CORBA & LabVIEW

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 can explain
why the socket activity is never dispatch to the ORB threads. Any idea? Thanks for your help.
NL.
0 Kudos
Message 1 of 2
(2,522 Views)
Hello,

First what are the version of the sofwares?
Then what are the steps you use to create your ORB object?
What is your home made application exactly?

regards,

Marc Larue
NIF
0 Kudos
Message 2 of 2
(2,481 Views)