Topic
|  | CORBA::COMM_FAILURE
|  | Cause
|  | These error messages occur when the other end of a communication crashes before completing its reponse. The top level executor application (dance_plan_launcher) should help to localize the source of the error to a particular node/LocalityManager instance if this error occurs during deployment. Most often, this error is generated as part of deployment in user code that causes a segmentation fault or other hard crash of the LocalityManager process.
|  | Troubleshooting
|  | On Linux-like operating systems, these errors can be localized by causing the LocalityManager to generate a core file. Note, however, that debugging symbols must be enabled to take the following steps: $ ulimit -c unlimited # Cause the COMM_FAILURE to occur $ gdb /path/to/core $DANCE_ROOT/bin/dance_locality_manager # Once GDB has loaded, at its command line > where
|  | CORBA::TRANSIENT
|  | Cause
|  | These errors occur when the other end of a synchronous communication is not present before communication begins. The most common cause of this error is when the location for the ExecutionManager provided to dance_plan_launcher is incorrect, or when the node location provided in the domain descriptor (CDD) file provided to the ExecutionManager is incorrect. These errors can infrequently occur at application run-time if a component invokes an invalid connection.
|  | Troubleshooting
|  | If the error occurs during deployment, dance_plan_launcher will produce an error diagnostic that will help to localize the source of the error.
|  | Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion `map->l_init_called' failed!
|  | Cause
|  | This error message may occur when one library which is explicitly loaded (e.g., a component implementation) links another library that is explicitly loaded (e.g., another component implementation or a deployment interceptor). This error message is emitted from the low-level Linux libraries like ld.so. While this error is innocuous, and appears only on shutdown, it can be problematic for automatic error detection scripts.
|  | Troubleshooting
|  | This can be addressed by refactoring the code such that the shared code is in a separate, not explicitly loaded library.
|  | PlanLauncher - Error: Unable to read in XML plan
|  | Cause
|  | This error indicates that there was some problem loading the CDP file, typically due to a syntax issue. This error should be extremely rare for model generated deployment plans.
|  | Troubleshooting
|  | Re-generate the plan from your model.
|  | There should be some debugging information output by the dance_plan_launcher that will indicate the source of the error in the XML deployment plan.
|  | 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
|  | Cause
|  | This messages indicates that there was some problem loading the component from the shared library
|  | Troubleshooting
|  | Verify that the library name in the component deployment plan (CDP) is correct
|  | Verify that the library is on the search path for dynamic loading (e.g., LD_LIBRARY_PATH
|  | Verify that the library in question does not have unresolved dependencies. This can be accomplished in Linux with "ldd -r".
|  | Entry point invalid in DLL
|  | Cause
|  | This message indicates that there was a problem loading a component DLL because the component factory operation was invalid.
|  | Troubleshooting
|  | Verify that the component factory operation in the CDP is correct and matches the 'extern "C"' factory function in the _exec.cpp and _svnt.cpp files.
|  | Verify that all dependencies of the library are present on the load path. On Linux this can be accomplished by executing: $ ldd -r libraryName_exec.so
|  | Executor factory failed
|  | Cause
|  | This message indicates that the factory method which constructs the component executor has failed by returning a nil pointer.
|  | Troubleshooting
|  | Verify that the executor factory method does not return a nil pointer.
|  | Caught BAD_PARAM while setting attributes.
|  | Cause
|  | This message indicates that there was a type mismatch when attempting to populate the initial value for an attribute, e.g.: The component interface has an attribute of type "string" but the CDP encodes the attribute as a "long".
|  | Troubleshooting
|  | Correct the mismatch between the CDP file and the component interface.
|  | NodeManager not found
|  | Cause
|  | The DomainApplicationManager was unable to resolve a reference to a remote node manager instance.
|  | Troubleshooting
|  | Ensure that the IOR identified in the CDD document is correct
|  | Ensure that the remote NodeManager has completed startup before attempting to launch the plan.
|  | 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
|  | Cause
|  | This indicates that the remote end of a connection was not deployed. Note that this may be innocuous in the event that this deployment is part of a progressive deployment scenario.
|  | Local connections require exactly 2 internalEndpoints
|  | Cause
|  | This message indicates that there was a problem establishing a local connection, e.g., between a component and its connector.
|  | Troubleshooting
|  | Verify that the both endpoints is present in the *same* process.
|  | Verify that the both endpoints has deployed correctly.
|  | Unable to narrow external reference to CCMObject
|  | Cause
|  | The external reference used when connecting an external facet to a local receptacle must be a reference to the remote component, not the remote facet.
|  | 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
|  | Cause
|  | This error indicates that an artifact field in a <implementation> field does not match any found in the component deployment plan.
|  | Troubleshooting
|  | Verify that the edu.vanderbilt.dre.CIAO.ServantArtifact and edu.vanderbilt.dre.CIAO.ExecutorArtifact execParameters name valid <artifact> entries in the same plan.
|  | No valid location field
|  | Cause
|  | The location field for the named artifact is empty.
|  | No Servant entrypoint provided, aborting installation
|  | Cause
|  | The edu.vanderbilt.dre.CIAO.ServantEntrypoint execParameter for a component is not present or invalid.
|  | No servant artifact identified.
|  | Cause
|  | The edu.vanderbilt.dre.CIAO.ServantArtifact execParameter for a component is not present or invalid
|  | No Executor artifact provided
|  | Cause
|  | The edu.vanderbilt.dre.CIAO.ExecutorArtifact execParameter for a component is not present or invalid
|  | No executor entrypoint provided
|  | Cause
|  | The 'component factory' execParameter for a component is not present or invalid.
|  | Invalid container
|  | Cause
|  | The edu.vanderbilt.dre.CIAO.ContainerId configProperty for a component is invalid.
|  | Troubleshooting
|  | If no edu.vanderbilt.dre.CIAO.ContainerId property is present, this error should not occur, as the component should be deployed in the default container.
|  | Verify that the edu.vanderbilt.dre.CIAO.ContainerId field on a component matches a valid container instance that has been deployed to the same process.
|  | Plan with same UUID already exists
|  | Cause
|  | A plan with the same UUID as the one you are attempting to deploy is already active.
|  | Troubleshooting
|  | Change the UUID if the plan you are currently attempting to deploy
|  | Ensure that two nodes in the CDD document are not aliased to the same node.