Cancel all requests
- Last Updated: February 11, 2026
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
Cancel all requests
The following method raises a STOP condition in the context of each outstanding request on the application server:
Syntax
|
The _cancelAllRequests() method is most useful
for multi-threaded clients.
This method throws a com.progress.open4gl.Open4GLException.
AppObjects, SubAppObjects, and ProcObjects have a _cancelAllRequests() method
that a client can call to do the following:
- Raise the
STOPcondition on a request that was initiated by any object in the proxy and is running (normally during a long execution) - Normal
STOPcondition processing applies, including the ability to trap theSTOPcondition - Close any open ResultSets
When a client invokes a proxy method, the result is a request to the
application server. The request itself can be in one of three states. Also, note that when the
method completes and returns control to the application, the request still can be active if
there is an open output ResultSet (that is, the connection is in a STREAMING state).
The three request states are:
-
QUEUED— The connection is busy with a request from another thread. The current request is queued until the connection becomes available. -
RUNNING— The current request is being run on the connection, and the connection is in theRUNNINGstate. -
STREAMING— The current request is transmitting records over the connection, and the connection is in theSTREAMINGstate.
The _cancelAllRequests() method operates on
a request according to its state, as follows:
-
QUEUED— Cancels the request and throws an exception if theSTOPcondition is not handled. -
RUNNING— Forwards aSTOPrequest to the ABL interpreter on the application server, which handles it according to normal ABLSTOPcondition rules. -
STREAMING— Initiates the close of any currently open output ResultSets, but does not call theclose()method. You must then execute theclose()method on all affected output ResultSets, to complete the closure. For large ResultSets, this is more efficient than using theclose()method alone. For more information on theclose()method, see Pass Temp-tables as SQL ResultSet Parameters.
If there are no requests in the above states when you run _cancelAllRequests(),
the method has no effect.