Skip navigation.

WebLogic Server Configuration Reference

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

JDBCDataSource

 


Description

This MBean defines a non-transactional JDBC DataSource.

 


Syntax

<JDBCDataSource
ConnectionWaitPeriod="number of seconds"
DeploymentOrder="number"
JNDIName="String"
Name="String"
Notes="String"
PoolName="String"
RowPrefetchEnabled=( "true" | "false" )
RowPrefetchSize="number"
StreamChunkSize="number of bytes"
Targets="list of Target names"
WaitForConnectionEnabled=( "true" | "false" )
/>

 


Parent Elements

 


Attributes

Table 21-1 JDBCDataSource attributes

Attribute

Description

Range of Values and Default

ConnectionWaitPeriod

Deprecated. The time in seconds which the system will wait for a free connection pool entry to become available if a request is received when there are no free entries in the pool. This value will be used only if setWaitForConnectionEnabled(true) has previously been called. A WLS server thread is occupied while waiting for a free connection, and this can result in a decrease in system throughput. Therefore, the recommended way to deal with the exhaustion of a connection pool is to increase the size of the pool, and this method is not recommended for use in a production environment!

Units: seconds

Default: 1

Minimum: 1

Maximum: 60

DeploymentOrder

A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.

Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.

Default: 1000

Minimum: 0

Maximum: 231-1

JNDIName

The JNDI path to where this DataSource is bound.

Applications that look up the JNDI path will get a javax.sql.DataSource instance that corresponds to this DataSource.

Admin Console field label: JNDI Name

Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.

Admin Console field label: Name

Required: no

Notes

Optional information that you can include to describe this configuration.

Admin Console field label: Notes

Required: no

PoolName

The name of the connection pool with which the DataSource is associated.

Calls from applications to getConnection() on this DataSource will return a connection from the associated connection pool.

Admin Console field label: Pool Name

Required: no

RowPrefetchEnabled

Controls row prefetching between a client and WebLogic Server for each ResultSet. When an external client accesses a database using JDBC through Weblogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access. WebLogic Server will ignore this setting and not use row prefetching when the client and WebLogic Server are in the same JVM.

Admin Console field label: Row Prefetch Enabled

Default: false

RowPrefetchSize

The number of result set rows to prefetch for a client. The optimal value depends on the particulars of the query. In general, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations.

Admin Console field label: Row Prefetch Size

Default: 48

Minimum: 2

Maximum: 65536

StreamChunkSize

Data chunk size for steaming datatypes. Streaming datatypes (for example resulting from a call to getBinaryStream()) will be pulled in StreamChunkSize sized chunks from WebLogic Server to the client as needed.

Admin Console field label: Stream Chunk Size

Units: bytes

Default: 256

Minimum: 1

Maximum: 65536

Targets

The targets in the current domain on which this item can be deployed.

Admin Console field label: Targets

Required: no

WaitForConnectionEnabled

Deprecated. Returns true if the system will wait for a free connection pool entry to become available when a request is made with all pool entries in use. In order to avoid tying up server threads and possibly hurting performance, it is recommended that this feature not be used.

Default: false

 

Skip navigation bar  Back to Top Previous Next