When a client disconnects from an Adaptive Server, the state of the connection is evaluated to determine whether to cache the connection. OpenSwitch does not cache these connections:
Connections with an open transaction
Connections not established due to login failure
Connections with Open Client-side cursors
Connections where the maximum number of cache threads is reached, as specified by CACHE_THREAD option in the [CONFIG] section of the OpenSwitch configuration file
In all of these states, restoring the connection to a user would place the user’s application in an uncertain state. To avoid this risk, OpenSwitch discards these connections when the client exits.
Because a cached connection never disconnects from the remote server, any state information held in that server regarding the user’s session is maintained between the time the user disconnects from OpenSwitch and reconnects to the cached connection.
This mean that temporary tables and “SET” options (except for “set database,” which is cleared) are maintained even after a user disconnects. Evaluate carefully how you use connection caching.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
