|
On 03/25/2002 at 02:01:12 PM, java400-l-admin@midrange.com wrote: Do you know of a way to incorporate datasource connection pooling with JNDI or something similar. What I'm interested is something that always running and can give out connections to the database through the JNDI look-up. --- end of excerpt --- You can put the DataSource in JNDI so that the connection can be reconstructed, but you can't put a Connection there. A Connection is a live job scoped resource, and if you could put it in JNDI, it would be just as expensive to retrieve from JNDI as the connect was in the first place. In the grand scheme of application startup/initialization, adding a new connection to that is probably not that significant is it? You might equally well off trying first, to figure out how to prevent your applications from ending/starting repeatedly (i.e. so they can be 'hot') before doing the same to the conneciton. In every single ethnic, religious or racial group, there are a very few truly evil people. For each of those people there are many, many, many good people. Assuming anything (evilness or capability for evil) about the particular group is bigotry and idiocy. Don't do it. -- Me Fred A. Kulack - IBM eServer iSeries - Java DB2 access, Jdbc, JTA, etc... IBM in Rochester, MN (Phone: 507.253.5982 T/L 553-5982) mailto:kulack@us.ibm.com Personal: mailto:kulack@magnaspeed.net AOL Instant Messenger: Home:FKulack Work:FKulackWrk
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.