Kbase P23946: Can not unbind a Stateless AppServer after the client side S
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/25/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
Can not unbind a Stateless AppServer after the client side SDO issues a getASHandle function call
RUN unbindServer(?). does not work.
The AppServer is in LOCKED state after running unbindServer()
CAUSE:
RUN unbindServer(INPUT ?) NO-ERROR.
Call requires a handle in which to run unbindServer.
FIX:
Run unbindServer() specifying the handle.
Example:
A simple SDO against the sports2000 database, a simple SmartDataViewer against this SDO, and a navigation panel on a SmartWindow.
Set the instance properties of the SDO to the AppServer partition that was
defined.
"Force to stateful operating mode" should be unchecked, so it should use the operating mode of the AppServer, which should be set to Stateless.
This should be in the initializeObject procedure of the SDO:
PROCEDURE initializeObject:
DEFINE VARIABLE h_ASdttMenu AS HANDLE NO-UNDO.
RUN SUPER.
h_ASdttMenu = DYNAMIC-FUNCTION('getASHandle':U IN h_djp ).
RUN FillMenu IN h_ASdttmenu (
INPUT-OUTPUT TABLE ttMenu,
INPUT-OUTPUT TABLE ttMenuItems,
INPUT CURRENT-LANGUAGE,
INPUT NO).
RUN unbindServer IN h_djp ( INPUT ? ) NO-ERROR.
END PROCEDURE.
With the above code, the server will not stay LOCKED. It goes back to AVAILABLE after each request is completed. And, the client is still connected to the broker.