You can also limit the number of connections per dispatcher with the (CONNECTIONS=) attribute of the MTS_DISPATCHERS initialization parameter. This also does not queue incoming connections, but causes incoming connections to hang, then time out.
It sounds like what Andrey needs is a function of the application software, not the database. -- Jeremiah Wilton http://www.speakeasy.net/~jwilton On Wed, 20 Mar 2002, Jeroen van Sluisdam wrote: > The only way to limit your connections is through the > max_sessions parameter. As far as I know there is no > queuing mechanism for this available. > About the price, only thing we experienced is dramatic performance > in certain batch applications which run through sqlnet. In these cases > you should use dedicated connections. > > -----Oorspronkelijk bericht----- > Van: Andrey Bronfin [mailto:[EMAIL PROTECTED]] > > I've done some RTFM but have not found any answer to this: > i want to limit the number of open sessions to some number (let's say 1000). > I want the next coming connections (after 1000) to be queued on the > dispatcher until one of the previous sessions drops/disconnects. > Is it possible ? > Also , what is the "price" of establishing a MTS connection compared to > "price" of establishing a dedicated conenction , performance-wise ? > Thanks a lot in advance. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
