OS: Ubuntu 14.04.2 LTS
Oracle: 12.1.0.1.0 or 11.2.0.3.0
Tomcat: 7.0.52-1ubuntu0.1
odjbc: Ojdbc6 or Ojdbc7 (placed in /var/lib/tomcat7/lib)
java version "1.8.0_31" of "1.7.0_65"
Context.xml:
<Resource name="*********1" auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@//*********:1521/********"
minIdle="1"
username="*******" password="*******" maxActive="10"
maxIdle="10" maxWait="-1" />
<Resource name="******2" auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@//*******:1521/**********"
username="*******" password="**********" maxActive="20"
maxIdle="10" maxWait="-1" />
Immediately after tomcat startup, number of connection goes up until it
reaches below:
SQL> select machine, username, count (1) from v$session group by
machine, username;
MACHINE USERNAME COUNT(1)
--------- --------------------- ----------
tc ******1 40
tc ******2 60
Then, after a while connection count drops to:
MACHINE USERNAME COUNT(1)
--------- --------------------- ----------
tc ******1 6
tc ******2 60
I have commented all other pools, most fail due to lack of resources on
database side (hundreeds of connections). Connection are opened if pool
is defined in context.xml, even if actually not used anywhere.
Catalina.out gives me nothing for two pools, bunch of errors with 3 or
more, but those seem to be due to exhaustion of databases availability.
Looked up oracle support, nothing of use there. All of this works fine
with tomcat6, java6, oracle 11g or 12c
Red
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
