Topic
> CORBA::COMM_FAILURE
> CORBA::TRANSIENT
> Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion
`map->l_init_called' failed!
> PlanLauncher - Error: Unable to read in XML plan
V StartError
* The StartError exception message indicates an error launching the application, and will have human readable error messages attached that will be emitted by the dance_plan_launcher. There are several potential causes of StartLaunch exceptions
> Unable to open executor DLL for component
> Entry point invalid in DLL
> Executor factory failed
> Caught BAD_PARAM while setting attributes.
> NodeManager not found
V InvalidConnection
* The InvalidConnection exception indicates that there was a problem creating a connection during deployment. There are several causes of InvalidConnection exceptions.
> Receptacle component not deployed
> Local connections require exactly 2 internalEndpoints
> Unable to narrow external reference to CCMObject
V PlanError
* This class of exceptions indicates that there was some aberration in the structure of the deployment plan, and should be infrequent for model-generated plans.
> No such artifact
> No valid location field
> No Servant entrypoint provided, aborting installation
> No servant artifact identified.
> No Executor artifact provided
> No executor entrypoint provided
> Invalid container
> Plan with same UUID already exists