On 1/24/06, Vance, Kathy <[EMAIL PROTECTED]> wrote: > You guys have lots of experience on using UniObjects. May I ask "How do > you manage the DB connection with UniObjects? How could I check the > number of DB connections in UniVerse while a web based Java app is > running?"
Guessing that you mean you want to check the number of connections coming *from* the Java app, a connection pool would be appropriate. Even if you never return connections to the pool, you can use the general pattern to limit (and query for) the number of connections. I don't, I just use a Factory (the UniSessionFactory mentioned earlier in the thread) to create connections, and throw them away when I'm done. I had trouble trying to re-use connections early on, and determined that it's fairly cheap to create a new one-- opening files and reading records takes *far* more time. IIRC there is a generic object pool in Jakarta Commons that works, I used it briefly. You won't be able to use any of the existing connection pools because they all expect a JDBC DataSource or something similar. (I occasionally want to write a thin layer around UOJ that makes it look like a JDBC driver... in fact I think someone here might have done it already.) -- Wendy ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
