RedHawk IDE cannot connect to domain manager after launch attempt

510 Views Asked by At

I am attempting to test my first waveform built with RedHawk running on CentOS. It has two components and they run ok in the sandbox, but when I attempt to launch a domain in order to test it as a waveform, it fails with a CORBA_COMM:Failure vmcid SUN minor code 201. If I turn debug level up to DEBUG or TRACE I can see that the domain manager starts and binds to the Naming Service and the last line in the console is Starting ORB! then a popup giving the CORBA_COMM failure. I can see the DomainManager proc running with ps and using nameclt I can see the domain registered in the NamingService, but the CORBA Name Service tab in the IDE does NOT show it (both nameclt and the IDE show EventChannelFactory). The IOR returned by nameclt and the one listed in the IDE console DEBUG line differ (shouldn't they match?).

This is somewhat similar to a question asked jerhil Jan 9 although he was using Fedora 20, but there has never been an answer to that question.

2

There are 2 best solutions below

3
On BEST ANSWER

I had the same problem. What seemed to be wrong for me was a fix I used from This stackoverflow article Sandbox not Appearing in SCA Explorer. If you had this same issue and used this fix I would suggest trying one of these fixes instead as they both worked for me.

1.) (This is probably the better method to try)
Follow the answer given to this question: Cannot Change Component Property Values

2.)If that didn't work try:

a.)Uncomment the line in eclipse.ini suggested in the linked post
b.)Comment out the line directly below it:
-Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORB

After doing either of these solutions and restarting the IDE I was then able to launch a domain manager from the IDE.

Hopefully this helps

0
On

Try restarting the omniNames and omniEvents using this guide: http://redhawksdr.github.io/Documentation/mainap8.html#x34-430000H

Most of the time hard reset works over soft reset. If that doesn't work, try running the simple waveform mentioned in the redhawk documentation. If you can run that fine, then it's probably the component itself that's causing the issue.