Weblogic creates new connection xhen using dataset

Question

Hi,
I use non JTS datasources in order to access to connectionpool. Each
time I request Weblogic, it recreates new connections. Of course quickly
the max connection number allowed is reached!
I used JTS datasources before and all worked fine!
Can someone help me understanding this?
Thx, Piot

Answer 1

ok Thx.
Slava Imeshev wrote:
Hi Piot,
There is a hidden bug in your code. Briefly, when you use
jts, it uses the same connection within the transaction.
So when you use non-jts DS, you always get a new connection
from the DS. Nevertheless, the your code should be adjusted to the
following approach:
1. get a connection from a DS
2. use the connection
3. close result sets
4. close [prepared] statements
5. close the connection
Obviously, your code doesn't follow these guidelines.
Regards,
Slava Imeshev
"Piot" <[email protected]> wrote in message
news:[email protected]...
weblogic.jdbc.connectionPool.pool1=\
url=jdbc:inetora:<ip>:1521:<db1>,\
driver=com.inet.ora.OraDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=1,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshTestMinutes=1,\
testTable=T1,\
props=user=User;password=Password\
I use a class PollAccess managing the connection access and release:
public PoolAccess(String poolName) {
InitialContext initCtx = null;
try {
initCtx = new InitialContext();
dataSource = (javax.sql.DataSource) initCtx.lookup(poolName);
catch (NamingException ne) {
System.out.println(ne.toString());
throw new EJBException(ne);
public Connection getConnection() throws SQLException {
// return connection from the DataSource
return dataSource.getConnection();
public void releaseConnection(Statement st) throws SQLException {
try {
if (st != null) {
st.close();
catch (Exception e) {
System.out.println("Error closing Statement: " + e);
try {
if (this.getConnection() != null) {
this.getConnection().close();
catch (Exception e) {
System.out.println("Error closing Connection: " + e);
when requesting :
Statement st=DatabaseAccess.getConnection().createStatement();
ResultSet rs = st.executeQuery(query.toString().toUpperCase());
while (rs.next()) {
some stuff;
rs.close();
DatabaseAccess.releaseConnection(st);
That's all!
Slava Imeshev wrote:
Could you give us definitions of your pools
and code snippets?
Regards,
Slava Imeshev
"Piot" <[email protected]> wrote in message
news:[email protected]...
1) The pool has 10 connection. I only use one connection...
2) that's exactly what I do. After each request I call close().
What is strange is that when I use the same code with JTS it works
fine...
Slava Imeshev wrote:
Hi,
I see two variants here. First, size of your pool is too small to
serve all requests. Second, you don't release connections
borrowed from the pool. All connections which are not used
should be explicitely returned to the pool by calling close();
"Stéphane Piotrowski" <[email protected]> wrote in message
news:[email protected]...
Hi,
I use non JTS datasources in order to access to connectionpool. Each
time I request Weblogic, it recreates new connections. Of course
quickly
the max connection number allowed is reached!
I used JTS datasources before and all worked fine!
Can someone help me understanding this?
Thx, Piot