Rev 11552:
* running the "say value()" program will only show an empty value now,
* running "rexx testOORexx.rex -f rxQueue.testGroup" works (all tests pass)
* running "rexx testOORexx.rex -f Macrospace.testGroup -s" or "rexx
testOORexx.rex -f
Macrospace.testGroup -s -S" stops without error and statistics while/after
running the seventh
test "TEST_ADD_THREE_ARGS_OPTION"
o dropping the trailing flags "-s" or "-s -S" yields dots, but it seems
the test runs forever
killing it after approx. three minutes (on Windows test execution takes
not even a second)
---rony
On 02.12.2018 17:53, Rick McGuire wrote:
> 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
> <mailto: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
