Here's my understanding of this:
I'm not sure what you mean by threads, but I'll assume you mean
connections to the db. ND opens db connections as it needs them (Sybase,
Oracle, whatever), up to your configured max per db. If your RDBMS
config looks like:
Max db connections per process - 4
Max db connections per DB - 4
Max records to retrieve - 5000
# of worker processes - 20
Max #of clients per worker - 7
Then the max number of connections that might be opened to the db would
be 20X4= 80. These connections, once opened, remain open "forever
after". ND keeps them open so as to be able to reuse them without the
overhead of opening them again. The only time it might close one down is
if the app uses two (or more ) databases (or two different user/password
pairs) and it needs to close a connection to one db so that it can open
a connection to another.
This is a "problem" or a "feature", depending on your point of view. If
your app is busy most of the time then it is a feature, since db access
is always fast. If your app has slack periods then it is a "problem"
since those db connections just hang around.
There is no ND feature that I know of which tells the app server to drop
unused db connections.
Ron Schiller wrote:
>
> Our DBA's are complaining that ND 4.0 ties up too many threads to their Sybase
> tables. Is there some code we should be including in our applications that clears
> out the threads when the user exits (presses an exit button as opposed to the
> browser 'back' button)? Or is this strictly a middleware problem they will have to
> pursue?
>
> Will we be looking at the same problem when we move some of these apps to
> Oracle?
>
> Thanks.
_________________________________________________________________________
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]
