Problems in starting up Connection Pools in SQLServer7

Hi
We are running both Commerce and Personlaization Server 3.5 with an SQL erver
7 backend. I recently migrated the database from Cloudscape to SQL Server and
added the following entry into my weblogicCommerce.properties file

# ---------------SQL Server ----------------------#
commerce.usermgmt.RDBMSRealm.driver=weblogic.jdbc.mssqlserver4.Driver
commerce.usermgmt.RDBMSRealm.dbUrl=jdbc:weblogic:mssqlserver4:wlcsDatabase@WEBLOGICSRVR01:1433
commerce.usermgmt.RDBMSRealm.dbUser=sa
commerce.usermgmt.RDBMSRealm.dbPassword=mcpassword

After doing this, the commercePool (Connection Pool) that comes with the installation
of the Commerce server did not work and came up with some java exceptions i.e.

Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Can't open a socket on none:1433. Check host and port num
ber and make sure the security manager allows this connection. You can also try
running the SocketApplet (java.net.UnknownHostException: none).
at weblogic.jdbcbase.mssqlserver4.BaseConnection.prepareConnection(BaseC
onnection.java:176)
at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:32)
Can any one give me an idea on what I need to do to resolve this problem?
Thanx

hii..did u change the startup and bea/wlcs/bin/win32/set-environment.cmd
files where u need to change the classpath related with SQL Server.After
that you will have to change JDBC setting thru console using
http://ip:7501/console/index.jsp
Do that and hope it will work.
Rajesh
"Bola Taylor" <[email protected]> wrote in message
news:3b724a71$[email protected]..
>
Hi
We are running both Commerce and Personlaization Server 3.5 with an SQLerver
7 backend. I recently migrated the database from Cloudscape to SQL Serverand
added the following entry into my weblogicCommerce.properties file

# ---------------SQL Server ----------------------#
commerce.usermgmt.RDBMSRealm.driver=weblogic.jdbc.mssqlserver4.Driver
commerce.usermgmt.RDBMSRealm.dbUrl=jdbc:weblogic:mssqlserver4:wlcsDatabase@W
EBLOGICSRVR01:1433
commerce.usermgmt.RDBMSRealm.dbUser=sa
commerce.usermgmt.RDBMSRealm.dbPassword=mcpassword

After doing this, the commercePool (Connection Pool) that comes with theinstallation
of the Commerce server did not work and came up with some java exceptionsi.e.
>

Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Can't open a socket on none:1433. Check host andport num
ber and make sure the security manager allows this connection. You canalso try
running the SocketApplet (java.net.UnknownHostException: none).
atweblogic.jdbcbase.mssqlserver4.BaseConnection.prepareConnection(BaseC
onnection.java:176)
atweblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:32)
>
>
Can any one give me an idea on what I need to do to resolve this problem?
Thanx

Similar Messages

A very surprise problem about JDBC and connection pool

I occur a very problem about JDBC and connection pool on Weblogic Platform
8.1.
There is a table in Oracle
Table
Name: t1
id varchar2(5);
content clob;
id is primary key.
If I use a connection pool to connect to Oracle,like following program:
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("cgOracleDataSource");
con = ds.getConnection();
then following program will throw a ClassCastException
String sql = "select content from t1 where id = ?";
PreparedStatement pst = con.prepareStatement(sql);
pst.setString(1,"001");
oracle.sql.CLOB clob = (oralce.sql.CLOB)rs.getClob("content") //this
statement will throw ClassCastException
but if I use JNDI to connect to Oracle,like following program, then those
program above is ok
private String dbdriver="oracle.jdbc.driver.OracleDriver";
private String dburl="jdbc:oracle:thin:@192.168.7.148:1521:ep";
private String username="ep";
private String password="epuser";
Class.forName(dbdriver);
conn = DriverManager.getConnection(dburl, username, password);
conn.setAutoCommit(false);
On the contrary, if I use JNDI to connect to Oracle, following program will
throw ClassCastException
weblogic.jdbc.vendor.oracle.OracleThinClob clob =
(weblogic.jdbc.vendor.oracle.OracleThinClob)rs.getClob("content");
but it is fine if I use connection pool to connect to Oracle.
I am confused this problem, who can tell me why?
Daniel

