Connection Pooling in heavy traffic web-applications

In a 24x7 web-app used by 3000-10000 concurrent users, what is the
realistic number of maxmimum connections one should
have defined in the application server's connection pool?
The app has no caching mechanism therefore every page is a database
hit. Does max connection of 20 make sense when at any time 1000 users
could be using the web-app?
Is that number dictated by the DBA or the Java app developer?
For example, web sites like Amazon.com sure must be using connection
pools to control access to resources. Do they define 20 max connections
or 200 max connections to their database? Do they have multiple replicated databases, how are the databases synced up.

If I were to rephrase this question like
In Weblogic 7.0, if my connection pool has
1. Minimum capacity = 10
2. Maximum capacity = 100
3. Capacity Increment = 1
And say 100 users are connected to my site using all 100 connections available.
What happens to the 101th user?
1. Will he be waiting for the connection to be free which was held up by 100 users?
2. Will he get a Error/Exception regarding the same?
Rgds,
Seetesh

Similar Messages

How to check if Connection Pooling is used in our application

We have an ASP.NET application designed by developer team.
All the files are .aspx
They are all hosted in an Windows IIS and connect to Oracle database.
I was reading some forums where people are suggesting to use "connection pooling" for better database performance.
Now is there anyway I can check in code of the .aspx files to see if our team is using connection pooling method or not.

Connection pooling is on by default. The easiest way to check is to check the connect string. If "pooling=false" is there, it's been turned off. If "pooling=true" is specified, or if it's not specified at all, it's on.
Hope it helps,
Greg

How to use connection pool of datasource to make applications run faster?

Hi, erveryone
I prepare to implement a servlet that access database and do sync with client.
When I access database, I would like to configure a datasource in weblogic and use connection pool.
In order to make servlet application run significantly faster, my servet how to use connection poo is much moreresonable?
For example, my servlet has many times database access. Is it true that geting and close a connection whenever
one time database access finished?
If from the servlet begins, the db connection is hold till servlet finalize. Will the solution affect the servlet performance? Is there any official document to introduce connection pool program? I search some documents.
<The Java EE 6Tutorial> introduce some simple intruduction about connection pool.

1. Use WebLogic Servers Data Source for Database Connections.
2. Open and close the connections where you need it. Dont open it in begin and close in finalise. That is bad practice.
3. Even when you invoke Connection.close () webLogic will not close the connection. it will commit the transaction and return it back to the pool rather than physically closing the DB connection.
4. You can tune data source for minimum, maximum and increments of connections that you need based on your application requirement.

How to retain connection pool resource while exporting the application war

hello,
lately i have figured out how to use connection pooling. now i have another issue.
i have to export the application war file to a remote server for deployment. i cant configure the server.xml file there due to restrictions. Now is there any way that i can retain the connection pooling with all JNDI resources while exporting the war file. what all things would i have to do. i am using tomcat 4.1 and the remote server too have the same appliaction server running.
is this possible?
thanks in advance

Hi,
you might have the problem in creating WAR files.
lease check that first.
thanks,
nvseenuNo, the problem is that you shouldn't be modifying the server.xml
The proper, portable way to do it is to create a context.xml file and put it in the META-INF directory of your WAR file. This contains your Resource definition and JDBC connection parameters. Everything's portable that way.
I know this works on Tomcat 5.x.
It can also work with Tomcat 4.1.x, but the way I've done it is to put the context.xml into a file whose name matches my WAR file (e.g, foo.war and foo.xml), placing both in the /webapps directory. Tomcat 4.1.x picks it up that way.
It would be worth an experiment to see if Tomcat 4.1.x picks up the context from /META-INF, because that way your WAR file is 100% portable.
This is precisely the reason why I advise people not to edit the server.xml. You don't always have the option to do so.
%

Not able to connect to the EAS using web application

Hello
I've upgraded Essasbe from 11.1.1.3 to 11.1.1.4. Before the upgrade am able to login into the EAS web application using the But after the upgrade to 11.1.1.4 am not able to login using the above said hostname but rather with the the new
My question is why did this happen.. It it something got to do with the upgrade.
Edited by: 964846 on Nov 14, 2012 10:54 AM
Edited by: 964846 on Nov 15, 2012 7:58 AM

