[Ace-users] Re: [ciao-users] calling Plan_Launcher leads to Execution_Manager coredump

Gan Deng gan.deng at vanderbilt.edu
Tue Jul 10 08:47:19 CDT 2007


Hi,

Could you please replace your .dat file with the one attached in my 
email and see whether it works better? I recall that some bug crept in 
when we refactored DAnCE code in parsing CORBA LOC map configuration 
file. Please let me know if this works or not.

Thanks,
Gan

Friedhelm Wolf wrote:
> CIAO VERSION: 0.5.8
> TAO VERSION : 1.5.8
> ACE VERSION : 5.5.8
> 
> HOST MACHINE and OPERATING SYSTEM:
>     i686 pc, SUSE linux Enterprise Server 9, Kernel 2.6.5
> 
> COMPILER NAME AND VERSION (AND PATCHLEVEL):
>     gcc 3.3.3 (SuSE Linux)
> 
> THE $ACE_ROOT/ace/config.h FILE:
>     #include "config-linux.h"
> 
> THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE :
>     include $ACE_ROOT/include/makeinclude/platform- linux.GNU
> 
> CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
>     (used by MPC when you generate your own makefiles):
>     N/A
> 
> AREA/CLASS/EXAMPLE AFFECTED:
>     DAnCE
> 
> DOES THE PROBLEM AFFECT:
>     EXECUTION: Plan_Launcher / Execution_Manager
> 
> SYNOPSIS:
>     calling Plan_Launcher leads to Execution_Manager coredump
> 
> DESCRIPTION:
> Hi there,
> 
> I try to deploy a simple component application, consisting
> of two components, running on one node
> (see attached StandaloneDeployment.cpd).
> 
> I followed the Simple Quoter tutorial to write a script
> which starts up the necessary DAnCE executables
> (see attached deploy.sh and Standalone.dat).
> 
> As a result the following output indicates a coredump:
> 
>     CIAO_NodeManager IOR: 
> IOR:010000001f00000049444c3a4349414f2f4e6f64654d616e616765724461656d6f6e3a312e300000010000000000000068000000010102000a0000006c6f63616c686f73740033831b00000014010f00525354cb339346c43908000000000001000000010000000002000000000000000800000001000000004f41540100000018000000010000000100010001000000010001050901010000000000 
> 
>     CIAO_NodeManager is running...
>     
>     CIAO_ExecutionManager is running...
>     
>     CIAO::Plan_Launcher_i: In ExecutionManager, the Priority Model 
> Policy is not exposed. Use non-RT mode.
>     (28610|182977823424) Initializing the Xerces runtime
>     CIAO (28605|182954076800) calling this->man_.is_plan_available()...
>     CIAO (28605|182954076800) Plan wasn't already available
>     CIAO (28605|182954076800) About to instantiate 
> CIAO::DomainApplicationManager_Impl
>     CORBA EXCEPTION: system exception, ID 
> 'IDL:omg.org/CORBA/COMM_FAILURE:1.0 <http://omg.org/CORBA/COMM_FAILURE:1.0>'
>     TAO exception, minor code = 6 (failed to recv request response; 
> ENOENT), completed = MAYBE
> 
>     Deployment failed. Plan_Launcher exiting.
>     ./deploy.sh: line 8: 28605 Segmentation fault      (core dumped) 
> $CIAO_ROOT/DAnCE/ExecutionManager/Execution_Manager -o EM.ior -i 
> Standalone.dat
> 
> I attached the stack of the dump file (Execution_Manager.dump).
> 
> Can you give me any hints, whats going wrong here. I generated the
> deployment plan using CoSMIC. I'm not shure, if anything within there
> is correct, but it seems to me, that the problem might even occur
> before the deployment plan is executed by the Plan_Launcher.
> 
> Any help is appreciated.
> 
> Thanks,
> Friedhelm
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ciao-users mailing list
> ciao-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/ciao-users

-------------- next part --------------
StandaloneNode corbaloc:iiop:localhost:99123/NodeManager


More information about the Ace-users mailing list