Chapter 13: JDBC Connectivity Attribute(s) Description auth type= javax.sql.DataSource

Chapter 13: JDBC Connectivity Attribute(s) Description auth type= javax.sql.DataSource maxActive maxIdle maxWait username= empro password= empass driverClassName= com.mysql .jdbc,Driver url= jdbc:mysql://localhost… Specifies if the Tomcat Container does the authentication on behalf of the application (auth= Container ) or if the application does it programmatically (auth= Application ). The type of resource that will be returned during this lookup is a javax.sql.DataSource. It also specifies that the container should authenticate against the RDBMS on behalf of the Web application. Maximum number of active connections in the connection pool. A 0 value indicates unlimited. Number of idle connections in pool before they are evicted. A -1 value indicates unlimited. Maximum number of milliseconds that the manager will wait for a database connection to respond, before throwing an exception. A -1 value indicates waiting indefinitely. The parameters for the MySQL Connector/J driver, including usernameand password. The driverClassName attribute tells Tomcat/DBCP the class to load as the JDBC driver. The URL is the MySQL-specific JDBC URL to access the database server instance. You may want to check Chapter 6 for a detailed examination of the attributes allowed in the element. Working with Other RDBMS s Tomcat s default DBCP factory will work with JDBC drivers for any RDBMSs. For example, here is the setting for accessing an Oracle database: DBCP Jakarta Commons Pooling Support To return a JDBC data source to the application, Tomcat 6 uses a data source factory to create the data source. Tomcat 6 uses the Jakarta Commons DBCP (by default) to supply a data source factory and implement connection pooling.

For high quality website hosting services please check java web hosting website.

Comments are closed.