tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Jonathan Pierce)
Subject Re:Tomcat 4 JDBCRealm Connection Pooling
Date Wed, 13 Feb 2002 17:02:16 GMT

It would be nice to reference the JDBC data source rather than configuring the
realm seperately. The problem I see is that the Realm is global in server.xml
and the data sources are specific to individual contexts. Should the realm be
moved into the context so that different contexts could be configured with
different realms?


____________________Reply Separator____________________
Subject:    Tomcat 4 JDBCRealm Connection Pooling
Author: "Tomcat Developers List" <>
Date:       2/13/2002 10:25 AM

Currently the JDBCRealm does not use db Connection Pooling, instead
it maintains an open connection and synchronizes use of the connection.

I have been using the new Tomcat 4.1-dev DBCP for creating
a JNDI named JDBC DataSource and it has been working well.

The easiest way to implement db connection pooling may be by 
providing a JDBC Realm which uses a JNDI named JDBC DataSource.

Should this support be added to the current JDBCRealm, or should a new
realm be created which uses a JNDI named JDBC DataSource?



Glenn Nielsen    | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

This email and any files transmitted with it are for the named person's use
only.  It may contain confidential, proprietary or legally privileged
information.  No confidentiality or privilege is waived or lost by any
mistransmission.  If you receive this message in error, please immediately
delete it and all copies of it from your system, destroy any hard copies
of it and notify the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.

This email message has been swept by a virus software product for the
presence of computer viruses.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message