Maximum no. of XA Connection pools

Hi,
Is there any limitation on number of XA Connection pools (NOT number of connections in a pool)
that can be created in a weblogic 8.1 server ?
Thanks in advance,
Reji

Internal DHCP is only for small networks and lab use.
We do not recommend to use it for any large deployment, please use an external DHCP server instead.
This is documented:
The internal DHCP server was introduced initially for branch offices where an external DHCP server is not available. It is designed to support a small wireless network with less than ten APs that are on the same subnet.
It is not a full-blown general purpose DHCP server. It only supports limited functionality and will not scale in a larger deployment.
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html#Internal-DHCP
While you can configure multiple DHCP pools and it can work fine for some time, in my experience I have seen this internal DHCP server stop leasing IP address with 2 or 3 class C networks configured.
My recommendation, use an external DHCP server.

Similar Messages

SOA Suite 11g - Connection Pools constantly getting suspended...

Hi,
I have composites, bpel processes using database adapters.
*I keep getting "+Pool mds-owsm is Suspended, cannot allocate resources to applications+" and " Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications.." in soa_server logg.*
There are no errors in db trace logs. It seems related to the WLS JDBC data sources, they are constantly getting suspended.
After a while no new connections can be created, and managed soa server hangs. Restart is the only "solution" for now...
I have increased "Maximum Capacity" on the connection pool to 300 without success.
Any ideas, pointers, help appreciated.
+<Jan 6, 2011 8:55:02 AM CET> <Error> <org.quartz.impl.jdbcjobstore.JobStoreCMT> <BEA-000000>+
+<ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'soaNonManagedDS': java.sql.SQLException:+
Could not retrieve datasource via JNDI url 'jdbc/SOALocalTxDataSource'*
weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications..org.quartz.JobPersistenceException:
Failed to obtain DB connection from data source 'soaNonManagedDS': java.sql.SQLException:
Could not retrieve datasource via JNDI url 'jdbc/SOALocalTxDataSource' weblogic.jdbc.extensions.PoolDisabledSQLException:
weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications..
+[See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/SOALocalTxDataSource'+
+weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications..]+
+     at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:167)+
+     at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3167)+
+     at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3811)+
+     at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3847)+
+<Jan 10, 2011 6:22:47 AM CET> <Warning> <oracle.wsm.resources.policyaccess> <WSM-06001> <Error obtaining Policy Set.+
oracle.wsm.policymanager.PolicyManagerException: WSM-02079 : Failed to connect to Policy Manager instance due to error "java.rmi.Rem
oteException: EJB Exception: ; nested exception is:
oracle.mds.exception.MDSRuntimeException: MDS-00001: exception in Metadata Services layer
MDS-00001: exception in Metadata Services layer
+weblogic.common.resourcepool.ResourceDisabledException: Pool mds-owsm is Suspended, cannot allocate resources to applications..".+ at oracle.wsm.policymanager.client.PolicyAccessServiceDelegate.getPolicies(PolicyAccessServiceDelegate.java:136)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread$1.run(PolicyCacheImpl.java:714)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread$1.run(PolicyCacheImpl.java:711)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:7
+9)+
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread.run(PolicyCacheImpl.java:710)
Caused By: java.rmi.RemoteException: EJB Exception: ; nested exception is:
oracle.mds.exception.MDSRuntimeException: MDS-00001: exception in Metadata Services layer
MDS-00001: exception in Metadata Services layer
+weblogic.common.resourcepool.ResourceDisabledException: Pool mds-owsm is Suspended, cannot allocate resources to applications..+ at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl_1033_WLStub.getPolicies
AsStrings(Unknown Source)
at oracle.wsm.policymanager.client.PolicyAccessServiceDelegate.getPolicies(PolicyAccessServiceDelegate.java:132)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread$1.run(PolicyCacheImpl.java:714)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread$1.run(PolicyCacheImpl.java:711)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:7
+9)+
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$BackTracingSynchronizationThread.run(PolicyCacheImpl.java:710)
Caused By: oracle.mds.exception.MDSRuntimeException: MDS-00001: exception in Metadata Services layer
MDS-00001: exception in Metadata Services layer
weblogic.common.resourcepool.ResourceDisabledException: Pool mds-owsm is Suspended, cannot allocate resources to applications..
at oracle.mds.internal.persistence.db.BaseReposAccess.<init>(BaseReposAccess.java:360)
at oracle.mds.internal.persistence.db.shredded.ShreddedReposAccess.<init>(ShreddedReposAccess.java:274)

Hi again,
Thanks for the input, to answer your questions Anuj:
Database
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
Middleware
Oracle SOA Management 11.1.1.3.0
Oracle SOA Infrastructure 11.1.1.3.0
Oracle SOA Suite Patch 11.1.1.3.0
Oracle SOA Common Adapters 11.1.1.3.0
Enterprice Manager 11g Fusion Middleware Control 11.1.1.3.0
And..
Connection Creation Retry Frequency is set to "10"
Test Connections On Reserve is enabled.
Login Delay is stil set to 0 (by default), why should this value be other than 0?, wouldn't increasing it to 10 heavily slow down message-processing..?
DB and SOA are not on same machine, no n/w issues.
Regards
Anders.

Maximum number of connection pools?

Hello,
I'm running WL 5.1, sp11 on Solaris with Oracle 8.1.7. I was
wondering, is there a maximum number of connection pools allowed by
weblogic? Or does it not matter so long as the sum of all the max
connections in each pool is less than the max connections oracle will
let you make simultaneously?
Thanks, Dave