Well where did you get new host name from? and where did the configurator get the host name from
What happens if you ping dbhysbstst-db0-bkp is it the same ip as the EAS server
Cheers
John
http://john-goodwin.blogspot.com/

Jdbc connection pool ping error in sun application server

hi,
i have done the appropriate settings for my connection pool
and i have got ping succeded................but it is only for sometimes.
while pinging with the same set of data during another time i have got different errors..........
they are the following:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: The transaction isolation could not be set: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=150999297)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI
=4))))
so i have doubted about my oracle server..........
plz tell me how to start the oracle database server and the oracle net listener............
i would really appreciate anybody for helping me in this problem........

hi,
i have done the appropriate settings for my connection pool
and i have got ping succeded................but it is only for sometimes.
while pinging with the same set of data during another time i have got different errors..........
they are the following:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: The transaction isolation could not be set: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=150999297)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI
=4))))
so i have doubted about my oracle server..........
plz tell me how to start the oracle database server and the oracle net listener............
i would really appreciate anybody for helping me in this problem........

Tomcat 5.0.* global JNDI database connect pooling. complex config question

Ok. I can't get global connection pooling to work in tomcat 5.0.24. (I am running windows xp pro)
I am using MySQL (installed on the same machine) and I have succesfully worked through the tutorial titled "MySQL DBCP Example" found at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html
This example does not demonstrate global connection pooling, however. I want to share a single connection pool across all my web applications. I don't want a different connection pool for each webapp.
So I define the connection pool JDBC resource in the conf/server.xml file under the <GlobalNamingResources> element.
Here is the entire <GlobalNamingResources> element lifted from conf/server.xml:
(Please overlook some of the formatting mistakes due to the <code> tag interpreting the xml as java.)

<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>
    <Resource name="jdbc/MySQL"
              auth="Container"
              type="javax.sql.DataSource"/>
    <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>
    <ResourceParams name="jdbc/MySQL">
        <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>20000</value>
        </parameter>
        <parameter>
           <name>username</name>
           <value>webapp</value>
        </parameter>
        <parameter>
           <name>password</name>
           <value>******</value>
        </parameter>
        <parameter>
            <name>removeAbandoned</name>
            <value>true</value>
        </parameter>
        <parameter>
            <name>removeAbandonedTimeout</name>
            <value>3000</value>
        </parameter>
        <parameter>
            <name>logAbandoned</name>
            <value>true</value>
        </parameter>
        <parameter>
            <name>url</name>
            <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
        </parameter>
    </ResourceParams>
</GlobalNamingResources>I am still trying to get the DBTest example (described in the link to the tomcat 5 docs above) to work, only now I want it to work using a global connection pool. So here is the contents of webapps/DBTest/WEB-INF/web.xml: (again, please overlook formatting difficulties :)
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
         http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
         version="2.4">
<description>MySQL Test App</description>
<resource-ref>
      <description>DB Connection</description>
      <res-ref-name>jdbc/MySQL</res-ref-name>
      <res-type>javax.sql.DataSource</res-type>
      <res-auth>Container</res-auth>
</resource-ref>
</web-app>The last thing I need to do, I think, is to include a <resourceLink> element in the context.xml file for this webapp. Now in tomcat 5.0.* it is not recommended that the <context> element appear in the conf/server.xml file. Instead, as I understand it, it should appear in either of the two following places (for a webapp called DBTest):
$CATALINA_HOME/conf/[engine_name]/[host_name]/DBTest.xml
$CATALINA_HOME/webapps/DBTest/META-INF/context.xmlSince I would eventually like to package each webapp in its own war file, I prefer the second option above. This will enable me to place the context.xml file within the .war file. Currently, however, I am not using .war files.
For the DBTest webapp I have the following <context> element in webapps/DBTest/META-INF/context.xml:
<context path="/DBTest" docBase="/DBTest" debug="1">
    <ResourceLink global="jdbc/MySQL" name="jdbc/MySQL" type="javax.sql.DataSource" />