When you are getting connection using datasource lookup from weblogic
connection pool, this connection is internally wrapped and hence you have to
cast it to weblogic.jdbc.vendor.oracle.OracleThinClob which you do and so it
works.
But when you get connection by loading driver straight, you are getting naked
oracle connection. In this case when you cast it to oracle.sql.Clob it works,
as you have seen in your test case.
I hope this explains what is going on with your code.
Thanks,
Mitesh
Daniel wrote:
I occur a very problem about JDBC and connection pool on Weblogic Platform
8.1.
There is a table in Oracle
Table
Name: t1
id varchar2(5);
content clob;
id is primary key.
If I use a connection pool to connect to Oracle,like following program:
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("cgOracleDataSource");
con = ds.getConnection();
then following program will throw a ClassCastException
String sql = "select content from t1 where id = ?";
PreparedStatement pst = con.prepareStatement(sql);
pst.setString(1,"001");
oracle.sql.CLOB clob = (oralce.sql.CLOB)rs.getClob("content") //this
statement will throw ClassCastException
but if I use JNDI to connect to Oracle,like following program, then those
program above is ok
private String dbdriver="oracle.jdbc.driver.OracleDriver";
private String dburl="jdbc:oracle:thin:@192.168.7.148:1521:ep";
private String username="ep";
private String password="epuser";
Class.forName(dbdriver);
conn = DriverManager.getConnection(dburl, username, password);
conn.setAutoCommit(false);
On the contrary, if I use JNDI to connect to Oracle, following program will
throw ClassCastException
weblogic.jdbc.vendor.oracle.OracleThinClob clob =
(weblogic.jdbc.vendor.oracle.OracleThinClob)rs.getClob("content");
but it is fine if I use connection pool to connect to Oracle.
I am confused this problem, who can tell me why?
Daniel

A strang problem about Resin database connection pool

I am a beginner，hope somebody can help me.
my web site occured a strange problem after I used the Resin database connection pool instead of
connecting directly
the error message as follows:java.lang.IllegalArgumentException: Request cannot be null
at javax.servlet.ServletRequestWrapper.<init>(ServletRequestWrapper.java:100)
at javax.servlet.http.HttpServletRequestWrapper.<init>(HttpServletRequestWrapper.java:92)
at com.caucho.server.connection.RequestAdapter.<init>(RequestAdapter.java:96)
at com.caucho.server.webapp.DispatchRequest.<init>(DispatchRequest.java:97)
at com.caucho.server.webapp.IncludeDispatchRequest.<init>(IncludeDispatchRequest.java:77)
at com.caucho.server.webapp.IncludeDispatchRequest.createDispatch(IncludeDispatchRequest.java:87)
at com.caucho.server.webapp.RequestDispatcherImpl.include(RequestDispatcherImpl.java:389)
at com.caucho.server.webapp.RequestDispatcherImpl.include(RequestDispatcherImpl.java:345)
at com.caucho.jsp.PageContextImpl.include(PageContextImpl.java:807)
at _jsp._intro__jsp._jspService(/intro.jsp:60)
at com.caucho.jsp.JavaPage.service(JavaPage.java:75)
at com.caucho.jsp.Page.pageservice(Page.java:571)
at com.caucho.server.dispatch.PageFilterChain.doFilter(PageFilterChain.java:155)
at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:211)
at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:177)
at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:221)
at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:263)
at com.caucho.server.port.TcpConnection.run(TcpConnection.java:331)
at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:464)
at com.caucho.util.ThreadPool.run(ThreadPool.java:408)
at java.lang.Thread.run(Thread.java:595)


<resin xmlns="http://caucho.com/ns/resin"
xmlns:resin="http://caucho.com/ns/resin/core">

<log name='' level='info' path='stdout:' timestamp='[%H:%M:%S.%s] '/>
<log name='com.caucho.java' level='config' path='stdout:'
timestamp='[%H:%M:%S.%s] '/>
<log name='com.caucho.loader' level='config' path='stdout:'
timestamp='[%H:%M:%S.%s] '/>

<dependency-check-interval>2s</dependency-check-interval>

<javac compiler="internal" args=""/>



<thread-pool>

<thread-max>128</thread-max>

<spare-thread-min>25</spare-thread-min>
</thread-pool>

<min-free-memory>1M</min-free-memory>
<server>

<class-loader>
<tree-loader path="$resin-home/lib"/>
</class-loader>

<keepalive-max>500</keepalive-max>
<keepalive-timeout>120s</keepalive-timeout>

<http server-id="" host="*" port="8080"/>


<cluster>
<srun server-id="" host="127.0.0.1" port="6802" index="1"/>
</cluster>

<ignore-client-disconnect>true</ignore-client-disconnect>

<cache path="cache" memory-size="10M"/>

<ping>

</ping>

<web-app-default>

<cache-mapping url-pattern="/" expires="5s"/>
<cache-mapping url-pattern="*.gif" expires="60s"/>
<cache-mapping url-pattern="*.jpg" expires="60s"/>

<servlet servlet-name="directory"
servlet-class="com.caucho.servlets.DirectoryServlet"/>
</web-app-default>

