The JADE 2022 release meets tomorrow’s business demands.
JADECare needs to be able to identify the condition where application processes are closing down as a result of the node receiving a WM_CLOSE or WM_QUIT message. We have multiple server applications running in the server node, one of which is the 'master' or monitoring process. When other processes terminate, the master process generates alerts. These alerts are spurious in the situation where the system/node is being shut down.
One approach to address the problem would be for JADE to cause a 'closing down' event (e.g. on Node) when the node receives the WM_CLOSE or WM_QUIT. This would let our master process know that a shutdown is in progress, and to ignore the OBJECT_DELETED events for other terminating processes on the node.
Martin Jagers
The situation with respect to server finalisation doesn't negate the utility of the functionality when you are simply terminating an app server.
Attachments Open full size
So, we considered this when it was NFS 65315. It has a few issues:
The operating system has told JADE to shut down. As part of that, we shut down all the running applications, including the application that's listening for the notification.
Let's say we sent the notification as part of our shutdown procedure. You'd find we quit before we delivered the notification.
Let's say we hung around for long enough to deliver the notification, how long should JADE wait in order for you to process the notification? (the OS has told us to GO AWAY, in the case of WM_QUIT, "NOW!")
Surely the exit code of the process is more informative? You might look at something like this: https://www.informit.com/articles/article.aspx?p=1564827&seqNum=6
Attachments Open full size