</context>Now, when I point my browser to http://localhost:8080/DBTest/test.jsp I get the following message:
javax.servlet.ServletException: Unable to get connection, DataSource invalid: "org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null', cause: No suitable driver"
For those who are interested, here is test.jsp:
<%@ taglib uri="http://java.sun.com/jsp/jstl/sql" prefix="sql" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<sql:query var="rs" dataSource="jdbc/MySQL">
select id, foo, bar from javatest.testdata
</sql:query>
<html>
<head>
    <title>DB Test</title>
</head>
<body>
<h2>Results</h2>
<c:forEach var="row" items="${rs.rows}">
    Foo ${row.foo}<br/>
    Bar ${row.bar}<br/>
</c:forEach>
</body>
</html>Now I know that this is a very long and detailed question and that it is unlikely that anyone is even going to read down this far, let alone take the time to study all that XML, but if anyone is able to tell me why this setup does not allow global connection pooling, I will be pretty *@&$**% impressed. I only wish I had duke dollars to give.
Jon

Okay, I went back and double checked that I can get the DBTest example working. It is described here: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html
I was not able to get it working exactly according to the tutorial, though. I was required to put the <context> element not in the conf/server.xml but in conf/Catalina/localhost/DBTest.xml. Then, with the DBTest/WEB-INF/web.xml as above, I was able to get the DBTest example working. The output of test.jsp (described above also) is the following:
Results
Foo hello
Bar 12345I would like to be able to put the <context> element in webapps/DBTest/META-INF/context.xml (as I think should be allowed) because then I would be able to include it in a war file that encompassed the entire web application. If I am forced to put the <context> element in a subdirectory of the conf directory, then I cannot include it in a war file and I will be unable to just drop my war files in the webapps directory and go. Instead I will have to drop my war files in the webapps directory, then go and fiddle around with the xml files in conf/Catalina/localhost/
But if I move the <context> element into webapps/DBTest/META-INF/context.xml then the example stops working. When I put it back in conf/Catalina/localhost/DBTest.xml everything is fine again.
Ok, no big deal. I guess my war file deployment will just have to be a little more complicated.
But what if I want the resource to be global??? If I remove the <Resource> and <ResourceParams> elements from the webapp-specific <context> element and put them in the <GlobalNamingResource> element in the conf/server.xml file I should have a global resource, right? I did this, then added a resource link to the <context> element (see above), however, the example stops working. I have tried both with and without the <resource-ref> element in web.xml.
Can some remarkably intelligent and knowledgeable person please explain to me how global resources work in tomcat 5.0, especially global JDBC connection pooling.
Thanks,
Jon

Configure Service Principle Name for Application Pool account and web application?

Hello Community
    On WS2012 Server running Sharepoint 2013 Server when you
configure SPN you configure it for the SQL server object "MSSQLSvc" (domain account)
and the user object "HTTP" (domain account).
    The question is if you also should configure SPN for the Application Pool account and
configure SPN for the web application, how do you configure SPN for the Application Pool
account and the web application?
    Thank you
    Shabeaut

The Web Application is only an IIS Site. You're configuring the SPN for the Domain User running the IIS Application Pool (that the Web Application (IIS Site) leverages).
So you would just need to use the format of:
setspn -A HTTP/webAppUrl domain\iisapppoolacctusername
setspn -A HTTP/webAppUrl.fqdn.com domain\iisapppoolacctusername
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Failed to obtain/create connection from connection pool after redeploy

I have a web application (.war) that uses a jdbc connection pool. The application works fine, however after I redeploy it using the administration console I get "Failed to obtain/create connection from connection pool [ Datavision_Pool ]. Reason : null" followed by "Error allocating connection : [Error in allocating a connection. Cause: null]" from javax.enterprise.resource.resourceadapter and I am forced to restart the instance. I am running Sun Java System Application Server 9.1 (build b58g-fcs)
using a connection pool to a Microsoft SQL 2000 database using inet software's JDBC drivers. I need to be able to redeploy applications without having to restart the instance. Any help is appreciated.

