I understand that this value is only the MAX value, usually the pool will start at 5 connections and increase when necessary.
But that value has nothing to do with this error. this error comes from the DB so you have to look for the properties of the DB to increase this value.
BUT BUT before doing that, it is very rare that you will need the 100 connections. You may not be closing the connection
You have to close it like this when you stop using it (ensure that when the server responses you already closed the connection)
to allow the server to recycle that connection. Believe me, a pool with a limit of 5 connections will allow you to serve hundred of customers. this is because the pool is very fast on making the connection when needed.
Also, because the error is DB related and not from the pool, take into consideration that more than one app (for example, you on your dev pc, and then production server) are requesting the connections. so even if you have one single connection to the DB on the production server, you may not be able to connect if for example you are connecting from your pc with a debugging app.[/code]