<database>
<jndi-name>jdbc/artunion</jndi-name>
<driver type="org.gjt.mm.mysql.Driver">
<url>jdbc:mysql://localhost:3306/union</url>
<user>as</user>
<password>as</password>
</driver>
<prepared-statement-cache-size>8</prepared-statement-cache-size>
<max-connections>20</max-connections>
<max-idle-time>30s</max-idle-time>
</database>

<host-default>
<class-loader>
<compiling-loader path='webapps/WEB-INF/classes'/>
<library-loader path='webapps/WEB-INF/lib'/>
</class-loader>

<access-log path='logs/access.log'
format='%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i"'
rollover-period='1W'/>

<web-app-deploy path='webapps'/>

<ear-deploy path='deploy'>
<ear-default>

</ear-default>
</ear-deploy>

<resource-deploy path='deploy'/>

<web-app-deploy path='deploy'/>
</host-default>

<resin:import path="${resinHome}/conf/app-default.xml"/>

<host id=''>
<document-directory>D:/artunion</document-directory>

<web-app id='/'>

<class-loader>
<simple-loader path="$host-root/xsl"/>
</class-loader>
<servlet-mapping url-pattern="/servlet/*" servlet-name="invoker"/>
</web-app>
</host>
</server>
</resin>
Thank you!

ResultSet problem with a jdbc connection pool implementation

Hi
I'm trying to use jdbc connection pool in my java application (js2e 1.4.0_01)
from the example at http://www.developer.com/tech/article.php/626141
In my main() code, in addition to JDBCConnection, JDBCConnectionImpl and JDBCPool classes, i use
JDBCConnection conn;
conn = new JDBCConnection(dbName);
// make a statement
sqlString = "SELECT........."
ResultSet rs = null;
rs = conn.sendRequest(sqlString, rs);
// print result
while (rs.next()) {
Unfortunately i get an error like "ResultSet is closed" in the line corresponding to rs.next. The error disappears if i remove the line
stmt.close();
in the method sendRequest of the JDBCConnectionImpl class.
1) Does anybody knows the solution?
2) How to close all connections?
Thanks you in advance.

