[Ace-users] Re: [ciao-users] callingPlan_LauncherleadstoExecution_Managercoredump

[Friedhelm Wolf]

Hi there,

after having another close look, I have to correct my assumptions.
In the stack, the call arrives at CLoggerClient_exec_i correctly (frame 17)
and triggers a collocated call to CLogger, using a receptacle/facet
connection. This call is dispatched until it ends up in the
CLogger_svnt.cpp.

Maybe there's something wrong with collocated calls, when two components exist
within the same node application? Did I forget to initialize something here?

Thanks,
Friedhelm

On 7/26/07, Friedhelm Wolf <friedhelm.wolf at googlemail.com> wrote:
> Hi Johnny,
>
> > The log just tells me enough what is happening. Can you maybe run your app
> > in the debugger and see what is received in the server?
>
> debugging the whole thing was not easy, but it helped a lot:
> I found out, that actually the whole node application seg faults, when
> the request
> is coming in (I could have realized that, if I'd had a look at the
> running processes,
> because behind the NodeApllication, there was the hint <defunct>).
>
> Actually the code, where the application crashes is autogenerated by the
> idl compiler, so maybe some CIAO people can help here.
>
> I attatched the stackdump. The codesnippet, where the whole thing crashes is:
>
>   template <typename T>
>   void
>   ILogger_Servant_T<T>::WriteMessage (
>     const char * messageSource,
>     const char * messageType,
>     const char * messageText
>   )
>   {
>     this->executor_->WriteMessage (
>       messageSource,
>       messageType,
>       messageText
>     );
>   }
>
> The reason for crashing is, that the executor_ member variable is a var
> class containing a null pointer at that moment.
>
> However, this is very strange because I do not want to connect to the
> CLogger component (to which the call seems to be delivered according
> to the stackdump), but to the CLoggerClient.
>
> After thinking about that, I have to assumptions:
> 1. Maybe the IOR generation mechanism in CIAO isn't working correctly
> all the time and I therefore end up in the wrong component.
> 2. It is not allowed to deploy two components to the same container,
> as I did (see attached deployment plan).
>
> Any comments on that?
>
> Thanks,
> Friedhelm
>
> On 7/26/07, Johnny Willemsen <jwillemsen at remedy.nl> wrote:
> >
> >
> > Hi,
> >
> >
> > Johnny
> >
> >
> >  ________________________________
> >  From: ciao-users-bounces at cse.wustl.edu
> > [mailto:ciao-users-bounces at cse.wustl.edu] On Behalf Of
> > Friedhelm Wolf
> > Sent: Wednesday, July 25, 2007 1:34 PM
> >
> > To: CIAO Users Mailing List
> > Subject: Re: [ciao-users]
> > callingPlan_LauncherleadstoExecution_Managercoredump
> >
> >
> > Johnny,
> >
> >
> >
> > >
> > >
> > >
> > > In the log I see the output below. Is this expected?
> > >
> > > Johnny
> > >
> > > TAO (24614|182954076800) - Transport[10]::cleanup_queue, byte_count = 582
> > > TAO (24614|182954076800) - Transport[10]::cleanup_queue, after transfer,
> > bc = 0, all_sent = 1, ml = 0
> > > TAO (24614|182954076800) -
> > Transport[10]::drain_queue_helper, byte_count = 582,
> > head_is_empty = 1
> > > TAO (24614|182954076800) - Transport[10]::drain_queue_i, helper retval = 1
> > > TAO (24614|182954076800) - Transport[10]::make_idle
> > > TAO (24614|182954076800) -
> > Leader_Follower[10]::wait_for_event, (leader) enter reactor
> > event loop
> >
> >
> > The first part of the log seems rather normal. Right? The Orb just listens
> > on the connection.
> >
> >
> > >
> > >
> > > Unable to find policies for the receptacle
> > logger_LoggerComponentEnvironment.ComponentImplementations.LoggerSystem.LoggerSystem.CLoggerClient
> > > In Servant_Impl_Base::add_receptacle (logger)
> > > Found no receptacle named (logger)
> > > Successfully added new receptacle named (logger)
> >
> >
> > I assume that this message is not a problem, because it appears in the Hello
> > example as well,
> > and the problem I have does not occur there.
> >
> > Thanks,
> > Friedhelm
> >
> >
> > >
> > >
> > >
> > > ________________________________
> >  From: ciao-users-bounces at cse.wustl.edu
> > [mailto:ciao-users-bounces at cse.wustl.edu] On Behalf Of
> > Friedhelm Wolf
> > > Sent: Wednesday, July 25, 2007 12:07 PM
> > >
> > > To: CIAO Users Mailing List
> > > Subject: Re: [ciao-users] calling
> > Plan_LauncherleadstoExecution_Managercoredump
> > >
> > >
> > >
> > > Hi Johnny,
> > >
> > >
> > >
> > > >
> > > >
> > > > Are you really sure the client connects to the correct server? The
> > client connects to 131.176.53.15 and then port 33137 but in the server log I
> > don't see any reference to post 33137.
> > >
> > >
> > > As I found out, I forgot to give the -ORBDebug option to the DAnCE
> > NodeApplications, which are started, so the server log was not complete.
> > > The IOR I am using to connect to the CLoggerClient component is generated
> > automatically by the Container_Impl class.
> > > I attatched the catior output, which looks good as well. In the new log,
> > there is a connection on the corresponding port,
> > > so I guess, the correct server is addressed.
> > >
> > > Any other hints?
> > >
> > > Thanks,
> > > Friedhelm
> > >
> > >
> > > >
> > > >
> > > > Johnny
> > > >
> > > >
> > > > ________________________________
> >  From: ciao-users-bounces at cse.wustl.edu [mailto:
> > ciao-users-bounces at cse.wustl.edu] On Behalf Of Friedhelm
> > Wolf
> > > > Sent: Tuesday, July 24, 2007 5:20 PM
> > > > To: CIAO Users Mailing List
> > > > Subject: Re: [ciao-users] calling Plan_Launcher
> > leadstoExecution_Managercoredump
> > > >
> > > >
> > > >
> > > > Hi Johnny,
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > Looks like the program you call closes the connection. Can you also
> > provide the log of the other side?
> > > >
> > > >
> > > > See attatched file for the complete log output of the running deployment
> > until the connection
> > > > effort of the executable.
> > > >
> > > > Thanks,
> > > > Friedhelm
> > > >
> > > > _______________________________________________
> > > > ciao-users mailing list
> > > > ciao-users at mail.cse.wustl.edu
> > > > http://mail.cse.wustl.edu/mailman/listinfo/ciao-users
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > ciao-users mailing list
> > > ciao-users at mail.cse.wustl.edu
> > > http://mail.cse.wustl.edu/mailman/listinfo/ciao-users
> > >
> > >
> >
> >
> > _______________________________________________
> > ciao-users mailing list
> > ciao-users at mail.cse.wustl.edu
> > http://mail.cse.wustl.edu/mailman/listinfo/ciao-users
> >
> >
>
>