><data-source
> name="test1"
> class="com.evermind.sql.DriverManagerDataSource"
> ejb-location="jdbc/OracleDS1"
> pooled-location="jdbc/OraclePooledDS1"
> xa-location="jdbc/xa/OracleXADS1"
> url="jdbc:oracle:thin:@test:1521:pilot"
> connection-driver="oracle.jdbc.driver.OracleDriver"
> username="test"
> password="test"
> max-connections="500"
> />
On a side note... If you are using Oracle 7....
I always try to make sure that the data-source.xml's max-connections and
inactivity-timeout (which is specified in seconds) values match or are less than the
Oracle username's profile definitions of SESSIONS_PER_USER and IDLE_TIME (specified in
minutes), respectively. You should also review all resource limits placed on the
userid - the Oracle limits may need to be changed when running a connection pool vs a
developer's login session vs a "Perl" application vs Oracle forms vs ... Having the
maximum number of concurrent connections set to 500 seems very, very high. In Oracle
7 you can review these settings by issuing the command "select * from
USER_RESOURCE_LIMITS" after you login. Comments from other Oracle users?
