Copy Connection Pool

Hello
As I see it one of the biggest tasks in setting up SJSAS is configuring database connection pools. This would not be such a big task if the admin console came up with a default list of properties that matches those we use.
The temptation is to go copying and pasting sections of the file domain.xml this temptation would be removed if the admin console allowed you to create a new database connection pool as a copy of an existing pool.
This is not possible already is it ?
How would I get this raised as a new feature request ?

Hello
As I see it one of the biggest tasks in setting up
SJSAS is configuring database connection pools. This
would not be such a big task if the admin console
came up with a default list of properties that
matches those we use.
The temptation is to go copying and pasting sections
of the file domain.xml this temptation would be
removed if the admin console allowed you to create a
new database connection pool as a copy of an existing
pool.I believe we already have basic properties listed, when one wants to create
a JDBC connection pool. Aren't you using app server 8.1?
>
This is not possible already is it ?
How would I get this raised as a new feature request ?

Similar Messages

Issue JDBC connection pool with Glassfish 3.1.2.2 and Oracle XE 11gR2

Hello,
I am experiencing an issue with pinging a JDBC connection Pool.
I installed the following without any warnings or errors:
Operating System: Oracle Enterprise Linux 5
Oracle XE 11gR2 (11.2.0.2.0) database
Glassfish 3.1.2.2
I will refer to the steps I did after the installations
1) In the .profile file of the OS I add the following:
JRE_HOME=/usr/java/jre1.6.0_31; export JRE_HOME
JAVA_HOME=/usr/java/jdk1.6.0_31; export JAVA_HOME
GLASSFISH_DIR=/u01/glassfish3
GLASSFISH_HOME=/u01/glassfish3/glassfish
DERBY_HOME=$GLASSFISH_DIR/javadb
OPEN_MQ_HOME=$GLASSFISH_DIR/mq
PATH=:$JAVA_HOME/bin:$JRE_HOME/bin:$PATH:$HOME/bin:$GLASSFISH_HOME/bin:$DERBY_HOME/bin:$OPEN_MQ_HOME/bin
export GLASSFISH_HOME
export DERBY_HOME
export OPEN_MQ_HOME
export PATH
LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/xe/lib; export LD_LIBRARY_PATH
. /u01/app/oracle/product/11.2.0/xe/bin/oracle_env.sh
2) I copied the ojdbc6.jar to the $GLASSFISH_HOME/domains/domain1/lib
3) I login to the Glassfish admin console and created a new JDBC Connection Pool.
Pool Name: ds_orasys
Resource Type: javax.sql.DataSource
Datasource Classname: oracle.jdbc.pool.OracleDataSource
User: [myschema]
Password: [myschema password]
URL: jdbc:oracle:thin:@localhost:1521:xe
When I ping the connection pool I get the following message in the server log:
[#|2012-10-23T12:14:37.069+0300|WARNING|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=22;_ThreadName=Thread-2;|RAR8054: Exception while creating an unpooled [test] connection for pool [ ds_orasys ], Connection could not be allocated because: Invalid Oracle URL specified|#]
[#|2012-10-23T12:14:37.071+0300|SEVERE|glassfish3.1.2|org.glassfish.admingui|_ThreadID=19;_ThreadName=Thread-2;|RestResponse.getResponse() gives FAILURE. endpoint = 'http://212.205.62.217:4848/management/domain/resources/ping-connection-pool.json'; attrs = '{id=ds_orasys}'|#]
I tried to use different jar files. I used ojdbc6dms.jar and ojdbc14.jar.
I also copied the jar files in the $GLASSFISH_HOME/domains/domain1/lib/ext directory as some people suggested. Still no luck. I keep getting the same error messages in the server.log
Can anybody help me out or point me to the right direction.
Thank you in advance

The error is in the URL. It was in front of my eyes and I couldn't see the error. I skipped the ':' before the '@' when I created the pool. It is working fine now.

HELP - DB2 v9 & App Server PE 9.0 - PING Connection Pool Failure - HELP

I've been playing around with Studio Creator and DB2 v9 without any issues.
So I figured I would installed App Server PE 9 and use this as my production server that I would deploy to from studio creator.
However, in my efforts to set up db2/v9 I have been trying to ping a connection pool without any luck. I get the following message:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [sunm][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
My datasource class name is com.sun.sql.jdbcx.db2.DB2DataSource.
And my resource type is javax.sql.datasource
I have copied smbase.jar, smdb2.jar and smutil.jar into c:\sun\appserver\lib
and I have all of the properties (serverName, portNumber, databaseName, user, password) created and set accordingly.
Any help would be greatly appreciated.

Here is how I got the DB2 Express-C and Sun PE 9.0 to work. ( at least base connectivity wise )
1. ) You have to have at least the DB2 Client installed on the system that will be communicating to the DB2 instance.
2.) The following jars will be needed ( depending on the driver type used) . db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar and use them in the App Server ->JVM settings -> Path Settings -> Classpath Suffix
3.) The next setup is dependent on the Type driver you use
I used the Type 4 and this is the resource setup I used.
Connection Pool:
Name: DB2TestPool
Datasource Classname: com.ibm.db2.jcc.DB2SimpleDataSource
Resource Type: javax.sql.ConnectionPoolDataSource
Properties:
user: xxxxxx
password: xxxxxx
databaseName: TEST
serverName: <hostname of machine>
portnumber: 50000
driverType: 4
URL: jdbc:db2://<hostname>:<port>/<database>
JDBC Resource:
JNDI Name: jdbc/TEST
Pool Name: DB2TestPool
With this configuration I was able to ping the database as well as connect to create an entity bean from a table. This should give you a starting point.
I have yet to deploy my application, but should be doing that sometime today to verify that a connection can be made and used from within the application.

