Re: [Oorexx-devel] ooRexx 4.0.0 RC3 / AIX 6.1 - update

[Rainer T. <ta...@ta...>]

Hello,
strange thing...

When I start the daemon in foreground then ooRexx works...

Bye
  Rainer


Rick McGuire wrote:
> Not much of a mystery there, the first send() method calls the second.
>  That's a perfectly normal looking call stack.  You're probably going
> to need to debug ApiServer::processMessages() method, which is what
> should be on the other end of this client connection.  Pay particular
> attention to the catch() blocks to see if some sort of error occurred.
>
> Also, you might want to check that you don't have an old version of
> rxapi running.  The latest builds are using the new port number, so it
> is possible that something has gotten messed up there.
>
> Rick
>
> On Mon, Jul 27, 2009 at 7:40 AM, Rainer Tammer<ta...@ta...> wrote:
>   
>> Hallo,
>> there is one strange thing in the call stack:
>>
>> ClientMessage.ClientMessage::send(SysClientStream*)(this =
>> 0x2ff20260, pipe = 0x30c13978), line 82 in "ClientMessage.cpp"
>> ..
>> ClientMessage.ClientMessage::send()(this = 0x2ff20260), line 59 in
>> "ClientMessage.cpp"
>>
>> I do not understand why both functions are active...
>>
>> I think somehow the initial connect does not go through and ooRexx does
>> not catch this.
>> Unfortunately my knowledge of the inner workings of the interpreter
>> (rxapi client part) is a bit to low .. :-((
>>
>>
>> Bye
>>  Rainer
>>
>> -----------------------------------------------------------------------------
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oor...@li...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>     
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>