Hi Michael, On 17.08.2025 03:47, Michael Lueck wrote:
W O W ! ! ! Bravo!!! A most impressive success milestone!
but not solved yet. It looks as it is somehow linked to terminating interpreter instances right before the callback from Java into ooRexx. The change I made was a debug output statement from the Java garbage collector run (collecting the peer Java RexxEngines) right before the ooRexx instance gets terminated from the Java side, as if this little time span makes the difference (at least on my machine) and allows the Java callback into ooRexx to not block.
---rony _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