Hi. There is no limit to the number of pools weblogic will let you
make. The number of connections Oracle will let you have is
between them and you. :-)
Joe
"D. Alvarado" wrote:
Hello,
I'm running WL 5.1, sp11 on Solaris with Oracle 8.1.7. I was
wondering, is there a maximum number of connection pools allowed by
weblogic? Or does it not matter so long as the sum of all the max
connections in each pool is less than the max connections oracle will
let you make simultaneously?
Thanks, Dave

RCA Connection Pool idle Time-Out takes no effect !

My question description goes here.
According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
What's your comments on it?
P.S.
I am using Sun Java System Application Server 8.1.
Thanks in advance!
BRs
/Leo

I have had following test to ensure I sent out notification to listener.
[#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
It's in managed env!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter matchManagedConnections() !|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
try to find a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Found a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
tearDown() is called, the application-level connection is released!|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Start calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
start to notify the listener the completeness of connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
notify the listener the completeness of connection successfully.|#]
Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

PI' RFC Connection pool doubt.

Hi PI exports:
i have a doubt about pi' RFC Connection pool ,pi RFC receive channel can set the conn pool size ,but when start the rfc receiver channel ,is there always only one Connection pool ,or there is only one Connection pool instance?
thinks
Edited by: kevin liang on Oct 19, 2009 6:45 AM

Hi,
Connection poolins size means how many number of connection you want to make open to send data to ECC, We can define maximum number of connection in Receiver RFC Adapter,Go to additional parameters section and define Max Number of connection give the number there,thats it.Internally it works as Connection poolin mechanism.
Regards,
Raj

Connection pool for ldap

Hi
My application is an interface to ldap directory. I have not used any ldap open source api to retrieve data from ldap. I have written connection pool that will help the application to connect to the ldap. It's working fine, but it's creating threads which are not invited.
ConnectionPool class takes care of the connection storage and creation, while Housekeeping thread relases these connection when idle after a given time.
Can someone please help in finding the problem in the code that creates additional threads.
package com.ba.cdLookup.manager;
import com.ba.cdLookup.exception.CDLookupException;
import com.ba.cdLookup.server.CdLookupProperties;
import java.util.Vector;
import javax.naming.Context;
import javax.naming.NamingException;
public class HouseKeeperThread extends Thread {
         * Apache Logger to log erro/info/debug statements.
    protected static org.apache.commons.logging.Log log = org.apache.axis.components.logger.LogFactory
         .getLog(HouseKeeperThread.class.getName());
    private static HouseKeeperThread houseKeeperThread;
         * Close all connections existing.
         * @param connections
         *                void
    private void closeConnections(Vector connections) {
     String methodIdentifier = "closeConnections";
     int numOfConn = connections.size();
     try {
         for (int i = 0; i < numOfConn; i++) {
          Context context = (Context) connections.get(i);
          if (context != null) {
              context.close();
              context = null;
              connections.remove(i);
              numOfConn--;
              log.info(" connection name:" + context
                   + " removed. Threadcount =" + (connections.size()));
     } catch (NamingException e) {
         String errMsg = "CDLdapBuilder connect() - failure while releasing connection "
              + " Exception is " + e.toString();
         log.error(errMsg);
     } catch (Exception e) {
         String errMsg = "CDLdapBuilder connect() - failure while releasing connection "
              + " Exception is " + e.toString();
         log.error(errMsg);
         * Thread run method
    public void run() {
     String methodIdentifier = "run";
     try {
         while(true){
          log.debug("house keeping :" + this + " ---sleep");
          //sleep(100000);
          log.debug("house keeping :" + this + " startd after sleep");
           sleep(CdLookupProperties.getHouseKeepConnectionTime());
          ConnectionPool connectionPool = ConnectionPool
               .getConnectionPool();
          Vector connList = connectionPool.getAvailableConnections();
          closeConnections(connList);
     } catch (CDLookupException cde) {
         log.error(methodIdentifier + " " + cde.getStackTrace());
     } catch (InterruptedException ie) {
         log.error(methodIdentifier + " " + ie.getStackTrace());
     * @param connectionPool
     * @return
     * Thread
    public static Thread getInstance() {
     if(houseKeeperThread==null){
         houseKeeperThread = new HouseKeeperThread();
     return houseKeeperThread ;
package com.ba.cdLookup.manager;
import com.ba.cdLookup.exception.CDLookupException;
import com.ba.cdLookup.server.CdLookupProperties;
import com.ba.cdwebservice.schema.cdLookupPacket.LookupFailureReasons;
import java.util.Properties;
import java.util.Vector;
import javax.naming.Context;
import javax.naming.NamingException;
import javax.naming.directory.DirContext;
import javax.naming.directory.InitialDirContext;
* ConnectionPool class manages, allocates LDAP connections. It works as a lazy
* binder and retrieves connections only when required. It doesn't allow
* connection greater then the maximum connection stated.
* To retrieve a connection the singelton method getConnectionPool is to used,
* which retruns thread safe singleton object for the connection.
public class ConnectionPool implements Runnable {
    private int initialConnections = 0;
    private int maxConnections = 0;
    private boolean waitIfBusy = false;
    private Vector availableConnections, busyConnections;
    private boolean connectionPending = false;
    private static int threadCount = 0;
         * classIdentifier
    private final String classIdentifier = "ConnectionPool";
         * Apache Logger to log erro/info/debug statements.
    protected static org.apache.commons.logging.Log log = org.apache.axis.components.logger.LogFactory
         .getLog(CDLdapBuilder.class.getName());
         * To get the attribute a systemaccessfor out of the search result
    private String vendorContextFactoryClass = "com.sun.jndi.ldap.LdapCtxFactory";// "com.ibm.jndi.LDAPCtxFactory";
         * context factory to use
    private String ldapServerUrl = "LDAP://test.ldap.com"; // default ldap
         * server live used by default
    private String searchBase;
         * environment properties.
    private Properties env;
         * DirContext
    private javax.naming.directory.DirContext ctx;
         * default search base to be used in Corporate Directory searches
    private String defaultSearchBase = "dc=Pathway";
         * search criteria
    private String searchAttributes;
         * search filter to retrieve data from CD
    private String searchFilter;
         * CorporateDirectoryLookup Constructor
         * <p>
         * loads the setup parameters from the properties file and stores them
         * Makes a connection to the directory and sets default search base
         * @throws CDLookupException
         * @throws CDLookupException
    private ConnectionPool() throws CDLookupException {
     this.maxConnections = CdLookupProperties.getMaxConnection();// maxConnections;
     this.initialConnections = CdLookupProperties.getInitialConnection();
     this.waitIfBusy = CdLookupProperties.isWaitIfBusy();
     this.searchBase = CdLookupProperties.getDefaultSearchBase();
     //for local env testing
//      this.maxConnections = 5;
//      this.initialConnections = 1;
//      this.waitIfBusy = true;
         * For keeping no of connections in the connection pool if
         * (initialConnections > maxConnections) { initialConnections =
         * maxConnections; }
     availableConnections = new Vector(maxConnections);
     busyConnections = new Vector(maxConnections);
     for (int i = 0; i < maxConnections; i++) {
         availableConnections.add(makeNewConnection());
         * ConnectionPoolHolder provide Thread safe singleton
         *         instance of ConnectionPool class
    private static class ConnectionPoolHolder {
         * connection pool instance
     private static ConnectionPool connectionPool = null;
         * If no ConnectionPool object is present, it creates instance of
         * ConnectionPool class and initiates thread on that.
         * @return ConnectionPool Returns singleton object of ConnectionPool
         *         class.
         * @throws CDLookupException
     private static ConnectionPool getInstance() throws CDLookupException {
         if (connectionPool == null) {
          connectionPool = new ConnectionPool();
          new Thread(connectionPool).start();
          // Initiate house keeping thread.
          HouseKeeperThread.getInstance().start();
         return connectionPool;
         * Returns singleton object of ConnectionPool class.
         * @return ConnectionPool
         * @throws CDLookupException
    public static ConnectionPool getConnectionPool() throws CDLookupException {
     return ConnectionPoolHolder.getInstance();
         * getConnection retrieves connections to the corp directory. In case
         * there is no available connections in the pool then it'll try to
         * create one, if the max connection limit for the connection pool
         * reaches then this waits to retrieve one.
         * @return Context
         * @throws CDLookupException
    public synchronized Context getConnection() throws CDLookupException {
     String methodIdentifier = "getConnection";
     if (!availableConnections.isEmpty()) {
         int connectionSize = availableConnections.size() - 1;
         DirContext existingConnection = (DirContext) availableConnections
              .get(connectionSize);
         availableConnections.remove(connectionSize);
                 * 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 == null) {
          notifyAll(); // Freed up a spot for anybody waiting
          return (getConnection());
         } else {
          busyConnections.add(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 CDLookupException("Connection limit reached", 0);
                 * 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) {
          String errMsg = "Exception raised =" + ie.getStackTrace();
          log.error(errMsg);
          throw new CDLookupException(classIdentifier, methodIdentifier,
               errMsg, ie);
         // connection freed up, 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);
         log.debug("background thread created");
         connectThread.start();
     } catch (OutOfMemoryError oome) {
         log.error("makeBackgroundConnection ="+ oome.getStackTrace());
         * Thread run method
    public void run() {
     String methodIdentifier = "run";
     try {
         Context connection = makeNewConnection();
         synchronized (this) {
          availableConnections.add(connection);
          connectionPending = false;
          notifyAll();
     } catch (Exception e) { // SQLException or OutOfMemory
         // Give up on new connection and wait for existing one
         // to free up.
         String errMsg = "Exception raised =" + e.getStackTrace();
         log.error(errMsg);
         * This explicitly makes a new connection. Called in the foreground when
         * initializing the ConnectionPool, and called in the background when
         * running.
         * @return Context
         * @throws CDLookupException
    private Context makeNewConnection() throws CDLookupException {
     String methodIdentifier = "makeNewConnection";
     Context context = null;
     env = new Properties();
     log.debug("inside " + methodIdentifier);
     try {
         env.put(Context.INITIAL_CONTEXT_FACTORY,
              getVendorContextFactoryClass());
         env.put(Context.PROVIDER_URL, getLdapServerUrl());
         env.put("com.sun.jndi.ldap.connect.pool", "true");
         context = new InitialDirContext(env);
     } catch (NamingException e) {
         String errMsg = "CDLdapBuilder connect() - failure while attempting to contact "
              + ldapServerUrl + " Exception is " + e.toString();
         throw new CDLookupException(classIdentifier, methodIdentifier,
              errMsg, e, LookupFailureReasons.serviceUnavailable);
     } catch (Exception e) {
         String errMsg = "CDLdapBuilder connect() - failure while attempting to contact "
              + ldapServerUrl + " Exception is " + e.toString();
         throw new CDLookupException(classIdentifier, methodIdentifier,
              errMsg, e, LookupFailureReasons.serviceUnavailable);
     log.info("new connection :" + (threadCount++) + " name =" + context);
     log.debug("exit " + methodIdentifier);
     return context;
         * releases connection to the free pool
         * @param context
    public synchronized void free(Context context) {
     busyConnections.remove(context);
     availableConnections.add(context);
     // Wake up threads that are waiting for a connection
     notifyAll();
         * @return int give total no of avail connections.
    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 <I>required</I> 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();
         * Close all connections existing.
         * @param connections
         *                void
    private void closeConnections(Vector connections) {
     String methodIdentifier = "closeConnections";
     try {
         for (int i = 0; i < connections.size(); i++) {
          Context context = (Context) connections.get(i);
          if (context != null) {
              log.info(" connection name:" + context
                   + " removed. Threadcount =" + (threadCount++));
              context.close();
              context = null;
     } catch (NamingException e) {
         String errMsg = "CDLdapBuilder connect() - failure while attempting to contact "
              + ldapServerUrl + " Exception is " + e.toString();
         log.error(errMsg);
    public synchronized String toString() {
     String info = "ConnectionPool(" + getLdapServerUrl() + ","
          + getVendorContextFactoryClass() + ")" + ", available="
          + availableConnections.size() + ", busy="
          + busyConnections.size() + ", max=" + maxConnections;
     return (info);
         * @return the defaultSearchBase
    public final String getDefaultSearchBase() {
     return defaultSearchBase;
         * @param defaultSearchBase
         *                the defaultSearchBase to set
    public final void setDefaultSearchBase(String defaultSearchBase) {
     this.defaultSearchBase = defaultSearchBase;
         * @return the ldapServerUrl
    public final String getLdapServerUrl() {
     return ldapServerUrl;
         * @param ldapServerUrl
         *                the ldapServerUrl to set
    public final void setLdapServerUrl(String ldapServerUrl) {
     this.ldapServerUrl = ldapServerUrl;
         * @return the vendorContextFactoryClass
    public final String getVendorContextFactoryClass() {
     return vendorContextFactoryClass;
         * @param vendorContextFactoryClass
         *                the vendorContextFactoryClass to set
    public final void setVendorContextFactoryClass(
         String vendorContextFactoryClass) {
     this.vendorContextFactoryClass = vendorContextFactoryClass;
     * @return the availableConnections
    public final Vector getAvailableConnections() {
        return availableConnections;
}

Hi,
As the connection pool implmentation has the bug of not extending more than the min size, workaround I use is MIN_CONN=100 and MAX_CONN=101,and just waiting for the bug to get fixed. (using Netscape SDK for java4.0)

Connection pool SAPPool is exhausted

hi..
I am getting this following error in my application
om.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool SAPPool is exhausted. The current pool size limit (max connections) is 50 connections.
at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5366)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6324)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6269)
at com.sap.mw.jco.JCO.getClient(JCO.java:8536)
at com.tcs.interfaces.sapConnectionUtility.JCOClient_Connection.connectToSAP(JCOClient_Connection.java:21)
at com.tcs.interfaces.wifi.outbound.DisablingWifi.disableWifi(DisablingWifi.java:110)
at com.tcs.interfaces.jco.StartJob.run(StartJob.java:68)
at java.lang.Thread.run(Thread.java:636)
The front end PMS (Property Management System) - SAP Customised product is unable to connect with the JCo Middleware server because of the above mentioned error.
The thing is that in java application I have set the maximum pool size (SAPPool) to 50.
Still we are facing this error twice a week.
Is there any kind of setting in SAP server side where JCo RFC connection limits can be set ?
Can any pls help in this regard.

After reading the url that you have pointed out: i have a question our from my
curiosity:
is there any overhead that does have if connection pool is very high say 100 and
the required is say like 70.
Thank You very much.
Rob Woollen <[email protected]> wrote:
I usually recommend that for production systems. There's some info here:
http://edocs.bea.com/wls/docs81/perform/WLSTuning.html#1123237
-- Rob
Mike wrote:
Thanks Rob,
is it a good idea to make InitialCapacity equal to the MaxCapacity?
say making InitialCapacity = MaxCapacity = 50
while thread count is also = 50
Rob Woollen <[email protected]> wrote:
Typically thread count = connection pool size is a good starting point.
You might want thread count > connection pool size if you want to
throttle work to the database, or if you have some threads which will
never require a db connection.
You might want connection pool size > thread count if remote clients
are
starting transactions or reserving connections. Another case is if
a
single thread starts multiple transactions.
-- Rob
Mike wrote:
what is the relationship between thread count and connection pool
Eg, if i have a thread count of =50
and connection pool = 36
how does these 2 parameters work together ?
is there any equation between the 2 ?
--Mike

Connection pool exausted

Dear all,
I am new to j2ee environment.
RFC from PI Java stack to PI ABAP stack failing intermittently. Error message: Error while lookupProblem when calling an adapter by using communication channel CC_RFC_LookUp (Party: , Service: PPICLNT900, Object ID: 2e663396395c3213aaecd4e7746a8ddd) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_RFC_LookUp]2e663396395c3213aaecd4e7746a8ddd is exhausted. The current pool size limit (max connections) is 1 connections.'. Cause Exception: 'error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_RFC_LookUp]2e663396395c3213aaecd4e7746a8ddd is exhausted. The current pool size limit (max connections) is 1 connections.'
When we go to http://hostname:50100/webdynpro/dispatcher/sap.com
we can see RFC CC_RFC_LookUp and MAx connection parameter set to 1.
Rest of RFCs are having maximum connections as 20.
Please let us know what is the procedure to change MAX connection parameter for this
particular RFC CC_RFC_LookUp and which parameter we need to change and where should we find
this parameter?
Regards,
RR

Thanks Manoj,
I have gone through VA nodes ... could please mention which node i need to make this pareameter changes.
Please note : currently all other JCO pool RFCs are set to Max connections 20 .
But this particular RFC CC_RFC_LookUp under JCO pool tab shows
max connections set to only 1.
Please let me know where in VA i will find this parameter?

Difference between connection pooling and simple connection

Anybody please tell me what is the Difference between connection pooling and simple connection and also where we define connection pooling and how.
Thanks
Please reply soon
amitindia

Creating and closing connection to the database is a relatively slow process. Equally connections use database resources so you can't just open as many as you want.
A connection pool maintains a number of open connections throughout the lifetime of the application. Instead of opening and closing the connections your application just "borrows" them from the pool when they're needed.
If the pool runs out of connections it will usually create new ones as needed until you reach some predefined upper limit.
A good connection pool will also manage connections which have failed for any reason, and report code which fails to return connections to the pool (ie connection leaks).
The number of connections created at startup is referred to as the "low water mark" and the maximum number that the pool will allow to be opened at any given time is the "high water mark". If no connections are available client code will generally block until one is released.
If by "defined" you mean where can you get a working implementation then your database or application server vendor is likely to provide one. Also the Apache Jakarta Commons includes [url http://jakarta.apache.org/commons/dbcp/]an implementation which you can use with any JDBC driver.
Dave.

Issues with JDBC Connection Pooling

Hi all,
I'm experiencing some unexpected behaviour when trying to use JDBC Connection Pooling with my BC4J applications.
The configuraiton is -
Web Application using BC4J in local mode
Using Default Connection Stagegy
Stateless Release Mode
Retrieving Application Modules using Configuration.createRootApplicationModule( am , cf );
Returning Application Modules using Configuration.releaseRootApplicationModule( am, false );
Three application modules
AppModuleA - connects to DatabaseConnection1
AppModuleB - connects to DatabaseConnection2
AppModuleC - connects to DatabaseConnection2
My requirement is to -
Use App Module Pooling and have individual pool for each Application Module
Use JDBC Pooling and have individual pool for each Database connection
Note: All configuration was achieved in design mode (i.e. right clicking AppModule->Configurations...)
1. Initial approach -
In the configuration for each Application Module I specified the connection type as 'JDBC Datasource' and specified to approriate datasource.
Tried setting doConnecitonPooling to 'true' as well as 'false'
In the data-sources.xml I specified all the appropriate info including min-connections and max-connections.
I would expect, with the above config that BC4J would use OC4J's built in JDBC connection pooling.
2. Second approach -
In the configuration for each Application Module I specified the connection type as JDBC URL.
In the configuration I specified doConnectionPooling = 'true' as well as the max connection, max available and min available
What I experienced in both cases was that the max connections seem to be ignored as the number of connection as reported by the database (v$session) was exceeded by more than 10.
In addition to this once the load was removed the number of JDBC connecitons did not drop (I would have expected it to drop to max available connections)
My questions are -
1. When specifying to use a 'JDBC Datasource' style of connection, is it in fact OC4J that is then responsible for pooling JDBC connections? And in this case should BC4J's doConnectionPooling parameter be set to true or false?
2. Are there any known issues with the use of the JDBC Conneciton Pool as stated by the above to approaches?

Thanks for the additional info. Please see my comments. below.
Sorry should have been more specififc -
1. Is each application pool using a different JDBC user? You mentioned DatabaseConnection1 and DatabaseConnection2
above; are these connections to different schemas / users? If so, BC4J will create a separate connection pool for each
JDBC user. Each connection pool will have its own maximum pool size.
Each 'DatabaseConnection' refers to a different database, actually hosted on a seperate physical server, different
schema and different user.BC4J will maintain a separate connection pool for each permutation of JDBC URL / schema. If each user is connecting
to a different DB instance then I would expect no greater than 10 DB sessions. However, if a DB instance is hosting
more than user then I would expect greater than 10 DB sessions (though still no more than 10 DB sessions per user).
2. Are all the v$session sessions related to the JDBC clients? There should be at least one additional database
session which will be related to the session that is querying v$session.
When querying the v$session table I specifically look for connections from the user in quesiton and from the machine
name in question and in doing so eliminate the database system's connections, as well as the query tools'
connection. One area I'm not sure about is the connection BC4J uses to write to its temporary tables. I am using
Stateless release mode and have not explicetly stated to save to the database but I'm wondering if it still does if so
and how does it come into the equation with max connections?BC4J's internal connections are also pooled and the limits apply as mentioned above. So, if you have specified
internal connection info for a schema which is different than the users above I would expect the additional conns.
One helpful diagnostic tool, albeit programmatic, might be to print the information about the connection pools after
your test client(s) have finished. This may be accomplished as follows:
// get a reference to the BC4J connection pool manager
import oracle.jbo.server.ConnectionPoolManagerFactory;
import oracle.jbo.server.ConnectionPoolManagerImpl;
import oracle.jbo.pool.ResourcePool;
import java.io.PrintWriter;
import java.util.Enumeration;
// get the ConnectionPoolManager. assume that it is an instance of the supplied manager
ConnectionPoolManagerImpl mgr = (ConnectionPoolManagerImpl)ConnectionPoolManagerFactory.getConnectionPoolManager();
Enumeration keys = mgr.getResourcePoolKeys();
PrintWriter pw = new PrintWriter(System.out, true);
while (keys.hasMoreElements())
Object key = keys.nextElement();
ResourcePool pool = (ResourcePool)mgr.getResourcePool(key);
System.out.println("Dumping pool statistics for pool: " + key);
pool.dumpPoolStatistics(pw);
}

How to create connection pooling in Tomcat 5.0

present i am developing one web site in that i am using tomcat 5.0
i am trying to establish connection pooling in tomcat,i am facing some problems..
tomcat throws the following exception ie.,
cannot create JDBC Driver class for connect URL null.
my code lik this
i configured the web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app>
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>sqlserver</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
my server.xml
<?xml version='1.0' encoding='utf-8'?>
<Server>
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
<GlobalNamingResources>
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<Resource auth="Container" description="User database that can be updated and saved" name="UserDatabase" type="org.apache.catalina.UserDatabase"/>
<Resource auth="Container" name="sqlserver" type="javax.sql.DataSource"/>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>password</name>
<value>sudha</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
<parameter>
<name>username</name>
<value>sudha</value>
</parameter>
</ResourceParams>
<ResourceParams name="sqlserver">
<parameter>
<name>url</name>
<value>jdbc:odbc:SQL</value>
</parameter>
<parameter>
<name>validationQuery</name>
<value>select * from employee</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>4</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>8</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>sun.jdbc.odbc.JdbcOdbcDriver</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>username</name>
<value>kpi</value>
</parameter>
<parameter>
<name>factory</name>
<value>org.apache.naming.factory.DbcpDataSourceFactory</value>
</parameter>
<parameter>
<name>password</name>
<value>kpi</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<Service name="Catalina">
<Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" port="8080" redirectPort="8443" maxSpareThreads="75" maxThreads="150" minSpareThreads="25">
</Connector>
<Connector port="8009" protocol="AJP/1.3" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" redirectPort="8443">
</Connector>
<Engine defaultHost="localhost" name="Catalina">
<Host appBase="webapps" name="localhost">
<Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_log." suffix=".txt" timestamp="true"/>
</Host>
<Logger className="org.apache.catalina.logger.FileLogger" prefix="catalina_log." suffix=".txt" timestamp="true"/>
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"/>
</Engine>
</Service>
</Server>
and i studied the the tomcat documentation in that tomcat mentioned
The configuration properties for Tomcat's standard data source resource factory (org.apache.naming.factory.DbcpDataSourceFactory) are as follows:
driverClassName - Fully qualified Java class name of the JDBC driver to be used.
maxActive - The maximum number of active instances that can be allocated from this pool at the same time.
maxIdle - The maximum number of connections that can sit idle in this pool at the same time.
maxWait - The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception.
password - Database password to be passed to our JDBC driver.
url - Connection URL to be passed to our JDBC driver. (For backwards compatibility, the property driverName is also recognized.)
user - Database username to be passed to our JDBC driver.
validationQuery - SQL query that can be used by the pool to validate connections before they are returned to the application. If specified, this query MUST be an SQL SELECT statement that returns at least one row.
how to configure server.xml file
and how to get the org.apache.naming.factory.DbcpDataSourceFactory
please help me...this module is very very urgen to me..

http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html

Has anyone run the connection pooling for mysql & tomcat successfully?

I'm trying to set up connection pooling. I'm following the how-to page at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
But when i test the DBTest/test.jsp file, tomcat displays an error =
could not load jdbc driver class 'null'(msdos)
i have placed all the required .jar files in the tomcat lib.
below is the cofiguration i did to the server.xml file



<Server port="8005" shutdown="SHUTDOWN" debug="0">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>


<Service name="Tomcat-Standalone">


<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />




<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>











<Engine name="Standalone" defaultHost="localhost" debug="0">



<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>


<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>







<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Context path="/my-jsp" docBase="c:\JSP-Files" debug="0"
privileged="true" reloadable="true" />
     <Context path="" docBase="c:\Inetpub\wwwroot" debug="0" privileged="true" />
<Context path="/sharon" docBase="C:\Tomcat 4.1\webapps\sharon" debug="0" privileged="true" />





<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
     timestamp="true"/>




<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>



          
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<Resource name="jdbc/TestDB"
     auth="Container"
     type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
     <name>factory</name>
     <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
     </parameter>
     
     <parameter>
     <name>maxActive</name>
     <value>100</value>
     </parameter>
     
     <parameter>
     <name>maxIdle</name>
     <value>30</value>
     </parameter>
     
     <parameter>
     <name>maxWait</name>
     <value>10000</value>
     </parameter>

<parameter>
<name>user</name>
<value>javauser</value>
</parameter>
<parameter>
<name>password</name>
<value>javadude</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>

     <parameter>
     <name>url</name>
     <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>



</Server>
Pleas4 help!!!

you have your driver jar in Tomcat\common\lib?
if so, check your classpath, it could be that.

[原创] 有关Weblogic Connection Pool 连接恢复的问题

这是一个古老的问题，一直困扰我，这里既然碰到了，就看看能不能解决。
环境描述：
WEBLOGIC版本是8.1 SP2，数据库是SQL SERVER 2000，分别部署在两个服务器上。
第一步：
问题描述：
数据库服务器重新启动，导致WEBLOGIC 的CONNECTION POOL中的连接中断，EJB无法获得连接，导致应用出错。
解决方法：
进入WEBLOGIC ADMIN CONSOLE,
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
打开 Test Reserved Connections ，Test Created Connections，Test Released Connections这三个选项。
将Test Table Name属性设置为:sysproperties(SQL Server系统表，即使自己的应用不存在，这个表也存在，而且默认的内部没有数据)
根据如下解释：
Connections that fail the test are closed and reopened to re-establish a valid physical database connection.
(You must specify a Test Table Name below.)
每次调用首先进行测试连接，如果测试失败连接将重新建立。
测试结果：
WEBLOGIC启动后，关闭数据库SQL SERVER，应用服务器前端调用此时失败。
重新启动SQL SERVER后，WEBLOGIC端略做等待，前端应用恢复正常。
第二步：
问题描述：
进一步测试，如果WEBLOGIC先启动，启动完成后再启动数据库。
在WEBLOGIC CONSOLE得到如下输出：
<2006-3-22 上午11时50分08秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
<2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001150> <Connection Pool "MyJDBC Connection Pool" deployment
failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [Microsoft][SQLServe
r 2000 Driver for JDBC]Error establishing socket..>
<2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001151> <Data Source "MyJDBC Data Source" deployment failed w
ith the following error: DataSource(jdbc/OMSEIITxDS) can't be created with non-existent Pool (connection or multi) (MyJD
BC Connection Pool).>
Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
[EJB:011028]The DataSource with the JNDI name: jdbc/XXXXXX could not be located. Please ensure that the DataSource h
as been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
1、在默认初始化打开的连接一一失败以后，连接池发现可用的连接为0，郁闷的宣布自己部署失败。
2、接着数据源发现没有可用的连接池，自己也宣布部署失败。
3、下面所有的EJB发现不了数据源的JNDI名，部署也全部失败。
应用启动完成后，大部分EJB的状态为INACTIVE。前端应用无法使用，此时启动数据库，前端应用无法使用。
手动重新部署 EJB失败,错误还是找不到JNDI，前端应用无法使用。
手动重新部署连接池，数据源后，部署EJB 依然失败。前端应用无法使用。
解决方法：
进入WEBLOGIC ADMIN CONSOLE,
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
将
Connection Creation Retry Frequency 参数设置为 60。
ConnectionCreationRetryFrequencySeconds含义：
当创建数据库连接时,如果数据库不可用(如数据库没启动),隔多长时间试着重新创建该连接,
WLS8.1会每隔ConnectionCreationRetryFrequencySeconds秒重试一次.直到JDBC POOL创建成功
参考：http://dev2dev.bea.com.cn/techdoc/20030469.html，‘JDBC Connect Pool’部分。
英文解释可以直接控制台上看到，或者edocs查。
测试结果：
将数据库关闭，WEBLOGIC重新启动。
在WEBLOGIC CONSOLE得到如下输出：
打开Connection Creation Retry Frequency 参数后，连接池在第一轮尝试失败以后，就成功部署了，数据源也成功部署。
EJB部署会失败，但是提示也与先前的不同：
Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool MyJDBC Connection Pool to
allocate to applications, please increase the size of the pool and retry..
每隔一段时间会看到，CONNECTION POOL不断的重新进行连接：
<2006-3-22 下午12时17分56秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
在WEBLOGIC启动完成后，所有EJB为INACTIVE状态。
启动数据库服务器，稍后，手动重新部署所有的EJB，EJB可以部署成功，前端应用可以正常使用。
此时，此问题已经基本解决，仍需要手动部署EJB。
第三步：
问题描述：
解决方法：
有关部署次序的问题，首先查阅WEBLOGIC文档，http://edocs.bea.com/wls/docs81/faq/deploy.html#744900，得到
WebLogic Server deploys server-level resources (first JDBC and then JMS) before deploying applications.
Applications are deployed in this order: connectors, then EJBs, then Web Applications.
If the application is an EAR, the individual components are loaded in the order in which they are declared
in the application.xml deployment descriptor.
WEBLOGIC先部署服务器端资源，JDBC -> JMS....，然后部署我们的应用，EJB->WEB APPLICATION。
实际从WEBLOGIC启动日志来看，即使打开了Connection Creation Retry Frequency，如果当时数据库不是可用的，CONNECTION POOL
会不断的调度CONNECTION进行重新连接。但是此时，EJB的部署也同时在进行。个人猜测这应该是两个不同的线程（组）分别调度的任务。
现在考虑的是能不能用StartupClass截住EJB的部署过程，粗略的说是如果DATASOURCE没有连接好，或者没有可用的连接池，
就不往下进行EJB部署的过程。
参考：http://edocs.bea.com/wls/docs81/config_xml/EJBComponent.html#DeploymentOrder
DeploymentOrder：
A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable
items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and
deploys startup classes.Items with the lowest Deployment Order value are deployed first.
There is no guarantee on the order of deployments with equal Deployment Order values.
There is no guarantee of ordering across clusters. Default: 1000 Minimum: 0 Maximum: 2N31-1
在部署同一类应用时，按照 DEPLOYMENT LOADER的数值决定，数值越小越先。（EJB的参数在ADMIN CONSOLE界面上叫做LOAD ORDER)
而且上面看来服务器是先部署EJB，再部署STARTUP CLASS，遗憾了。
好在STARTUP CLASS上有两个选项，
Run Before Application Deployments
Run Before Application Activations
这两个选项分别可以设置StartupClass分别在系统资源部署之前，以及在系统资源部署和用户应用部署之间启动。
选上Run Before Application Activations。
现在可以了，我写了一个STARTUP CLASS，思路见下：
主代码：
private void testConnection(){
while (!isTimeout() && !getConnection()){
try{
Thread.sleep(testInterval*1000);
}catch(Exception ignor){}
log("DBConnectHolder job finished with following status:");
log("Timeout:"+isTimeout +",Connection OK:"+isConnected);
测试结果：
只要配置的等待时间足够长，应用服务器先行启动的情况下，等待数据库启动后才进行EJB等等的部署。
（主要考虑如果数据库连接不OK，EJB启动了也没有太大用，还得手工重新部署。）算是比较完满的解决了问题。
另外一个思路是是否可行？通过MBean, 在CONNECTION 建立起来以后通知一把，进行EJB的重新部署。
没来得及研究，请有经验的同学帮我补充完善。
结论：
其实也没什么结论，只是把自己遇到问题，解决问题的思路写了一下。短时间内阅读的文献有限，可能采用了一些苯方法
，或者走了弯路，也请大家拍砖。
在WL8版本上，数据库连接进行恢复和重新连接的时候，上面提出的几个参数应该是比较重要的，我再次强调一下。
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
Test Reserved Connections
Test Created Connections
Test Released Connections
Test Table Name
Connection Creation Retry Frequency

在第一个情景中应该只需要打开Test Reserved Connections 就可以了。
Test Created Connections表示创建连接后放到pool之前进行测试看连接是否可用
Test Released Connections表示释放连接回到pool之前进行测试看连接是否可用
I think so！

Unable to get the expected results with connection pooling

Hi All,
I have been trying to create JDBC connection pooling provided by the Apache Tomcat 4.0 with MySQL 4.0.16-nt at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html and my configuration is as follows
server.xml
<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>

<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>

<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>

<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>

<parameter>
<name>username</name>
<value>javauser</value>
</parameter>
<parameter>
<name>password</name>
<value>javadude</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>

<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
</Context>
web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<description>MySQL Test App</description>
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/TestDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
test.jsp
<jsp:useBean id="foo" class="foo.DBTest" scope="page" />
<html>
<head>
<title>DB Test</title>
</head>
<body>
<%
foo.DBTest tst = new foo.DBTest();
tst.init();
%>
<h2>Results</h2>
Foo <%= tst.getFoo() %>
Bar <%= tst.getBar() %>
</body>
</html>
DBTest.java package
package foo;
import javax.naming.*;
import javax.sql.*;
import java.sql.*;
public class DBTest {
String foo = "Not Connected";
int bar = -1;
public void init() {
try{
Context ctx = new InitialContext();
if(ctx == null )
throw new Exception("Boom - No Context");
DataSource ds =
(DataSource)ctx.lookup(
"java:comp/env/jdbc/TestDB");
if (ds != null) {
Connection conn = ds.getConnection();
if(conn != null) {
foo = "Got Connection "+conn.toString();
Statement stmt = conn.createStatement();
ResultSet rst =
stmt.executeQuery(
"select id, foo, bar from testdata");
if(rst.next()) {
foo=rst.getString(2);
bar=rst.getInt(3);
conn.close();
}catch(Exception e) {
e.printStackTrace();
public String getFoo() { return foo; }
public int getBar() { return bar;}
Now when I am trying to run this on browser, everything goes fine except it doesn't show the expected results, instead of that it shows following in the browser:-
Results
Foo Not Connected
Bar -1
Can anybody help me out as to why I am getting such result while everything is right from my side. Is the program unable to connect to the database or it is not supporting the JDBC version that I am using.
Thanks in advance
Regards
Vikas

Oh, I think this is not the right place to post this message. I have placed the same in other place of this forum. please ignore this post here!!
MJ, by the way the link that you suggested is not useful to me.
Thank you

Unable to get Results using Connection Pool

Hi All,
I have been trying to create JDBC connection pooling provided by the Apache Tomcat 4.0 with MySQL 4.0.16-nt at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html and my configuration is as follows
server.xml
<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>

<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>

<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>

<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>

<parameter>
<name>username</name>
<value>javauser</value>
</parameter>
<parameter>
<name>password</name>
<value>javadude</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>

<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
</Context>
web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<description>MySQL Test App</description>
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/TestDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
test.jsp
<jsp:useBean id="foo" class="foo.DBTest" scope="page" />
<html>
<head>
<title>DB Test</title>
</head>
<body>
<%
foo.DBTest tst = new foo.DBTest();
tst.init();
%>
<h2>Results</h2>
Foo <%= tst.getFoo() %>
Bar <%= tst.getBar() %>
</body>
</html>
DBTest.java package
package foo;
import javax.naming.*;
import javax.sql.*;
import java.sql.*;
public class DBTest {
String foo = "Not Connected";
int bar = -1;
public void init() {
try{
Context ctx = new InitialContext();
if(ctx == null )
throw new Exception("Boom - No Context");
DataSource ds =
(DataSource)ctx.lookup(
"java:comp/env/jdbc/TestDB");
if (ds != null) {
Connection conn = ds.getConnection();
if(conn != null) {
foo = "Got Connection "+conn.toString();
Statement stmt = conn.createStatement();
ResultSet rst =
stmt.executeQuery(
"select id, foo, bar from testdata");
if(rst.next()) {
foo=rst.getString(2);
bar=rst.getInt(3);
conn.close();
}catch(Exception e) {
e.printStackTrace();
public String getFoo() { return foo; }
public int getBar() { return bar;}
Now when I am trying to run this on browser, everything goes fine except it doesn't show the expected results, instead of that it shows following in the browser:-
Results
Foo Not Connected
Bar -1
Can anybody help me out as to why I am getting such result while everything is right from my side. Is the program unable to connect to the database or it is not supporting the JDBC version that I am using.
Thanks in advance
Regards
Vikas

I've seen cases where NOT using the ResourceParams section, and instead using attributes in the Resource section will fix this. Don't know why.
i.e.
Instead of using:
<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>use the driver attribute of the Resource tag:
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"
driver="org.gjt.mm.mysql.Driver"/>Also note...I don't use the org.gjt.mm.mysql.Driver class (which is in the distribution), I use com.mysql.jdbc.Driver. Any reason you don't? This could be part of it. I don't really know.

Maximum no. of XA Connection pools

Similar Messages

Maybe you are looking for