Discussions

Performance and scalability: Accessing the Connection pool

  1. Accessing the Connection pool (1 messages)

    Hi,
    I have created a connection pool in Weblogic.I want to access the pool from my client.

    There is one remote interface which is defined as follows

    ResultSet executeDataBaseQuery(Connection conn,String queryString) throws RemoteException;


    My bean implements this interface and sends back the resultset
    as follows

    public ResultSet executeDataBaseQuery(Connection conn,String queryString)
    {
    Statement stmt=null;
    ResultSet result=null;
    try
    {
    if (conn==null)
    {
    System.out.println("Connection is null");
    }

    System.out.println("Inside bean first stmt");
    stmt = conn.createStatement();
    result=stmt.executeQuery(queryString);
    stmt.close();
    } catch(SQLException e)

    {
    System.out.println("Exception inside JDBCConnector.executeDataBaseQuery"+e.getErrorCode());
    e.printStackTrace();
    return null;
    }
    return result;


    The client code is as follows

    public Connection getConn() throws ClassNotFoundException, InstantiationException, IllegalAccessException
    {

    try
    {
    Connection conn = null;
    Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    conn = DriverManager.getConnection("jdbc:weblogic ool raclePool");
    System.out.println("Got a connection from JDBC Pool");
    if (conn == null)
    {
    System.out.println("Connection is null in the function getConn()");
    }
    return conn;

    }
    catch(Exception e)
    {
    System.out.println("Could not get free Connection from the pool "+e.getMessage());
    e.printStackTrace();
    return null;
    }

    }


    When I call the above getconn() from the application it gives error message as

    "Pool connect failed"

    I changed the txdatasource in the properties file, but still am not able to solve the problem. Am using weblogic 5.1


    Could U please tell me where the problem is
  2. Accessing the Connection pool[ Go to top ]

    Did you try posting your problem on newsgroups.bea.com?