How database connection pooling works in a application

Hi Guys,
I am new to Java and looking into best way of doing J2ee database conectivity. I am using Eclipse galileo3.5 J2EE with Mysql database and Tomcate 6.0.
I am developing an email application where I need to implement MVC model for my webapplication, using jsp for presentation, servlet for control and java beans for model.
I came across two tutorial for database connection pooling as given below.
Eclipse Corner Article: Creating Database Web Applications with Eclipse - In this tutorial connection pooling is configure in Tomcate 6.0
It says Copy and paste the following into your context.xml file (you may have to click on the Source tab at the bottom of the editor to be able to paste). This defines a DataSource with the name "jdbc/SampleDB". Our application will retrieve database connections from the pool using this name.
<?xml version="1.0" encoding="UTF-8"?>
<Context>
<Resource name="jdbc/SampleDB" auth="Container"
type="javax.sql.DataSource"
username="app" password="app"
driverClassName="org.apache.derby.jdbc.ClientDrive r"
url="jdbc:derby://localhost:1527/sample"
maxActive="8" />
</Context>
Where as in second tutorial - http://www.roseindia.net/answers/viewanswers/2838.html
It uses java bean for connection pooling and then use straight way in JSP and no Servlet used.
conpool.jsp
<%@page import="java.sql.Connection"%>
<jsp:useBean id="pl" class="com.CoreJava.ConnectionPooling"/>
<% Connection con = pl.getConnection(); %>
//do something using con
connectionPooling.java
import com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolD ataSource;
public class ConnectionPooling
static Connection con=null;
public static Connection getConnection()
try
MysqlConnectionPoolDataSource po=new MysqlConnectionPoolDataSource();
po.setServerName("localhost");
po.setPortNumber(3306);
po.setDatabaseName("mydatabase"); //changeur database name
po.setUser("root");//ur username
po.setPassword("");//ur password
con = po.getConnection();
catch(Exception e)
System.out.println("Exception Connection :"+e);
return con;
Please some one explain which is the best way of doing connection pooling to the database by using MVC pattern
Please if some one advise me how to use MVC architecture for simple email application and database connectivty.
Thanks