I have turned on some additional diagnostics and found out some answers and a work-around, but I think that there may be a bug in the way JDBC connection pool classes are loaded. The actual error was a null pointer in the JDBC driver class in the perpareStatement method. The only line in this method is "return factory.createPreparedStatement( this , sql );" and the only possible NPE would be if the factory was null, which should be impossible because it is a static variable and it is initialized when the class is loaded. The problem occurs because we deploy the JDBC driver .jar file within our .war file, for use when a client doesn't have or want to use connection pooling. Apparently, the connection pool must have picked up some of these classes and when the .war was redeployed, the reference to the factory was lost for existing connections (not sure how). If I remove the JDBC .jar file from the .war, it works, but that wasn't an ideal solution, the other way to get it to work was to change the sun-web.xml file to have <class-loader delegate="true">. We previously had it set to false in version 8.1 because of interference with a different version of the apache Tiles classes, which has now been addressed in version 9.1.
I still think there is an issue, because the connection pool should never use the application specific classloaders. Am I wrong to believe this?

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

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

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

Server-side connection pooling for clients in different VM's

We have a need to centeralize our connection pool manger.
Is there a server-side connection pooling manger product to allow multiple clients running in different VM's to connect to and share connection objects to the same Database?
e.g. An applet, and a swing and a servlet/web app application all running in different VM's will connect to this central connection pool manager and share connection objects to the same DB.
We are using connection pooling for all of our applications but each application is maintaining its own connection pool and it is becomming a nightmare to manage and configure each one.
Also, we have to have at a miniumum one connection open per application to access the database regardless of wether we are using connection pool or not. This means that 100 apps(running in different VM's) will use at minimum 100 connections... where all of these 100 apps will do just fine with just 10-15 connections.
while back we used T3 server but can't find this product on BEA web site any more.
does jdbc 2.2 or 3.0 have any server side pool management specs outlined?
Please HELP as we can't afford anymore licensing fees for our company.
oh.. We can't open and close connections on each query as they will be slow.
any suggestions greatly appreciated.

if i understand you question, i don't think this is possible, since the Connection interface (and basically all of the related jdbc interfaces) aren't Serializable.. so they can't be sent over the wire to your client(s).
However, you could feasibly write some server side connection pool, and some server side facade which will allow clients to submit queries (either SQL String's or however you want to do it - obviously a more elegant solution involves a series of classes which dynamically create sql based on query criteria), then the server can grab a connection, execute the query, cycle through the results and populate some result object of your creation and send that back over the wire to your client(s).
.

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 and datasource

In WL 7, we need to configure a datasource and a connection pool in order for the application to get a connection to the database. How is the datasource and connection pool related?
In WL 9.2, there is no option to configure the connection pool, there is only the option to configure the data source. Where did the connection pool go in WL 9.2?

gerald lee wrote:
In WL 7, we need to configure a datasource and a connection pool
in order for the application to get a connection to the database.
How is the datasource and connection pool related?
It depends on the WLS version. pre-9.X, there can be more than one datasource pointing to a given pool,
but you do need a datasource typically to use a pool.
In WL 9.2, there is no option to configure the connection pool, there is only
the option to configure the data source. Where did the connection pool go in WL 9.2?In 9.X and beyond the relationship is one-to-one, and you will create both at the
same time when creating a datasource.
Joe

Error in creating web application through power shell

hi,
i have taken the ps script from the below url :
credits to Roger :
http://blogs.msdn.com/b/rcormier/archive/2012/09/01/how-to-create-sharepoint-web-applications-with-powershell.aspx
http://gallery.technet.microsoft.com/Create-SharePoint-Web-742a8fb9
But when i am running the script, i am getting many errors:
Note: i am not using appln pool account password [as i dont know the password]
want to know whether this paramter is necessary.
$ver = $host | select version
if($Ver.version.major -gt 1) {$Host.Runspace.ThreadOptions = "ReuseThread"}
if(!(Get-PSSnapin Microsoft.SharePoint.PowerShell -ea 0))
Write-Progress -Activity "Loading Modules" -Status "Loading Microsoft.SharePoint.PowerShell"
Add-PSSnapin Microsoft.SharePoint.PowerShell
Write-Progress -Activity "Creating Web Application" -Status "Setting Variables"
#Set Individual Web App Variables
#This is the Web Application URL
$WebApplicationURL = "http://mysrvr:2020/"
#This is the Display Name for the SharePoint Web Application
$WebApplicationName = "myweb1"
#This is the Content Database for the Web Application
$ContentDatabase = "myContentDB"
#Set Common Variables
#This is the Display Name for the Application Pool
$ApplicationPoolDisplayName = "mapppool2020"
#This is identity of the Application Pool which will be used (Domain\User)
$ApplicationPoolIdentity = "mydomain\myidd"
#This is the password of the Appliation Pool account which will be used
#$ApplicationPoolPassword = "Pass@word1"
#This is the Account which will be used for the Portal Super Reader Account
$PortalSuperReader = "i:0#.w|in\hariharan.venugopalk"
#This is the Account which will be used for the Portal Super User Account
$PortalSuperUser = "i:0#.w|in\spinstall.dev"
Write-Progress -Activity "Creating Web Application" -Status "Loading Functions"
#Create Functions
Function CreateClaimsWebApp($WebApplicationName, $WebApplicationURL, $ContentDatabase, $HTTPPort)
    #AppPoolUsed is set when calling the ValidateAppPool function. This will be true if the application pool is already running SharePoint web appplications
    #If the application pool is already being used in web applications, the syntax for New-SPWebApplication changes
    if($AppPoolUsed -eq $True)
        #Create the web application, assign it to the WebApp variable. The WebApp variable will be used to set object cache user accounts
        Write-Progress -Activity "Creating Web Application" -Status "Using Application Pool With Existing Web Applications"
        Set-Variable -Name WebApp -Value (New-SPWebApplication -ApplicationPool $ApplicationPoolDisplayName -Name $WebApplicationName -url $WebApplicationURL -port $HTTPPort -DatabaseName $ContentDatabase -HostHeader $hostHeader
-AuthenticationProvider (New-SPAuthenticationProvider)) -Scope Script
        #Call the SetObjectCache function, which sets the object cache.
        Write-Progress -Activity "Creating Web Application" -Status "Configuring Object Cache Accounts"
        SetObjectCache
    else
        #Create the web application, assign it to the WebApp variable. The WebApp variable will be used to set object cache user accounts
        Write-Progress -Activity "Creating Web Application" -Status "Using Application Pool With No Existing Web Applications"
        Set-Variable -Name WebApp -Value (New-SPWebApplication -ApplicationPool $ApplicationPoolDisplayName -ApplicationPoolAccount $AppPoolManagedAccount.Username -Name $WebApplicationName -url $WebApplicationURL -port $HTTPPort
-DatabaseName $ContentDatabase -HostHeader $hostHeader -AuthenticationProvider (New-SPAuthenticationProvider)) -Scope Script
        #Call the SetObjectCache function, which sets the object cache.
        Write-Progress -Activity "Creating Web Application" -Status "Configuring Object Cache Accounts"
        SetObjectCache
Function ValidateURL($WebApplicationURL)
    #Find out if a web application with the target URL exists
    if(get-spwebapplication $WebApplicationURL -ErrorAction SilentlyContinue)
        #If a web application with the specifid URL already exists, wait 5 seconds and exit
        Write-Progress -Activity "Creating Web Application" -Status "Aborting Process Due To URL Conflict"
        Write-Host "Aborting: Web Application $WebApplicationURL Already Exists" -ForegroundColor Red
        sleep 5
        #Setting the CriticalError value to $True results in the script to not create anything
        Set-Variable -Name CriticalError -Value $True
    #If the WebApplicationURL passed is not already a SharePoint web application, find out if it starts with HTTP or HTTPS
    elseif($WebApplicationURL.StartsWith("http://"))
            #If the string starts with http://, and not https://, trim the protocol from the URL. Set the host as the host header
            Set-Variable HostHeader -Value ($WebApplicationURL.Substring(7)) -Scope Script
            #If we're using HTTP, use port 80
            Set-Variable -Name HTTPPort -Value "80" -Scope Script
        elseif($WebApplicationURL.StartsWith("https://"))
            #If the string starts with https://, and not http://, trim the protocol from the URL. Set the host as the host header
            Set-Variable HostHeader -Value ($WebApplicationURL.Substring(8)) -Scope Script
            #If we're using HTTPS, use port 443
            Set-Variable -Name HTTPPort -Value "443" -Scope Script
Function ValidateAppPool($AppPoolName, $WebApplicationURL)
    #Change the ErrorActionPreference to SilentlyContinue while preserving the original value in a temporary variable
    #Failing to do this will result in error messages being displayed if Get-WebAppPoolState does not return an object. The script would still continue
    $CurrentErrorActionPreference = $ErrorActionPreference
    $ErrorActionPreference = "SilentlyContinue"
    #Check to see if an application pool with the name passed by the AppPoolName variable already exists, assign this to a variable.
    #This variable will be used in order to determine if the application pool exists, but is not part of SharePoint
    $TestAppPool = Get-WebAppPoolState $AppPoolName
    #If we have a SharePoint application pool with the value passed by the AppPoolName variable, find out if there are any sites using that app pool
    #This changes the syntax used with New-SPWebApplication
    if(Get-SPServiceApplicationPool $AppPoolName)
        #Return all application pools used by all web applications
        $AppPools = Get-SPWebApplication | select ApplicationPool
        #Providing there is more than one application pool, find out what their names are
        if($AppPools)
            foreach($Pool in $AppPools)
                #Get The application pool display name for each application pool returned
                [Array]$Poolchild = $Poolchild += ($Pool.ApplicationPool.DisplayName)
                #If any application pool matches the value passed by ApplicationPoolDisplayName, set AppPoolUsed to True
                #This is referenced in the CreateClaimsWebApp function
                if($Poolchild.Contains($ApplicationPoolDisplayName))
                    Set-Variable -Name AppPoolUsed -Value $True -Scope Script
                #If the application pool display name does not match the value passed by ApplicationPoolDisplayName, set AppPoolUsed to False
                #This is referenced in the CreateClaimsWebApp function
                else
                    Set-Variable -Name AppPoolUsed -Value $False -Scope Script
        #Since this is a SharePoint Application Pool, set the AppPool value to the the SPServiceApplicationPool object returned
        Set-Variable -Name AppPool -Value (Get-SPServiceApplicationPool $AppPoolName) -scope Script
        #Set the AppPoolManagedAccount variable to the name of the managed acount used by the application pool returned
        #AppPoolManagedAccount is used in the CreateClaimsWebApp function if the application pool does not have existing web applications that are using it
        Set-Variable -Name AppPoolManagedAccount -Value (Get-SPManagedAccount | ? {$_.username -eq ($AppPool.ProcessAccountName)}) -scope Script
    #Check to see if the application pool is in IIS, but is not a SharePoint app pool
    elseif($TestAppPool)
        #If the application pool exists in IIS and is not a SharePoint application pool, abort the script by setting CriticalError to True
        Write-Host "Aborting: Application Pool $AppPoolName already exists on the server and is not a SharePoint Application Pool `n`rWeb Application `"$WebApplicationURL`" will not be created" -ForegroundColor
Red
        Set-Variable -Name CriticalError -Value $True
    #If it's not a SharePoint app pool, and it doesn't exist in IIS, we have to create one
    elseif(!($TestAppPool))
        #Find out if a managed account exists by calling the ValidateManagedAccount function
        validateManagedAccount $ApplicationPoolIdentity
        #If the managed account exists, create an application pool using the existing managed account
        if($ManagedAccountExists -eq $True)
            #Set the AppPoolManagedAccount to the identity of the managed acocunt referenced by the ApplicationPoolIdentity variable
            Write-Host "Creating New App Pool using Existing Managed Account"
            Set-Variable -Name AppPoolManagedAccount -Value (Get-SPManagedAccount $ApplicationPoolIdentity | select username) -scope "Script"
            #Create a new SPServiceApplicationPool, assign that to the AppPool variable
            Set-Variable -Name AppPool -Value (New-SPServiceApplicationPool -Name $ApplicationPoolDisplayName -Account $ApplicationPoolIdentity) -scope "Script"
        #If there is no managed account matching the account referenced by the ApplicationPoolIdentity, create it
        else
            #Use the ApplicationPoolIdentity and ApplicationPoolPassword to create a credential object
            #This is necessary when creating a new managed account
            Write-Host "Creating New Managed Account And App Pool"
            $AppPoolCredentials = New-Object System.Management.Automation.PSCredential $ApplicationPoolIdentity, (ConvertTo-SecureString $ApplicationPoolPassword -AsPlainText -Force)
            #Create a new managed account, assign that to the AppPoolManagedAccount variable
            Set-Variable -Name AppPoolManagedAccount -Value (New-SPManagedAccount -Credential $AppPoolCredentials) -scope "Script"
            #Create a new application pool using the new managed account, assign this to the AppPool variable
            Set-Variable -Name AppPool -Value (New-SPServiceApplicationPool -Name $ApplicationPoolDisplayName -Account (get-spmanagedaccount $ApplicationPoolIdentity)) -scope "Script"
    #Return the ErrorActionPreference to the default value
    $ErrorActionPreference = $CurrentErrorActionPreference
Function ValidateManagedAccount($ApplicationPoolIdentity)
    #Find out if the manage account referenced by the AppPoolIdentity already exists
    #If it does, set ManagedAccountExists to True
    if(Get-SPManagedAccount $ApplicationPoolIdentity -ErrorAction SilentlyContinue)
        Set-Variable -Name ManagedAccountExists -Value $True -Scope Script
    #If it does not, set ManagedAccountExists to False
    else
        Set-Variable -Name ManagedAccountExists -Value $False -Scope Script
Function ClearScriptVariables
    #Set the ErrorActionPreference to SilentlyContinue
    #If this is not set, and the script variables referenced have not been set, an error message will be returned. The script would still continue
    $CurrentErrorActionPreference = $ErrorActionPreference
    $ErrorActionPreference = "SilentlyContinue"
    #Remove the CriticalError variable
    Remove-Variable $CriticalError -ErrorAction SilentlyContinue
    $ErrorActionPreference = $CurrentErrorActionPreference
Function SetObjectCache
    #Set object cache user account properties based on the value of the parameters supplied
    $WebApp.Properties["portalsuperuseraccount"] = $PortalSuperUser
    $WebApp.Properties["portalsuperreaderaccount"] = $PortalSuperReader
    #Create a New Policy for the Super User
    $SuperUserPolicy = $WebApp.Policies.Add($PortalSuperUser, "Portal Super User Account")
    #Assign Full Control To the Super User
    $SuperUserPolicy.PolicyRoleBindings.Add($WebApp.PolicyRoles.GetSpecialRole([Microsoft.SharePoint.Administration.SPPolicyRoleType]::FullControl))
    #Create a New Policy for the Super Reader
    $SuperReaderPolicy = $WebApp.Policies.Add($PortalSuperReader, "Portal Super Reader Account")
    #Assign Full Read to the Super Reader
    $SuperReaderPolicy.PolicyRoleBindings.Add($WebApp.PolicyRoles.GetSpecialRole([Microsoft.SharePoint.Administration.SPPolicyRoleType]::FullRead))
    #Commit these changes to the web application
    $WebApp.Update()
#Script
#Call the ClearScriptVariables function to empty out varialbes that should be blank when the script executes.
ClearScriptVariables
#Validate the URL passed by calling the ValidateURL function
Write-Progress -Activity "Creating Web Application" -Status "Validating Web Application URL Variables"
ValidateURL $WebApplicationURL
#Validate the application pool variables by calling the ValidateAppPool function
Write-Progress -Activity "Creating Web Application" -Status "Validating Application Pool Variables"
ValidateAppPool $ApplicationPoolDisplayName $WebApplicationURL
#As long as CriticalError has not been set, create the web application using the variables passed.
if(!($CriticalError))
Write-Progress -Activity "Creating Web Application" -Status "Creating Claims-Based Web Application"
CreateClaimsWebApp $WebApplicationName $WebApplicationURL $ContentDatabase $HTTPPort
error is thrown below:
deployment
S D:\myworkspace\bif> iisreset
ttempting stop...
nternet services successfully stopped
ttempting start...
nternet services successfully restarted
S D:\myworkspace\bif> .\CreateSP2013ClaimsWebApplication.ps1
reating New Managed Account And App Pool
ew-SPWebApplication : "mysrvr:2020/" contains invalid character ':'.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:68 char:43
         Set-Variable -Name WebApp -Value (New-SPWebApplication
ApplicationPool ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
   + CategoryInfo
: InvalidData: (Microsoft.Share...PWebApplication:
SPCmdletNewSPWebApplication) [New-SPWebApplication], ArgumentException
   + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWeb
Application
annot index into a null array.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:235 char:5
     $WebApp.Properties["portalsuperuseraccount"] = $PortalSuperUser
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : NullArray
cannot index into a null array.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:236 char:5
     $WebApp.Properties["portalsuperreaderaccount"] = $PortalSuperReader
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : NullArray
ou cannot call a method on a null-valued expression.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:239 char:5
     $SuperUserPolicy = $WebApp.Policies.Add($PortalSuperUser, "Portal Super
ser ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : InvokeMethodOnNull
ou cannot call a method on a null-valued expression.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:242 char:5
SuperUserPolicy.PolicyRoleBindings.Add($WebApp.PolicyRoles.GetSpecialRole([
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : InvokeMethodOnNull
ou cannot call a method on a null-valued expression.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:245 char:5
     $SuperReaderPolicy = $WebApp.Policies.Add($PortalSuperReader, "Portal
uper ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : InvokeMethodOnNull
ou cannot call a method on a null-valued expression.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:248 char:5
SuperReaderPolicy.PolicyRoleBindings.Add($WebApp.PolicyRoles.GetSpecialRole
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : InvokeMethodOnNull
ou cannot call a method on a null-valued expression.
t D:\myworkspace\bif\CreateSP2013ClaimsWebApplication.ps1:251 char:5
     $WebApp.Update()
     ~~~~~~~~~~~~~~~~
   + CategoryInfo
: InvalidOperation: (:) [], RuntimeException
   + FullyQualifiedErrorId : InvokeMethodOnNull

Hi Benjamin,
If you're getting a Null Value error anywhere, that means a variable you're referencing isn't set to anything. If you're getting that try echoing out each variable after it's assigned to see if it's set to anything.
The link you are referring is for SharePoint 2010 and verified on Windows Server 2008 R2 and 2008, but not Windows Server 2012.
The approach in this case includes the following per the blog:
Check to see if a web application with the current specified URL is already in use – exit if it is
Check to see if an application pool with the name already exists. If so use it, otherwise create one
Create a web application based on the parameters specified
Assign the object cache properties to the new web application
Create policies for the object cache users to the web application
To simplified the code, we could use powershell below to check if web application and application pool have been already in use ahead. And skip the last two steps in the first time.
Get-SPWebApplication | fl displayname, applicationpool
Please refer to New-SPWebApplication
which is used to create a new web application within the local farm:
http://technet.microsoft.com/en-us/library/ff607931(v=office.15).aspx. Only two parameters i.e. ApplicationPool and Name are required, we could try a simple command at first:
Please run Get-SPManagedAccount to check the managed account, then execute the command below:
$ap = New-SPAuthenticationProvider
New-SPWebApplication -Name "Contoso Internet Site" -Port 2014 -ApplicationPool "ContosoAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "Domain\Administrator")
-AuthenticationProvider $ap -SecureSocketsLayer
Regards,
Rebecca Tu
TechNet Community Support

Threading with connection pool

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 ejp
Thx for the reply.
// Enable connection pooling
env.put("com.sun.jndi.ldap.connect.pool", "true");
Is this suffice to get the connection pool working,
Should i merely have a thread to maintain the connection with the ldap that uses sun's connection pool; or allow requestes to create new object for the connection and still this pool will hold.
for example in the above code instead to housekeep the thread merely maintain connection with the pool
or
should I directly connect each object with the ldap?
I am unable to understand how exactly sun's connection pool is working and how it should be used. I have gone thru the following example but picture is still hazy and undigestable to me.
java.sun.com/products/jndi/tutorial/ldap/connect/pool.html
Rgds

Connection Pooling in heavy traffic web-applications

Similar Messages

Maybe you are looking for