Logging in seems to establish a DB connection. This connection will be active as long
as there is activity and then for some more time, depending on things like
the settings
in your dsRDBMS service and the # of different users.
If you kill the connection from the DB server side, then ND will not know about this
dead connection. (Works that way for Informix)
When there is a connection loss due to server dropping the connection, ND tries to use
the connection, which happens to be dead and then throws an ugly error. (Again, this
is for Informix).
Some guesswork here:
You seem to have some retry logic in your DBErrorRecoveryPlans, which may be starting
up a new connection to the DB. This may exlain the little delay in getting to
the
DB after killing the connection and retrying login.
Does anyone know of ways of killing database connections from ND with ND knowing that
the connection is dead?
"Isabel Kaluza" <[EMAIL PROTECTED]> wrote:
>
>Hi
>I am using Sybase with ND 4.1.3.8. I see the following scenario.
>I see database users connected in the database even after they are done
>using NetDynamics.
>What I mean is they login to the database and run our ND Project. Run the
>reports they require and logout. On the logout page, I do a
>removeUserSession. When I do an sp_who in the database which shows current
>users connected, I still see the users even though I know they are not using
>ND anymore.
>
>I tried executing kill userid in my logout page. That worked but when
>return to my login page and try to login again as the same or different
>user, for some reason there is a delayed reaction between ND Server and
>Sybase. As anyone seen this scenario?? Does anyone have any suggestions?
>Thanx
>Isabel
>
>
_________________________________________________________________________
To unsubscribe from this mailing list please send an email to:
[EMAIL PROTECTED]
Please remember to use the same email address you subscribed with.
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