>
>
Where as in second tutorial - http://www.roseindia.net/answers/viewanswers/2838.html
Never EVER use roseindia. It is terrible shit.
[http://balusc.blogspot.com/2008/06/what-is-it-with-roseindia.html]
The correct answer is what you found in the eclipse article. And you can read the Tomcat docs for more.
As per usual the code you have posted from Roseindia is a big pile of rubbish that was written by a complete idiot. I mean the person who wrote it apparently doesn't know much Java at all. Let alone JDBC. Or Connection pools. Or J2EE. It's not the worst I've seen from them but it's pretty bad.

Connection pooling and auditing on an oracle database

Integration of a weblogic application with an oracle backend,
Connection pooling, and auditing ,2 conflicting requirements ?
Problem statement :
We are in the process of maintaining a legacy client server application where
the client is
written in PowerBuilder and the backend is using an Oracle database.
Almost all business logic is implemented in stored procedures on the database.
When working in client/server mode ,1 PowerBuilder User has a one-to-one relation
with
a connection(session) on the oracle database.
It is a requirement that the database administrator must see the real user connected
to the database
and NOT some kind of superuser, therefore in the PowerBuilder app each user connects
to the database
with his own username.(Each user is configured on the database via a seperate
powerbuilder security app).
For the PowerBuilder app all is fine and this app can maintain conversional state(setting
and
reading of global variables in oracle packages).
The management is pushing for web-based application where we will be using bea
weblogic appserver(J2EE based).
We have build an business app which is web-based and accessing the same oracle
backend app as
the PowerBuilder app is doing.
The first version of this web-based app is using a custom build connector(based
on JCA standard and
derived from a template provided by the weblogic integration installation).
This custom build connector is essentially a combination of a custom realm in
weblogic terms
and a degraded connection pool , where each web session(browser) has a one-to-one
relation
with the back end database.
The reason that this custom connector is combining the security functionality
and the pooling
functionality , is because each user must be authenticated against the oracle
database(security requirement)
and NOT against a LDAP server, and we are using a statefull backend(oracle packages)
which would make it
difficult to reuse connections.
A problem that surfaced while doing heavy loadtesting with the custom connector,
is that sometimes connections are closed and new ones made in the midst of a transaction.
If you imagine a scenario where a session bean creates a business entity ,and
the session bean
calls 1 entity bean for the header and 1 entity bean for the detail, then the
header and detail
must be created in the same transaction AND with the same connection(there is
a parent-child relationship
between header and detail enforced on the back end database via Primary and Foreing
Keys).
We have not yet found why weblogic is closing the connection!
A second problem that we are experincing with the custom connector, is the use
of CMP(container managed persistence)
within entity beans.
The J2EE developers state that the use of CMP decreases the develoment time and
thus also maintenance costs.
We have not yet found a way to integrate a custom connector with the CMP persistence
scheme !
In order to solve our loadtesting and CMP persistence problems i was asked to
come up with a solution
which should not use a custom connector,but use standard connection pools from
weblogic.
To resolve the authentication problem on weblogic i could make a custom realm
which connects to the
backend database with the username and password, and if the connection is ok ,
i could consider this
user as authenticated in weblogic.
That still leaves me with the problem of auditing and pooling.
If i were to use a standard connection pool,then all transaction made in the oracle
database
would be done by a pool user or super user, a solution which will be rejected
by our local security officer,
because you can not see which real user made a transaction in the database.
I could still use the connection pool and in the application , advise the application
developers
to set an oracle package variable with the real user, then on arrival of the request
in the database,
the logic could use this package variable to set the transaction user.
There are still problems with this approach :
- The administrator of the database can still not see who is connected , he will
only see the superuser connection.
- This scheme can not be used when you want to use CMP persistence , since it
is weblogic who will generate the code
to access the database.
I thought i had a solution when oracle provided us with a connection pool known
as OracleOCIConnectionPool
where there is a connection made by a superuser, but where sessions are multiplexed
over this physical pipe with the real user.
I can not seem to properly integrate this OCI connectionpool into weblogic.
When using this pool , and we are coming into a bean (session or entity bean)
weblogic is wrapping
this pool with it's own internal Datasource and giving me back a connection of
the superuser, but not one for the real user,
thus setting me with my back to the wall again.
I would appreciate if anyone had experienced the same problem to share a possible
solution with us
in order to satisfy all requirements(security,auditing,CMP).
Many Thanks
Blyau Gino
[email protected]

Hi Blyau,
As Joe has already provided some technical advice,
I'll try to say something on engineering process level.
While migrating an application from one technology to
other, like client-server to n-tier in you case, customers and
stakeholders want to push into the new system as many old
requirements as possible. This approach is AKA "we must
have ALL of the features of the old system". Mostly it happens
because they don't know what they want. Ad little understanding
of abilities of the new technology, and you will get a requirement
like the one you have in you hands.
I think "DBA must see real user" is one of those. For this
type of requirements it can make sense to try to drop it,
or to understand its nature and suggest alternatives. In this
particular case it can be a system that logs user names,
login and logout times.
Blind copying of old features into an incompatible new architecture
may endanger the whole project and can result in its failure.
Hope this helps.
Regards,
Slava Imeshev
"Blyau Gino" <[email protected]> wrote in message
news:[email protected]...
>
Integration of a weblogic application with an oracle backend,
Connection pooling, and auditing ,2 conflicting requirements ?
Problem statement :
We are in the process of maintaining a legacy client server applicationwhere
the client is
written in PowerBuilder and the backend is using an Oracle database.
Almost all business logic is implemented in stored procedures on thedatabase.
When working in client/server mode ,1 PowerBuilder User has a one-to-onerelation
with
a connection(session) on the oracle database.
It is a requirement that the database administrator must see the real userconnected
to the database
and NOT some kind of superuser, therefore in the PowerBuilder app eachuser connects
to the database
with his own username.(Each user is configured on the database via aseperate
powerbuilder security app).
For the PowerBuilder app all is fine and this app can maintainconversional state(setting
and
reading of global variables in oracle packages).
The management is pushing for web-based application where we will be usingbea
weblogic appserver(J2EE based).
We have build an business app which is web-based and accessing the sameoracle
backend app as
the PowerBuilder app is doing.
The first version of this web-based app is using a custom buildconnector(based
on JCA standard and
derived from a template provided by the weblogic integrationinstallation).
This custom build connector is essentially a combination of a custom realmin
weblogic terms
and a degraded connection pool , where each web session(browser) has aone-to-one
relation
with the back end database.
The reason that this custom connector is combining the securityfunctionality
and the pooling
functionality , is because each user must be authenticated against theoracle
database(security requirement)
and NOT against a LDAP server, and we are using a statefull backend(oraclepackages)
which would make it
difficult to reuse connections.
A problem that surfaced while doing heavy loadtesting with the customconnector,
>
is that sometimes connections are closed and new ones made in the midst ofa transaction.
If you imagine a scenario where a session bean creates a business entity,and
the session bean
calls 1 entity bean for the header and 1 entity bean for the detail, thenthe
header and detail
must be created in the same transaction AND with the same connection(thereis
a parent-child relationship
between header and detail enforced on the back end database via Primaryand Foreing
Keys).
We have not yet found why weblogic is closing the connection!
A second problem that we are experincing with the custom connector, is theuse
of CMP(container managed persistence)
within entity beans.
The J2EE developers state that the use of CMP decreases the develomenttime and
thus also maintenance costs.
We have not yet found a way to integrate a custom connector with the CMPpersistence
scheme !
In order to solve our loadtesting and CMP persistence problems i was askedto
come up with a solution
which should not use a custom connector,but use standard connection poolsfrom
weblogic.
To resolve the authentication problem on weblogic i could make a customrealm
which connects to the
backend database with the username and password, and if the connection isok ,
i could consider this
user as authenticated in weblogic.
That still leaves me with the problem of auditing and pooling.
If i were to use a standard connection pool,then all transaction made inthe oracle
database
would be done by a pool user or super user, a solution which will berejected
by our local security officer,
because you can not see which real user made a transaction in thedatabase.
I could still use the connection pool and in the application , advise theapplication
developers
to set an oracle package variable with the real user, then on arrival ofthe request
in the database,
the logic could use this package variable to set the transaction user.
There are still problems with this approach :
- The administrator of the database can still not see who is connected ,he will
only see the superuser connection.
- This scheme can not be used when you want to use CMP persistence , sinceit
is weblogic who will generate the code
to access the database.
I thought i had a solution when oracle provided us with a connection poolknown
as OracleOCIConnectionPool
where there is a connection made by a superuser, but where sessions aremultiplexed
over this physical pipe with the real user.
I can not seem to properly integrate this OCI connectionpool intoweblogic.
When using this pool , and we are coming into a bean (session or entitybean)
weblogic is wrapping
this pool with it's own internal Datasource and giving me back aconnection of
the superuser, but not one for the real user,
thus setting me with my back to the wall again.
I would appreciate if anyone had experienced the same problem to share apossible
solution with us
in order to satisfy all requirements(security,auditing,CMP).
Many Thanks
Blyau Gino
[email protected]

How to use my connection pool in multiple servlets?

I now have a functioning connection pool using these lines in a servlet:
private Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
========================
If I want to create additional servlets in the same web app which query the same database,
do I need to repeat this block of code in every servlet, or can I just put it in one servlet
and have other servlets access it in some way to get a connection? Should I change the code
above from a "private" Connection to a "public" Connection?
An example servlet is shown below. To put my question another way: If I want to
create a second servlet with a different set of queries, would I just make a copy of the first
servlet and then change only the queries, or is there a more efficient way to have multiple
servlets get connections from the pool?
Any suggestions are greatly appreciated.
Thank you.
Logan
************************************servlet example**********************************
package CraigsClasses;
import javax.servlet.*;
import javax.servlet.jsp.*;
import java.net.*;
import java.util.*;
import java.io.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.Date;
import java.text.*;
import javax.naming.*;
import javax.sql.DataSource;
public class CraigsMain extends HttpServlet {
public void init(ServletConfig config) throws ServletException {
super.init(config);
private Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
// Process the http Get request
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
try {
response.setContentType("text/html");
PrintWriter out = response.getWriter();
String sql = "select formtitle from checkboxforms where cbformid = 157";
// error occurs at this line
Connection ocon = getConnection("java:comp/env/jdbc/CraigsList");
PreparedStatement pStmt = ocon.prepareStatement(sql);
ResultSet rs1 = pStmt.executeQuery();
rs1.next();
out.println(" " + rs1.getString(1));
rs1.close();
pStmt.close();
ocon.close();
} catch(SQLException sqle) {
System.err.println("sql exception error: " + sqle);
} catch(NamingException ne) {
System.err.println("naming exception error: " + ne);
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
doGet(request, response);
=======================================================================

sjasja, Thank you for the reply. What you are suggesting is exactly what I have been looking for. But I'm pretty weak on how to make this separate con pool servlet work. My first attempt is shown below. It doesn't compile this line, which is obviously wrong:
public static Connection getConnection(String lookup) throws NamingException, SQLException {
Could you please help me with this servlet code? Thanks.
package CraigsClasses;
import javax.servlet.*;
import javax.servlet.jsp.*;
import java.net.*;
import java.io.*;
import javax.servlet.http.*;
import java.sql.*;
import javax.naming.*;
import javax.sql.DataSource;
public class ConPoolInit extends HttpServlet {
public void init(ServletConfig config) throws ServletException {
super.init(config);
try {
public static Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
} catch(SQLException sqle) {
System.err.println("sql exception error: " + sqle);
} catch(NamingException ne) {
System.err.println("naming exception error: " + ne);
=======================================

Shared Connection Pool via Singleton

I have just started to learn Java (more jsp & servlets) and have been going through "Core Servlets and Java Server Pages" and in there is stuff on connection pooling. The author provides a good a connection pool servlet that can be shared, but as I'm new and don't fully understand how everything works (got a basic idea).
How do i go about making the following code accessiable via a singleton class?
ConnectionPool Class
package sco;
import java.sql.*;
import java.util.*;
/** A class for preallocating, recycling, and managing
* JDBC connections.
* 
* Taken from Core Servlets and JavaServer Pages
* from Prentice Hall and Sun Microsystems Press,
* http://www.coreservlets.com/.
* © 2000 Marty Hall; may be freely used or adapted.
public class ConnectionPool implements Runnable {
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)
 throws SQLException {
 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();
 for(int i=0; i<initialConnections; i++) {
 availableConnections.addElement(makeNewConnection());
public synchronized Connection getConnection()
 throws SQLException {
 if (!availableConnections.isEmpty()) {
 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.
 if (existingConnection.isClosed()) {
 notifyAll(); // Freed up a spot for anybody waiting
 return(getConnection());
 } else {
 busyConnections.addElement(existingConnection);
 return(existingConnection);
 } 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) {
 throw new SQLException("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) {}
 // Someone freed up a connection, so try again.
 return(getConnection());
// 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
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
 // to free up.
// This explicitly makes a new connection. Called in
// the foreground when initializing the ConnectionPool,
// and called in the background when running.
private Connection makeNewConnection()
 throws SQLException {
 try {
 // Load database driver if not already loaded
 Class.forName(driver);
 // Establish network connection to database
 Connection connection =
 DriverManager.getConnection(url, username, password);
 return(connection);
 } catch(ClassNotFoundException cnfe) {
 // Simplify try/catch blocks of people using this by
 // throwing only one exception type.
 throw new SQLException("Can't find class for driver: " +
 driver);
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
public synchronized String toString() {
 String info =
 "ConnectionPool(" + url + "," + username + ")\n" +
 ", available=" + availableConnections.size() + "\n" +
 ", busy=" + busyConnections.size() + "\n" +
 ", max=" + maxConnections;
 return(info);
ScoPool Class (singleton to access the connection pool)
package sco;
public class ScoPool extends ConnectionPool {
private ScoPool pool = null;
private ScoPool() {
 super(); // Call parent constructor
public static synchronized ScoPool getInstance() {
 if(pool == null) {
 pool = new ScoPool();
 return(pool);
}Please help a newbie.

Figured it out.
package sco;
import java.sql.SQLException;
public class ScoPool extends ConnectionPool {
private static ScoPool pool;
private ScoPool(String driver, String url, String username, String password,
 int initialConnections, int maxConnections, boolean waitIfBusy) throws SQLException {
 super(driver, url, username, password, initialConnections, maxConnections, waitIfBusy); // Call parent constructor
public static synchronized ScoPool getInstance() {
 if(pool == null) {
 String driver = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
 String url = "jdbc:microsoft:sqlserver://MIM-W0432:1433;DatabaseName=sco";
 String username = "sco_user";
 String password = "123";
 int initCon = 5;
 int maxCon = 10;
 boolean waitIfBusy = true;
 try {
 pool = new ScoPool(driver, url, username, password, initCon, maxCon, waitIfBusy);
 catch(SQLException sqle) {
 return pool;
}

Unable to start the Universal Connection Pool error

Hi,
I am trying to deploy two instances of one and the same web application on Tomcat 6. I have application test.war, I have copied and renamed it to test2.war and moved both wars in Tomcat' webapps folder. One of those (which Tomcat decides to start first) correctly gets connection from PoolDataSourceFactory.getPoolDataSource() and works fine, but the second throws this exception while trying to get database connection.
Please help,
Thanks
java.sql.SQLException: Unable to start the Universal Connection Pool: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:276)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:646)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:613)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:607)
at com.avalonsql.core.db.connection.ConnectionWrapper.<init>(ConnectionWrapper.java:26)
... 31 more
Caused by: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:247)
... 35 more
Caused by: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:421)
at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:389)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:149)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:242)
... 35 more
Caused by: java.security.PrivilegedActionException: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
at java.security.AccessController.doPrivileged(Native Method)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:136)
... 36 more
Caused by: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl$2.run(UniversalConnectionPoolManagerMBeanImpl.java:142)
... 38 more

I was getting the following exception.. However after setting the property ConnectionFactoryClassName, it went off..
Caused by: java.sql.SQLException: Invalid Universal Connection Pool configuration: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
 at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
 at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
 at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:523)
 at oracle.ucp.admin.UniversalConnectionPoolManagerBase.createConnectionPool(UniversalConnectionPoolManagerBase.java:554)
 ... 92 more
Caused by: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
 at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
 at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
 at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2457)
 at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:386)
 ... 93 more
Caused by: java.lang.ClassNotFoundException:
 at java.lang.Class.forNameImpl(Native Method)
 at java.lang.Class.forName(Class.java:169)
 at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2444)
 ... 94 more
Edited by: user7953709 on Aug 26, 2011 1:08 AM

Issue in setting up a connection pool in Glassfish

Hello,
I'm having an issue in setting up a connection pool in Glassfish. Previously I did it succesfully when I installed Glassfish in a Windows Server machine, but now I'm trying to do the same thing on a Linux machine and it's not working.
Glassfish version is: Glassfish server open source edition 3.1.1 (build 12)
The machine is a AWS machine running Amazon Linux AMI
Oracle Database is Oracle 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option
The Oracle client installed on the machine is Release 11.2.0.3.0 Production
Java version is: Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
I've created the pool with the following options:
Resource Type: javax.sql.DataSource
Datasource classname: oracle.jdbc.pool.OracleDataSource
And as additional properties (apart from User and Password) I put as URL jdbc:oracle:oci8:@EVOREAD
The TNS file is correct and I can connect without any problem using sqlplus. I already copied the ojdbc6.jar in the /opt/Glassfish3/Glassfish/lib folder and I already restarted Glassfish server. Basically I did all the same steps that I did in the Windows machine, but in the Linux machine I always receive the following error:
java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path no ocijdbc11 in java.library.path
I needed to create also a connection pool to a MySql Database and basically I did exactly the same steps (apart of course using all the parameters needed for MySql and the proper connector) and it worked immediately.
Anyone can help me?

You are using an OCI driver? You can either revert to using a thin client, or install the SQL client binaries and add its lib directory to the LD_LIBRARY_PATH.

Setting up Connection Pool in sun app server 8.1 with SQL server 2000

Hello,
I am trying to set up a connection pool & data source for SQL server 2000 (MSDE 2000).
Here is what I attempted to do:
I have a pool data source in a jar file called poll.jar and I copied it to C:\sun\Appserver\lib (Install dir\lib)
com.microsoft.mspool.PoolDataSource is the pool data source class.
In the Admin console, JDBC>Connection pools. Selected NEW and made the following entries.
GENERAL SETTINGS
Name: MsPool
Datasource class name : com.microsoft.mspool.PoolDataSource
Resource type: javax.sql.DataSource
POOL SETTINGS: default values
CONNECTION VALIDATION: default values
TRANSACTION ISOLATION: default values
PROPERTIES:
DataSourceName:PoolDataSource
NetworkProtocol:tcp
DatabaseName: myDB
Password:User specific
user:User specific
server: localhost
PortNumber:1433
I get the following error when I ping:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.microsoft.mspool.PoolDataSource.
Can any one help me if have a solution?
Thanks in advance.
mag

You need to copy your jar to ${AS_INSTALL}/domains/domain1/lib/ext (replace domain1 by your
domain). Another option is to leave the jar in ${AS_INSTALL}/lib and add a entry in the classpath-suffix element of your domain.xml.
thanks,
:aditya

Urgent...Help Needed.1. Helper Class 2. Connection Pool

Hello,
1. There are few helper classes which has to be
shared b/w session and entity beans. But it
seems,state of the object is not transfered to entity
bean though the class has implemented Serializable
interface. I have archived all the helper class and
copied to j2ee\home\lib directory. The same jar file
is made accessible to server via updating <library-
path> in j2ee/home/config/application.xml file.
2. How can i utilise connection pooling in oc4j. In data-sources.xml, i am using
"OracleConnectionPoolDataSource" class. But i feel that connection pool is not utilised coz server hangs in the middle of the retrieval.
The value of max-connections is 50.
We are actually migrating from Weblogic 5.1.0 to Oracle 9i AS. In weblogic, we had given 10 max connections in weblogic.properties,it is working fine. But i dont understand why it is not working in 9i AS though the max-connections is 50.
Kindly let me know the solution at the earliest as it is very urgent to get the program running...
Thanx and Regards,
Achyuth

Hi,
hopefully I can help you.
1. There are few helper classes which has to be ...We have just the same constellation. We have put the HelperClasses in the
J2EE/home/lib dir, NOT specifying it in the application.xml. So everything works fine.
The only thing: never, again: never put these files within WEB-INF and the lib-dir.
With the HelperClasses in both we have only faced massive problems, mostly ClasCastExceptions.
We had once all the helperClasses within J2EE/home/applications/lib, but this requires to
specify this dir within the orion-application.xml within the appl dir in applications-deployment.
It also worked fine.
2. How can i utilise connection pooling in oc4j. In data-sources.xml, i am using ...I'm not sure of this, but I think, the container handles Connection Pooling, no matter what Factory you
specify. But I think, the Class hasn't to be OracleConnectionPool ... but I have to check this (right now
I have no access to our datasource.xml ..)
cu
ed

Setting up a connection pool to ms sql database

Hi
I am trying to create a connection pool to talk to an MSSQL database, and could not manage to ping the DB (Operation 'pingConnectionPool' failed in 'resources' Config Mbean.) .
What set of properties need to be included for connection pool to an MS SQL DB?
your help is very much appreciated,
Yhank you
orms2004

package coreservlets;
import java.sql.*;
import java.util.*;
/** A class for preallocating, recycling, and managing
* JDBC connections.
* 
* Taken from Core Servlets and JavaServer Pages
* from Prentice Hall and Sun Microsystems Press,
* http://www.coreservlets.com/.
* © 2000 Marty Hall; may be freely used or adapted.
public class ConnectionPool implements Runnable {
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)
 throws SQLException {
 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();
 for(int i=0; i<initialConnections; i++) {
 availableConnections.addElement(makeNewConnection());
public synchronized Connection getConnection()
 throws SQLException {
 if (!availableConnections.isEmpty()) {
 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.
 if (existingConnection.isClosed()) {
 notifyAll(); // Freed up a spot for anybody waiting
 return(getConnection());
 } else {
 busyConnections.addElement(existingConnection);
 return(existingConnection);
 } 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) {
 throw new SQLException("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) {}
 // Someone freed up a connection, so try again.
 return(getConnection());
// 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
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
 // to free up.
// This explicitly makes a new connection. Called in
// the foreground when initializing the ConnectionPool,
// and called in the background when running.
private Connection makeNewConnection()
 throws SQLException {
 try {
 // Load database driver if not already loaded
 Class.forName(driver);
 // Establish network connection to database
 Connection connection =
 DriverManager.getConnection(url, username, password);
 return(connection);
 } catch(ClassNotFoundException cnfe) {
 // Simplify try/catch blocks of people using this by
 // throwing only one exception type.
 throw new SQLException("Can't find class for driver: " +
 driver);
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
public synchronized String toString() {
 String info =
 "ConnectionPool(" + url + "," + username + ")" +
 ", available=" + availableConnections.size() +
 ", busy=" + busyConnections.size() +
 ", max=" + maxConnections;
 return(info);
}taken from:
http://archive.coreservlets.com/Chapter18.html

Cant create connection Pool for MS SQL Server 2000 with Microsoft Driver

i am using bea weblogic server 6.1, i cant create connection pool while using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft website. when
i give the following class name for JDBC driver and the connection url and click
apply while selecting the available server, a number of exception appears in default
server (that is the connection pool cannot be created..... cannot load the driver
class).
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple application in Jbuilder
7.0 the application runs successfully and fetches the data deom MS SQL database
but in at Bea connection Pool is not created with these settings. i do give appropriate
username and password in properties field in connection pool. Thankx for any help!

khabbab wrote:
That was the original code part from "startweblogic" :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
echo off
and i changed it to :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;D:\Program Files\Microsoft
SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL
Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server
2000 Driver for JDBC\lib\mssqlserver.jar;I suggest moving or copying the three ms driver jars to a directory that has no blanks
in it so the classpath doesn't have blanks in it. Ie:
go to the "D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib"
directory and do this:
mkdir D:\microsoft_jdbc_driver
cp *.jar D:\microsoft_jdbc_driver
Then make the classpath include D:\microsoft_jdbc_driver\msbase.jar etc.
Joe
>
>
echo off
when i save and run the bat file, server appears then disappears.
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???Show me what change you made to the startweblogic file.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!

How to make connection Pool for standalone Application

hi
I have got an application to craete a stadalone appliaction for connection pool.But it is taking m more time to create the Connection and fetch the data.
import java.sql.*;
import java.util.*;
/** A class for preallocating, recycling, and managing
* JDBC connections.
* 
* Taken from Core Servlets and JavaServer Pages
* from Prentice Hall and Sun Microsystems Press,
* http://www.coreservlets.com/.
* © 2000 Marty Hall; may be freely used or adapted.
public class ConnectionPool implements Runnable {
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)
 throws SQLException {
 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();
 for(int i=0; i<initialConnections; i++) {
 availableConnections.addElement(makeNewConnection());
public synchronized Connection getConnection()
 throws SQLException {
 if (!availableConnections.isEmpty()) {
 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.
 if (existingConnection.isClosed()) {
 notifyAll(); // Freed up a spot for anybody waiting
 return(getConnection());
 } else {
 busyConnections.addElement(existingConnection);
 return(existingConnection);
 } 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) {
 throw new SQLException("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) {}
 // Someone freed up a connection, so try again.
 return(getConnection());
// 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.
public void makeBackgroundConnection() {
 connectionPending = true;
 try {
 Thread connectThread = new Thread(this);
 connectThread.start();
 } catch(OutOfMemoryError oome) {
 // Give up on new connection
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
 // to free up.
// This explicitly makes a new connection. Called in
// the foreground when initializing the ConnectionPool,
// and called in the background when running.
public Connection makeNewConnection()
 throws SQLException {
 try {
 // Load database driver if not already loaded
 Class.forName(driver);
 // Establish network connection to database
 Connection connection =
 DriverManager.getConnection(url, username, password);
 return(connection);
 } catch(ClassNotFoundException cnfe) {
 // Simplify try/catch blocks of people using this by
 // throwing only one exception type.
 throw new SQLException("Can't find class for driver: " +driver);
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();
public 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
public synchronized String toString() {
 String info =
 "ConnectionPool(" + url + "," + username + ")" +
 ", available=" + availableConnections.size() +
 ", busy=" + busyConnections.size() +
 ", max=" + maxConnections;
 return(info);
}///// The Calling Class is below---------/////////////////
import java.util.*;
import java.sql.*;
public class dbConnection
 public static void main(String[] args)
 String driver="oracle.jdbc.driver.OracleDriver";
 String username="ETS";
 String password="ETS";
 String url="jdbc:oracle:thin:@192.168.47.10:1521:ETS";
 int initialConnections=10;
 int maxConnections=50;
 boolean waitIfBusy=false;
 Connection con=null;
 Statement stmt = null;
 ResultSet rs = null;
 try
 System.out.println("Before constructory "+new java.util.Date());
 ConnectionPool pool=new ConnectionPool(driver,url,username,password,initialConnections,maxConnections,waitIfBusy);
 System.out.println("After constructory "+new java.util.Date());
 con=pool.makeNewConnection();
 System.out.println("After Connection pool "+new java.util.Date());
 String sql="select * from emp_master";
 stmt = con.createStatement();
 rs = stmt.executeQuery(sql);
 while(rs.next()) {
 int login1=rs.getInt("emp_code");
 System.out.println("Employee Code is "+login1);
 System.out.println("check 2");
 String pass=rs.getString("PASSWORD");
 System.out.println("Pass Word is "+pass);
 }catch(Exception e)
 System.out.println("Exception is "+e);
 finally {
}

I once created a connection pool programatically with Apache DBCP API. It didnt took more than 10 lines. Unforchunetly I dont have to code with me now.
But If I remember right there is a sample code for that in the Apache Commans DBCP documentation.

BI Admin Tool - Setting connection pool via shell script - Is it possible?

Hi,
Here's the problem I am trying to solve.
I am using a J2EE application that uses OBIEE for reporting.
The *.rpd file is installed at a particular location when our J2EE product is installed.
I then copy the *.rpd file to the BI home on a different server using a shell script.
The shell script that deploys the *.rpd file does the following:
1. Shuts down BI processes that are running
2. Deletes the old *.rpd file
3. Copies the new *.rpd file
4. Starts all BI processes
I am happy with the way we have automated this process, but would like to take it one step further.
The *.rpd file does not have the connection pool hard-coded in it. And we want to keep it that way.
What we would like to do is - pass the connection pool parameters to the shell script (that is used for *.rpd's deployment) and have it automatically update the *.rpd file. Is it possible to do this at all? How do we go about accomplishing this?
Or in other words - Is there a way to update the connection pools WITHOUT hard-coding it in the *.rpd file or WITHOUT using the BI Administration Tool.
Currently, we manually update the connection pools in the Physical Layer using the Oracle BI Administration Tool.
The version of BI Administration Tool being used is 10.1.3.3.1 installed on a Microsoft Windows XP Professional SP2 machine. The BI Server itself is running on an Oracle Enterprise Linux 4.0 box.
Do let me know if you need more information that would help answer this question.
Thank you.

Thank you - fiston and Gagan.
I am going with fiston's solution - since it is easier to implement. I am on the QA team and the automated deployment is to lessen QA's deployment time.
While one of our developer's said that she prefer's Gagan's solution - it would be over-kill to make changes to the application's schema for the said purpose.
I will further make another post as to whether or not the automated deployment worked for us.

Copy Connection Pool

Similar Messages

Maybe you are looking for