[Oorexx-devel] rxapi daemon / kill -TERM not always working

2009-06-04 Thread Rainer Tammer
Hello, if I did not miss something there is no explicit signal handler for SIGTERM in the API daemon. Sometimes a simple kill does not terminate the daemon. Would it be a problem if I add a signal handler for SIGTERM ? My idea is to add an handler which calls apiServer.terminateServer(); ... Is

Re: [Oorexx-devel] rxapi daemon / kill -TERM not always working

2009-06-04 Thread Rick McGuire
I can't think of any reason why it would be a bad idea, though at this point, it should only be developed on trunk for a future release and not applied to the 4.0 branch. Rick On Thu, Jun 4, 2009 at 2:35 AM, Rainer Tammer tam...@tammer.net wrote: Hello, if I did not miss something there is no

Re: [Oorexx-devel] rxapi daemon / kill -TERM not always working

2009-06-04 Thread Rainer Tammer
Hello, Rick McGuire wrote: I can't think of any reason why it would be a bad idea, though at this point, it should only be developed on trunk for a future release and not applied to the 4.0 branch. thats fine with me. In this step I will also add some code for AIX to enable the rxapi

Re: [Oorexx-devel] rxapi daemon / kill -TERM not always working / HEAD

2009-06-04 Thread Rainer Tammer
Hello, this is my first attempt to add: - handler for SIGTERM - make rxapi capable of working with the AIX subsystem resource controller (SRC) I had added some debugging output to the Stop() routine during my tests. The apiServer.terminateServer() gets called and then exit(1) gets called. So it

[Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rony G. Flatscher
Having proceeded to a point in which I am confident that dispatching Rexx intepreter instances on separate Java threads is stable, I turned back to a use case from a BSF4Rexx user who tries to halt Rexx threads from Java. In the 4.0 API version the Halt() API of the interpreter instance is used

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rick McGuire
Halt() does not use any signalling mechanisms. It only iterates through the threads associated with each instance and sets a flag indicating that a halt condition needs to be raised. That flag is detected at instruction boundaries and the condition gets raised. That's all that this does. Rick

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rony G. Flatscher
Rick McGuire wrote: Halt() does not use any signalling mechanisms. It only iterates through the threads associated with each instance and sets a flag indicating that a halt condition needs to be raised. That flag is detected at instruction boundaries and the condition gets raised. That's

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rick McGuire
I did spot a resource locking problem in the Halt() API that could create a race condition that might result in a memory overlay. I've fixed that, but there really is not much else involved with that API. Rick On Thu, Jun 4, 2009 at 5:34 PM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: