Re: Connection pooling

Peter Sharman wrote:

> No, your understanding is incorrect. Connection pooling is a way of
> overcoming the physical 32 bit limit of 64000 ports on a Unix box.

Wouldn't 32 bits give you 4294967296 ports as opposed to 64000 or more like the 65536 which is a 16 bit limit?

Anyway, the way I read the manuals, connection pooling provides a side effect of guaranteed connections because it will disconnect and reconnect as needed, in order to efficiently use the available ports. More like the disconnected record sets in ADO. Or am i still in fog. I got more information stating that i need an extra system to run the connection manager. If connection pooling is not the answer than what is? I have apps that do not handle loosing the connection to the server and they have to stay up all the time ;-).

> I don't
> know of anyone whose tried getting that high a user count on NT!

Neither do I. I am having problems with more than 32 !

>
>
> HTH.
>
> Pete
>
> Dee Csipo wrote:
>
> > Hi,
> >
> > Correct me if i am wrong but connection pooling allows the creation of
> > permanent, guaranteed connections between a client and a server. Does
> > anybody have experience with this feature on ORACLE 8.0.4 on NT 4.0? I
> > am planning to rely on it for a 7/24 system. Is it wise?
> >
> > dee
> > ;-D
>
> --
>
> Regards
>
> Pete
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Peter Sharman Email: psharman_at_us.oracle.com
> WISE Course Development Manager Phone: +1.650.607.0109 (int'l)
> Worldwide Internal Services Education (650)607 0109 (local)
> San Francisco
>
> "Controlling application developers is like herding cats."
> Kevin Loney, ORACLE DBA Handbook
> "Oh no it's not! It's much harder than that!"
> Bruce Pihlamae, long term ORACLE DBA
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Received on Wed Feb 10 1999 - 22:09:49 CST