Do you see about a 1-second delay on the first one? The logic of it is the first launch tries to connect to the server, finds it is not able to connect, so it launches rxapi, waits 50msec, then makes 100 attempts to connect with a 10msec delay between each attempt before it gives up. So it appears that there is some delay in the rxapi launch on the Mac that keeps it from coming available in time. By the time the second command is issued, the server is initialized. In face, by the time you make the queued() call, things are up. Unfortunately, the first connection attempt is a critical one because it sets the environment variable that allows the rxqueue filter to put the lines onto the correct session queue.
The logic for implementing the connection is in LocalApiManager::establishServerConnection(). You might try fiddling with the delay both after the server launch and between each of the connection attempts. Rick On Sun, Dec 2, 2018 at 4:14 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > It still fails > > to keep it short … > > No need to bother the oorexx test suite > > > [enrico@enrico-imac ooRexx.testsuite]$pkill rxapi > [enrico@enrico-imac ooRexx.testsuite]$rexx -e "'pwd | rxqueue' ; say > queued(); do queued();parse pull l; say l; end " > 0 > [enrico@enrico-imac ooRexx.testsuite]$rexx -e "'pwd | rxqueue' ; say > queued(); do queued();parse pull l; say l; end " > 1 > /opt/ooRexx.testsuite > [enrico@enrico-imac ooRexx.testsuite]$ > > > > Not easy to debug without knowing the logic behind it > > E > > _______________________________________________ > 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