Hi ,
You are closing the statement and then trying to use resultset , which is not going to work .So close then statment after using resultset .Ideally the code should be like this
try {
conn = // get the connection
pstmt = conn.prepareStatement(sql);
rs = pstmt.executeQuery();
while ( rs.next()){
// do something
catch (Exception ex) {
finally {
try {
if (rs != null)
rs.close();
if (pstmt != null)
pstmt.close();
if(conn!=null )
conn.close();

Connection pooling - where to start

I'm starting to learn about connection pooling but I am unsure of how it can be used to in the web server environment. Are connection pools just static classes placed in a global environment for all webapps to use? What is the best approach for creating these pools. How would an app access this class? Thanks!

Where to start with connection pooling?
The shallow end, of course. And don't go in within 30 minutes of eating.
The best approach is to let your app server handle it for your. Tomcat does; so does WebLogic and every other J2EE-compliant container.
When the container handles it, classes will do a JNDI lookup of the connection and go from there.
Check out the docs for details on how to set it up.

JDBC connection pool failures when used by JMS stores

 We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
 a JMS Store.
 <JDBCConnectionPool Name="sybaseJMSPool"
 Targets="cluster00"
 InitialCapacity="2"
 MaxCapacity="10"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;charset=utf8"
 URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
 (note that the @xxx@ string are replaced by actual values).
 We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
 We deployed this configuration on a number of environments (testing, staging,
 ..). The actual hardware and network configuration is different for the different
 system, but the WebLogic domain stays the same regarding this issue.
 On the test system we frequently get the following exceptions:
 <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
 <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
 <JMSServer "JMSServer00", store failure while writing message for topic
 OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
 <sybaseJMSPool>, prefix = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 .>
 java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
 = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 at weblogic.jms.store.JDBCIOStream.throwIOException
 (JDBCIOStream.java:1213)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 Before that this message appeared:
 <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
 <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
 <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
 received a message over an uninitialized connection: 'JVMMessage from: 'null'
 to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
 1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
 invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
 offset: '34'''>
 This problem did not occur on another system which was used during a 2 day stress
 testing session.
 It seems that the problem occurs after a period in which no user request where
 made. The user requests trigger EJB's that start sending JMS messages.
 When the problem occurs, the JMS messaging systems seems to lock up as no messages
 are received anymore by the different listeners (MDBs).
 Undeploying and redeploying the JBDC connection pool solves the problem. This
 solution is unacceptable in case of a production system.
 A similarly defined connection pool, which is used by the EJBs to make database
 connection, does not manifest this problem.
 <JDBCConnectionPool Name="sybasePool"
 Targets="cluster00"
 InitialCapacity="10"
 CapacityIncrement="5"
 MaxCapacity="50"
 PreparedStatementCacheSize="150"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
 URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
 The JDBC connection pool is used as follows by the JDBC store
 <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
 <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
 <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
 <JMSTopic JNDIName="ADIS.Status"
 Name="StatusTopic" RedeliveryDelayOverride="300000"/>
 <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
 Name="OrderChangeTopic" RedeliveryLimit="3"/>
 </JMSServer>
 Turning on the "Test Reserved Connection" with a appropriate test table does not
 help.
 Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
 can be related to network problems. Nevertheless the connection pool should be
 able to cope with this.
 Can you provide any solution for this ? Or give us hints what can cause the problem


Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe

Connection pool for big web application

hi,
i am developing an application which had more then 20 classes and each class use databases.
i made an connection bean and use it for database connectivity but as my code expand and my application run for longer time i start getting error of connection limit.
then i start using connection pool. in this i start using one connection for whole application.
now i want that my
1-whole application use that connection pool and i dont need to initialize it in different classes.
2- The main problem is that may at a time i have to connect database with different user and these connections should remain active.
my application will be used for enterprise level and remain active for months .
following is my connection pool
public class ConnectionPool implements Runnable
 private Log log=new Log();
 private String driver, url, username, password;
 private int maxConnections;
 private boolean waitIfBusy;
 private Vector availableConnections, busyConnections;
 private boolean connectionPending = false;
 public ConnectionPool(String driver, String url,String username, String password,int initialConnections, int maxConnections, boolean waitIfBusy)
 this.driver = driver;
 this.url = url;
 this.username = username;
 this.password = password;
 this.maxConnections = maxConnections;
 this.waitIfBusy = waitIfBusy;
 if (initialConnections > maxConnections)
 initialConnections = maxConnections;
 availableConnections = new Vector(initialConnections);
 busyConnections = new Vector();
 try
 for(int i=0; i<initialConnections; i++)
 availableConnections.addElement(makeNewConnection());
 catch(Exception e)
 log.write(e.getMessage());
 }//EO constructor
public synchronized Connection getConnection()
 if (!availableConnections.isEmpty())
 log.write("Total connections="+availableConnections.size());
 Connection existingConnection = (Connection)availableConnections.lastElement();
 int lastIndex = availableConnections.size() - 1;
 availableConnections.removeElementAt(lastIndex);
 // If connection on available list is closed (e.g.,it timed out), then remove it from available list
 // and repeat the process of obtaining a connection. Also wake up threads that were waiting for a connection because maxConnection limit was reached.
 try
 if (existingConnection.isClosed())
 notifyAll(); // Freed up a spot for anybody waiting
 return(getConnection());
 else
 log.write( "in available connection" );
 busyConnections.addElement(existingConnection);
 return(existingConnection);
 catch(SQLException se)
 log.write(se.getMessage());
 } else {
 // Three possible cases:
 // 1) You haven't reached maxConnections limit. So establish one in the background if there isn't
 // already one pending, then wait for the next available connection (whether or not it was the newly established one).
 // 2) You reached maxConnections limit and waitIfBusy flag is false. Throw SQLException in such a case.
 // 3) You reached maxConnections limit and waitIfBusy flag is true. Then do the same thing as in second
 // part of step 1: wait for next available connection.
 if ((totalConnections() < maxConnections) && !connectionPending)
 makeBackgroundConnection();
 else if (!waitIfBusy)
 log.write("Connection limit reached");
 // Wait for either a new connection to be established (if you called makeBackgroundConnection) or for
 // an existing connection to be freed up.
 try {
 wait();
 catch(InterruptedException ie)
 log.write(ie.getMessage());
 // Someone freed up a connection, so try again.
 return(getConnection());
 }//EO main if-else
 return null;
}//EO getconnection method
// You can't just make a new connection in the foreground
// when none are available, since this can take several
// seconds with a slow network connection. Instead,
// start a thread that establishes a new connection,
// then wait. You get woken up either when the new connection
// is established or if someone finishes with an existing
// connection.
private void makeBackgroundConnection() {
 connectionPending = true;
 try {
 Thread connectThread = new Thread(this);
 connectThread.start();
 } catch(OutOfMemoryError oome) {
 // Give up on new connection
 log.write(oome.getMessage());
public void run() {
 try {
 Connection connection = makeNewConnection();
 synchronized(this) {
 availableConnections.addElement(connection);
 connectionPending = false;
 notifyAll();
 } catch(Exception e) { // SQLException or OutOfMemory
 // Give up on new connection and wait for existing one free up.
 log.write(e.getMessage());
// This explicitly makes a new connection. Called in
// the foreground when initializing the ConnectionPool,
// and called in the background when running.
private Connection makeNewConnection()
 //log.write("make new connection with "+url+" "+username+" "+password +" and driver= "+driver);
 Connection connection=null;
 try
 // Load database driver if not already loaded
 //Class.forName(driver);
 DriverManager.registerDriver(new OracleDriver());
 // Establish network connection to database
 connection = DriverManager.getConnection(url, username, password);
 if( connection.isClosed() )
 log.write("ooooooops no connection");
 else
 log.write("yahoooo get connection");
 catch(Exception e)
 log.write(e.getMessage());
 return(connection);
public synchronized void free(Connection connection) {
 busyConnections.removeElement(connection);
 availableConnections.addElement(connection);
 // Wake up threads that are waiting for a connection
 notifyAll();
public synchronized int totalConnections() {
 return(availableConnections.size() + busyConnections.size());
/** Close all the connections. Use with caution:
 * be sure no connections are in use before
 * calling. Note that you are not required to
 * call this when done with a ConnectionPool, since
 * connections are guaranteed to be closed when
 * garbage collected. But this method gives more control
 * regarding when the connections are closed.
public synchronized void closeAllConnections() {
 closeConnections(availableConnections);
 availableConnections = new Vector();
 closeConnections(busyConnections);
 busyConnections = new Vector();
private void closeConnections(Vector connections) {
 try {
 for(int i=0; i<connections.size(); i++) {
 Connection connection =
 (Connection)connections.elementAt(i);
 if (!connection.isClosed()) {
 connection.close();
 } catch(SQLException sqle) {
 // Ignore errors; garbage collect anyhow
 log.write(sqle.getMessage());
}i get this code from internet, in which it also mention that use following code
public class BookPool extends ConnectionPool {
private static BookPool pool = null;
private BookPool(...) {
super(...); // Call parent constructor
public static synchronized BookPool getInstance() {
if (pool == null) {
pool = new BookPool(...);
return(pool);
}if some one want to use it for whole application then use connection pool by BookPool,
now main point is i m not getting the BookPool class could some one explain it to me???
and second by using it can i connect to different users of DB at a time, if cant then how i can.
its good if some one explain it by little code.
thxxxxxxxxxxxxxxxxxx

If this is a real, serious application and not just for practice, then why are you trying to write your own connection pool implementation?
You'd better use Jakarta's Commons Pool and Commons DBCP, which are widely used, well tested implementations of connection pools.
If this is a web application running in a J2EE container, you'd normally configure the connection pool in the container. The container will register the pool in JNDI and you'd look it up in JNDI from your application.
Here's some documentation on how to do that in Tomcat 5.5: JNDI Datasource HOW-TO

Unable to create connection pool on weblogic startup

Hi, I have a problem currently with the connection pool of weblogic 8.1 not being able to be created on a scheduled restart daily.
The weblogic server is restarted daily at 6am. However, the oracle database is shut down for maintenance daily till 7am before it is up again. It is not possible to shift either timings of restarting weblogic and oracle.
Is there any script or option settings in weblogic to reconnect the connection pool after 7am daily without restarting the weblogic instance?
Please help. Thanks.

Kwee Tin Toh wrote:
Hi, I have a problem currently with the connection pool of weblogic 8.1 not being able to be created on a scheduled restart daily.
The weblogic server is restarted daily at 6am. However, the oracle database is shut down for maintenance daily till 7am before it is up again. It is not possible to shift either timings of restarting weblogic and oracle.
Is there any script or option settings in weblogic to reconnect the connection pool after 7am daily without restarting the weblogic instance?
Please help. Thanks.You can use the weblogic.Admin command line program to create, destroy, disable, or enable pools
in a running server. However, the easiest thing to do is to define your pool to have an initial
capacity of zero, so it is allowed to be created at startup, without needing to make any connections.
Then it will self-populate as needed when application load starts, if/when the DBMS is available.
Joe

ORA-22990 ( Cannot span lob... ) while using connection pooling...

Hi all, I am maintaining a web site that has lots of requests ( about 10 requests a second ) to an Oracle table that has a BLOB field. Those requests create new blobs, updates them and reads them... My program worked fine until I started using connection pooling ( Before that, I used a single connection that was initialized at startup ). Although I had to synchronized the methods that interact with blob field, everything worked great. So now, to optimize my site, I want to use connection pooling so that even if my methods are synchonized on the connection object, there will be more than one connection available so it will not affect performance.
So once I introduced my connection pooling system with the oracle.jdbc.pool.OracleConnectionCacheImpl class, I started getting ORA-22990 ( Cannot span lob objects... ). I get the error on the flush() method when I try to write the blob to the database. Here is my function that writes a row in the databse.
private synchronized void writeSession(CapSession pSession) throws Exception
        javax.sql.PooledConnection pc = pool.getPooledConnection();
        Connection conn = pc.getConnection();
        CallableStatement stmt=conn.prepareCall(writeObjSQL);
        stmt.setString(1,pSession.getSessionId()+pSession.getPassword());
        stmt.setLong(2,pSession.getLastAccess());
        stmt.setLong(3,pSession.getTimeout());
        stmt.registerOutParameter(4,java.sql.Types.BLOB);
        stmt.executeUpdate();
        oracle.sql.BLOB blob=(BLOB)stmt.getBlob(4);
        OutputStream os=blob.getBinaryOutputStream();
        ObjectOutputStream oop=new ObjectOutputStream(os);
        oop.writeObject(pSession);
        oop.flush();
        oop.close();
        os.close();
        stmt.close();
        conn.commit();
        conn.close();
        pc.close();
} If anyone could help me, I would deeply appreciate it!
Thank you for your time.

kalle
Thank you very much for your advice!!!
Like you said, I started to check whether the connections are fine before giving them from the pool.I am executing a simple "select 'anil' from dual" and if its fine only then I return the connection. So far it seems to be fine. Also I am reopening the connections(closing the old ones and opening new connections) after every 12 hours.
As far as the JDBC driver is concerned, I already tried with Oracle 8i driver, it gave the same problems. I read that 9i driver might solve this problem, so I changed to the latest 9i driver (classes12_g.zip).
Sometimes before(before I started checking whether the connection is good )the application used to hang up at the point where I am issuing setAutoCommit(false).It never comes out from that statement.Is this something to do with theconnections being closed?
What I am afraid is, will the appilation get hung up even after I check the connection with select query and then issue autocommit(false)??
Or will it hang up while I check with a select query??
As long as it doesn't hung up, I am fine. Because i am cathching the exceptions.
Thanks In ADVANCE
Anil

How to use connection pool with RDBMSRealm

I am having a problem with the RDBMSRealm. The problem is that the connection defined in the .realm_properties file times out after 1 hour. My solution was to use the connection pool defined in the weblogic.properties file, but the realm_proprties are read before the connection pool is created so it did'nt work.Is there anyway of controling the order of which WLS reads various properties?If no, is there any way of setting "autorefresh" on the connection defined in the .realm_properties file?I'am using WLS 5.1, S.P 8, WIN2000 and Sybase. It works fine except for the timeout.Please help-Marius

I've been struggling to find a way to use a weblogic connection
pool or datasource nicely, and have failed with whatever I've tried.
There is a chicken and egg problem here. The connection pool needs
security to initialize itself, and security needs a connection
pool. So that will not work.
I've tried the follwing, which almost worked. Weblogic falls
back to the default realm if your custom realm returns null for
any user or group requests. So if your custom realm is not capable
of reading info from the database, return null. The default realm
will take over, and allow the connection pool to initialize if
you allow everybody (or users defined in the weblogic.properties
file) access to the pool. Then define a datasource which points
to the pool.
After the server starts, security can then use JNDI to look up
the datasource, and all seems well. However, in some instances
(it seems like calls for a bean), where security and jndi can get
into infinite loops where jndi performs a security check when doing
the lookup, so they both end up asking each other for information.
So if anyone knows how to successfully use a connection pool or
DataSource in a custom realm, I would love to know how.
For you, I would suggest you don't try and use a connection pool,
but figure out how to refresh your connection. You can do it manually
by taking your connection, checking if it's valid before using
it, if not, then open a new one.
-d-
Marius <[email protected]> wrote:
I am having a problem with the RDBMSRealm. The problem
is that the connection defined in the .realm_properties
file times out after 1 hour. My solution was to use the
connection pool defined in the weblogic.properties file,
but the realm_proprties are read before the connection
pool is created so it did'nt work.Is there anyway of
controling the order of which WLS reads various properties?If
no, is there any way of setting "autorefresh" on the
connection defined in the .realm_properties file?I'am
using WLS 5.1, S.P 8, WIN2000 and Sybase. It works fine
except for the timeout.Please help-Marius

Error while executing jdbc commands but getting connection pool

I was not able to make a simple oracle connection and that hurts me.
The program(jsp) is...
<%@ page language="java" import="java.sql.*,java.io.*,
java.util.*,pac1.*,javax.naming.*,javax.sql.*"%>
<html>
<body>
<%
Context ctx= new InitialContext();
DataSource dsindogulf1=(DataSource)ctx.lookup("jnindogulf1");
Connection conn=dsindogulf1.getConnection();
if(conn!=null)
System.out.println(conn.toString());
else
System.out.println("sorry");
Statement st=conn.createStatement();
String string1="CREATE TABLE Authorr(col1 CHAR(10));";
st.executeUpdate(string1);
%>
</body>
</html>
If i delete the
st.executeUpdate(string1); then there is no problem I get the connection pool. That means i am getting the connection. But when i include the
st.executeUpdate(string1); there is an error which i cannot understand.. the error is
Error 500--Internal Server Error
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-00911: invalid character
 at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
 at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
 at weblogic.jdbc.oracle.OracleImplStatement.execute()V(Optimized Method)
 at weblogic.jdbc.base.BaseStatement.commonExecute()V(Optimized Method)
 at weblogic.jdbc.base.BaseStatement.executeUpdateInternal()I(Unknown Source)
 at weblogic.jdbc.base.BaseStatement.executeUpdate(Ljava.lang.String;)I(Unknown Source)
 at weblogic.jdbc.wrapper.Statement.executeUpdate(Ljava.lang.String;)I(Statement.java:360)
 at jsp_servlet.__test._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__test.java:149)
 at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
 at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3661)
 at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
 at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
 at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
the steps which i have followed are... I have made a connection pool using weblogic type 4 driver in the administrative console... then i have created the data source using jndi name jnindogulf1..... but although i am getting the connection pool i am receiving error ehice executing jdbc commands
please help
thanks

babuli nayak wrote:
I was not able to make a simple oracle connection and that hurts me.
The program(jsp) is...
<%@ page language="java" import="java.sql.*,java.io.*,
java.util.*,pac1.*,javax.naming.*,javax.sql.*"%>
<html>
<body>
<%
Context ctx= new InitialContext();
DataSource dsindogulf1=(DataSource)ctx.lookup("jnindogulf1");
Connection conn=dsindogulf1.getConnection();
if(conn!=null)
System.out.println(conn.toString());
else
System.out.println("sorry");
Statement st=conn.createStatement();
String string1="CREATE TABLE Authorr(col1 CHAR(10));";
st.executeUpdate(string1);
%>
</body>
</html>
If i delete the
st.executeUpdate(string1); then there is no problem I get the connection pool. That means i am getting the connection. But when i include the
st.executeUpdate(string1); there is an error which i cannot understand.. the error is
Error 500--Internal Server Error
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-00911: invalid character
 at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
 at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
 at weblogic.jdbc.oracle.OracleImplStatement.execute()V(Optimized Method)
 at weblogic.jdbc.base.BaseStatement.commonExecute()V(Optimized Method)
 at weblogic.jdbc.base.BaseStatement.executeUpdateInternal()I(Unknown Source)
 at weblogic.jdbc.base.BaseStatement.executeUpdate(Ljava.lang.String;)I(Unknown Source)
 at weblogic.jdbc.wrapper.Statement.executeUpdate(Ljava.lang.String;)I(Statement.java:360)
 at jsp_servlet.__test._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__test.java:149)
 at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
 at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3661)
 at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
 at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
 at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
the steps which i have followed are... I have made a connection pool using weblogic type 4 driver in the administrative console... then i have created the data source using jndi name jnindogulf1..... but although i am getting the connection pool i am receiving error ehice executing jdbc commands
please help
thanks
Hi. Remove the semicolon from your SQL string: stmt.executeUpdate("CREATE TABLE Authorr(col1 CHAR(10))");Joe

Database connection pooling in ADF causing db procedure calls to use different transaction or session

We have developed an application using JDev Version 11.1.2.1.0 and the database is oracle 11g EE.
We have many database procedures or function calls from the model (AMImpl.java, VORowImpl.java) and the commit does not happen in the database and it happens from ADF. The database procedures are called in some valueChangeListnener and these procedures use the same transaction or session database session when called and update some records in some tables that are displayed in pages.
We started using connection pooling recently in our ADF application, -Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1. When using connection pooling, we noticed that the database procedure calls use a different trasanction or different database session and the data or records that these procedures update is lost.
After removing the connection pooling, we noticed that the procedures again started using the same transaction or same database session and was working fine.
I want to know why this connnection pooling caused this issue and is there any fix for this when using connection pooling?

Take a look at
http://docs.oracle.com/cd/E15523_01/web.1111/b31974/bcampool.htm#CIHCHHEA
What You May Need to Know About Database User State and jbo.doconnectionpooling = true
As you can see:
"At the end of the request when the application module is released back to the application module pool, that application module pool releases the JDBC connection it was using back to the database connection pool. It follows that with jbo.doconnectionpooling set to true the application module instance in the pool may have a completely different JDBC connection each time you check it out of the pool"
So, the best you can do, is to revert jbo.doconnectionpooling to false.

Connection Pool error

Hello,
I am getting the following error in Answers while trying to view the results
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 16001] ODBC error state: IM002 code: 0 message: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. (HY000)
SQL Issued: SELECT reports."YEAR" saw_0, REPORTs."Total " saw_1 FROM sample_prod_pc ORDER BY saw_0
And in the administration tool during the consistency check i am getting the following warning
[39028] The features in the database sample_prod do not match the defaults.This can cause the query problems.
Please let me know where is the problem.
Thanks in Advance.

Hi Kishore,
Thanks for the reply.
I am able to import the metadata from from this datasource like administrationtool->file->import->from database.
Its working fine without any problems.But when i say update row counts its throwing the following errors.
[NQODBC][SQL_STATE:HY000][nqserror: 10058] A general error has occured.
[nqsError :43093]An errror occured while processing the EXECUTE Physical statement.
[nQSError: 17001]Oracle Error Code:12154,message:ORA-12154:TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach.
[nQSerror: 17014] Could not connect to ORacle database.
Is that means no problem with the DSN connection,but the problem is with the connection pool?
Please help me out.
Thanks in advance.

Running WL as NT Service is not Creating Connection Pools?

We have something very strange happening here. We recently installed Weblogic 6.1 sp 4 on an WinNT 2000 box and installed our application. We are connecting to an Oracle 8.1.7 database using the Oracle 8.1.7 client drivers. We configured our connection pool via the Web Console. We also installed our application to run as a NT Service using "beasvc.exe" utility.
When we run our application after starting Weblogic from the commandline, our application runs fine. It creates the Oracle connection pool and everything is great.
However when we run our application by starting it under the NT Services window, our application fails to start the connection pool. Looking at all the logs, I don't see and errors or exceptions being thrown. I did notice that the connection pool was not created. But again, no errors were thrown.
Has anyone seen this behavior? To make things more confusing for me, this whole solution is working fine on another WinNT 2000 box with the only difference beint that we are using Weblogic 6.1 sp2. Anyone have any ideas??? Also, running the NT Service version of Weblogic in debug mode also worked!

It takes the Oracle service quite a bit of time to start up. Make sure that you
set up the DependsOnService correctly in your registry so that Oracle comes up
fully before launching WL.
Paul
Clyde <[email protected]> wrote:
We have something very strange happening here. We recently installed
Weblogic 6.1 sp 4 on an WinNT 2000 box and installed our application.
We are connecting to an Oracle 8.1.7 database using the Oracle 8.1.7
client drivers. We configured our connection pool via the Web Console.
We also installed our application to run as a NT Service using "beasvc.exe"
utility.
When we run our application after starting Weblogic from the commandline,
our application runs fine. It creates the Oracle connection pool and
everything is great.
However when we run our application by starting it under the NT Services
window, our application fails to start the connection pool. Looking
at all the logs, I don't see and errors or exceptions being thrown.
I did notice that the connection pool was not created. But again,
no errors were thrown.
Has anyone seen this behavior? To make things more confusing for me,
this whole solution is working fine on another WinNT 2000 box with the
only difference beint that we are using Weblogic 6.1 sp2. Anyone have
any ideas??? Also, running the NT Service version of Weblogic in debug
mode also worked!

JDriver for MS SQL Server 6.5 and Connection Pooling

I was given the unfortunate task :-) of getting data out of M$FT SQL 6.5. I set
up a JDBC connection pool using jDriver in mssqlserver4v65.jar, and created a
JDBCDataSource for the pool. I am using a stateless session bean + JDBC (with
the DAO pattern) to get data. In the DAO class I have an instance variable for
the datasource, which I look up in the constructor. In the DAO's business method
I RELIGIOUSLY call datasource.getConnect() first, and ALWAYS call connection.close()
in the finally block. Now the initial requests are fine, but after a while I
got a weblogic.common.ResourceException telling me there were no more connection
available in the pool. Is this a jDriver bug? I never run into such a problem
with an Oracle connection pool using the thin driver.
Any insight will be greatly appreciated.
Eric Ma

Eric Ma wrote:
Joe:
Connection is a LOCAL variable declared in each method. DataSource is an instance
variable.That sounds fine... let me see your code (main block plus finally block). How long does this
take to reproduce? Show me your pool definition.
thanks,
Joe
>
>
Eric
Joseph Weinstein <[email protected]> wrote:
Eric Ma wrote:
I was given the unfortunate task :-) of getting data out of M$FT SQL6.5. I set
up a JDBC connection pool using jDriver in mssqlserver4v65.jar, andcreated a
JDBCDataSource for the pool. I am using a stateless session bean +JDBC (with
the DAO pattern) to get data. In the DAO class I have an instancevariable for
the datasource, which I look up in the constructor. In the DAO's businessmethod
I RELIGIOUSLY call datasource.getConnect() first, and ALWAYS call connection.close()
in the finally block. Now the initial requests are fine, but aftera while I
got a weblogic.common.ResourceException telling me there were no moreconnection
available in the pool. Is this a jDriver bug? I never run into sucha problem
with an Oracle connection pool using the thin driver.
Any insight will be greatly appreciated.
Eric MaHi. Is the connection object an instance variable? That would be a problem.
The connection object has to be a method variable to be safe from multithreading
issues.
Joe

Problems in starting up Connection Pools in SQLServer7

Similar Messages

Maybe you are looking for