Kbase P164907: Why is the Appserver connect pid different than the disconnect pid?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/5/2010 |
|
Status: Unverified
GOAL:
Why is the Appserver connect pid different than the disconnect pid?
GOAL:
Why is the Appserver connect process id different than the disconnect process id?
GOAL:
Why is the Appserver connect pid different than disconnect pid when using stateless mode?
GOAL:
Why is the Appserver connect process id different than disconnect process id when using stateless mode?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
In stateless mode, each request is dispatched to the first available agent (with its own process id, or pid). As such, when a client connects, the connect request is processed by the first available agent. The same is true when the client disconnects, the disconnect request goes to the first available agent. There is no guarantee that it will go to the same agent that ran the connect request. In fact, it is unlikely that the request will be processed by the same agent. In stateless mode, the application is responsible for managing user and application context. OpenEdge provides some help such as the SERVER-CONNECTION-ID and SERVER-CONNECTION-CONTEXT attributes, but the application must manage the actual application state.