Great, think this is is a simple as adding a few sleep calls between
connection attempts.
Rick
On Sun, Dec 2, 2018 at 11:41 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
> On 02.12.2018 17:27, Rick McGuire wrote:
>
> Ok, I have a theory that I'd like you to test out. Run this simple
> one-line program after you have killed rxapi, then run it a second time:
>
> say value('RXQUEUESESSION',,'ENVIRONMENT')
>
> I suspect the code gives up trying to connect to the rxapi process before I
> has a chance to get fully. The first connection attempt occurs when it
> creates the session queue and sets the RXSESSIONQUEUE
>
> env variable. If that never happens, then the rxqueue filter will add the
> lines to the wrong session queue.
>
>
> Running the command with "rexx -e say value('RXQUEUESESSION',,
> 'ENVIRONMENT')" first yields an empty string, the second time some value
> (in my case "0x15fa7").
>
> ---rony
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
