Ben Ricker wrote: > Running against a database? Are you pooling the connections? We hit > maxthreads when either the DB is messed up (i.e., someone locks a table) > or before, when the programmers forgot to run socket_close() on the DB > connection, thereby returning it to the pool.
Why, yes I am going against a database - we could never get Tomcat connection pooling working right with it, so we went with just internal (Ingres db) connection pooling. I don't know a whole lot about that, as that's not the primary app I work on - it's kind of been just "there", if you know what I mean, but now that you mention it, I think someone might be able to lock a table - I'll have to look into that. Forgive me for showing my ignorance, but is socket_close() a Java routine? I don't think I've seen that before - we probably call it something different. Is it anything like invalidating a session? -- Lynn Hollerman. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
