Mladen, Probably, something is very wrong with application design. >With iPlanet, it looks like this: >Application invokes bean, pumpkin or servlet which has something to do >with oracle. The app server pooling mechanism will allocate one of the >already established dedicated server connections, which will perform the >work. When the same user executes another vegetable (EJB or servlet), he >or she may do so within a different dedicated server connection. We have a >situation in which a single user utilizes several dedicated server connections >within a single logical screen.
Usually application server is smart enough (we use Weblogic) to reuse same physical connection if any number of calls comes from any different places once all the calls are a single transaction. I can imagin single call to allocate more than one connection if more than one transaction contexts required for this call (although, smartest app servers and the best databases can optimize even this transaction can be suspended and then resumed after another transaction commits), but it must be some very special need - it is not common what I'm saying. Single logical screen probably cannot use connections at all: screen means control is on users side means transaction should not be opened means no connection assigned . So, it's probably not an architecture's fault, it's design issue. Regards Vadim -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Gorbounov,Vadim INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
