Queue Thread Display,
com.tymeac.client.jframe.TyQueThd
This frame class displays the status of a Queue's Threads.
The non-frame version of this class is TyQueThdClient, below.
(click to link to full image)
Elements
Queue Name -- Enter the name of the Tymeac Queue.
List -- This is a List of the Queue's Threads containing:
Id - A number beginning at zero. This Id is also found suffixed to the Thread Name, TyQueMaint, and in the statistics for the Queue
(#_Proc'd) - The total number of requests processed.
Status - The status of the Thread: (See also the full life cycle of a thread.)
Never used -- Never activated.
/ existent -- There is a physical java thread attached.
/ null -- There is no physical java thread. Tymeac must instantiate
a new thread when necessary.Inactive -- The Thread was active at one time, but no longer selectable.
/ existent -- There is a physical java thread attached.
/ null -- There is no physical java thread. Tymeac must instantiate
a new thread when necessary.Waiting for work -- The Thread is waiting for work and is selectable.
Thread processing -- The Thread is executing code outside the application. For instance, fetching a request from a Wait List, preparing to invoke the application method or processing the output from the application.
In application class -- The execution is within the invoked application.
Scheduling Output Agent -- This is an Asynchronous Request. The Function has an Output Agent Queue. The last Queue Thread finished processing and is now scheduling the Output Agent Queue.
Notified, awaiting execution -- The status was Waiting for work , above. A request found this Thread, 'notified' it, but execution has not begun. This is a small window.
Reactivated, awaiting execution -- The status was Inactive, above. A Threshold was exceeded or a Wait List overflow occurred, TyQueMaint. The Thread was awakened (when necessary, a new instance acquired) but execution has not begun. This is a small window.
Cancelled -- The Tymeac Monitor determined that the Thread exceeded a prudent time limit. This status has no effect on an executing Thread. When processing is just slow, the Thread changes its own status for each event in its life. This status effects scheduling.
See also scheduling failures.
A Thread of this status cannot participate in scheduling. The How a Thread becomes disabled document details the time limits.Disabled -- See How a Thread becomes disabled.
Buttons
REFRESH -- Refreshes the display.
DISABLE SELECTED -- Select a Thread. This button:
- Informs the Thread to stop processing and terminate (issue a return in the run() method.)
- Changes the status to 'disabled'. However, this is only a logical disable.
If the Thread is "hanging", then this has no effect on the executing Thread. In order to kill a Thread, see how a Thread is named in TyQueMaint, and use a Java tool.
Three circumstances require disabling a Thread:
During shut down, when a Thread finishes processing all pending requests, it sets its status to "Disabled". Shut down cannot complete (writing statistics, etc.) until all Threads finish. Manually disabling a Thread lets shut down complete.
When a new instance of a Thread is necessary. Application processing determines this situation. See the"Enable All" button, below.
When an application class was faulty, was repaired and renamed, and, a new copy obtained (TyNewCopy). Now, when the actual status of Threads is in doubt, purge all the Threads (with a java tool if necessary) disable all Threads (here) then use the "Enable All" button, below.
Note: As above, this is a logical disable. If the thread is scheduling an Output Agent Queue or executing within a Processing Application Class, it may change its status at any time. Use the Refresh button for the latest status of all threads. When the thread finishes with a request, it then checks for a "stop processing" request.
ENABLE ALL -- All 'disabled' Threads are set to 'Inactive'.
When a Thread instance is null (meaning the Thread does not exist) this button instantiates a new Thread.
When all the Threads were 'disabled' and Asynchronous Requests are pending , one Thread is 'activated' so that any Asynchronous Requests may continue.
Message Block at bottom : -- This is an information message:
Connection failure -- The RMI connection failed or the Tymeac Server returned an invalid message.
Selected Thread Invalid -- Cannot disable a disabled Thread.
Use Refresh First -- Cannot Enable until the list is displayed.
Queue name invalid -- As indicated.
OK -- All Threads were Enabled.
com.tymeac.client.Class TyQueThdClient
This is the Non-GUI equivalent of the GUI Class, above. An example of how to use this class is: com.tymeac.demo.TyDemoClient_NonGui.java in the <TymeacHome>source/com/tymeac/demo directory.
Constructor 1 -- has no arguments. This is for the RMI Server. The constructor gets a new instance of a Tymeac internal class that is similar to TySvrComm
Constructor 2-- is for the internal server. The single argument is the Tymeac Server Interface, TymeacInterface.
Instance Methods --
public int disable(String que, int nbr) {
Returns:
3 Connection failure
0 Invalid queue name
1 selected thread invalid
4 OKParameters: the queue name, the thread number.
public int enable(String que) {
Returns:
1 Connection failure
3 Invalid queue name
0 OKParameters: the queue name.
public String[] refresh(String que) {
Returns:
0 Connection failure
2 Invalid queue name
3 OKParameters: the queue name