Hi, as I understand documentation of weblogic, if there is more requests then threads, container serialize request, so request is executed immediately after running thread finish previous request and is free. Weblogic 5.1 is using by default 15 threads for ejb container. About db connection pool, it's recommended use number of connection same or higher then number of threads (you can set number of connection in pool less then number of threads but then you can experience problems with SQLException : connection not available when high load of server). This recommendation seems to be very logical, when you close connection immediately after you finish request to db, then each thread (and in this case each concurrent request) is using exactly one connection. After all: Number of threads limits number of requests executed in same time, increasing number of threads increase the number of requests handled concurrently, but can also significantly increase usage of CPU and memory on application server. What is best for your application you can find by running some stress tests of application, in most cases the default 15 threads is enough (this mean you can have 15 concurrently running requests, but number of open sessions can be totally different, consider this: 100 users is connected to your e-zine application, 90 of them is reading article, and only 10 is in phase login/logout or requesting article and so on == only 10 threads is used, and 5 is still in the pool)
Hope this helps. Rah > -----Original Message----- > From: John Harby [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 04, 2001 3:03 PM > To: [EMAIL PROTECTED] > Subject: Re: vendor specific (Weblogic 5.1 / service pack 10) > > > You'll probably get better answers posting these questions at > http://newsgroups.bea.com/cgi-bin/dnewsweb > but have you done any profiling of this scenario? If you are both > CPU and memory bound you may want to increase the execute threads > but I would first try increasing the db connection pool size. > > > >From: Praveen Vijayan <[EMAIL PROTECTED]> > >Reply-To: Praveen Vijayan <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: vendor specific (Weblogic 5.1 / service pack 10) > >Date: Tue, 4 Dec 2001 12:59:21 +0530 > > > >Hi, > > > >This question is related to specifying number of execute > thread counts for > >an application in weblogic.properites file. > > > >Let us say at a given point in time, 60 concurrent hits (60 database > >requests) are there should we have to define execute thread > counts as 60??? > > > >We have currently defined the execute threadcounts as 30. > > > >Should the execute threadcounts = no maxconnections set in the > >connectionpool property > > > >Weblogic documentation says unnecessariliy one should not > increase no. of > >execute threadcounts but if there are more users to be > served at a given > >point of time is this point valid? > > > >Regards, > >Praveen > > > >============================================================= > ============== > >To unsubscribe, send email to [EMAIL PROTECTED] and > include in the body > >of the message "signoff EJB-INTEREST". For general help, > send email to > >[EMAIL PROTECTED] and include in the body of the message "help". > > > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > ============================================================== > ============= > To unsubscribe, send email to [EMAIL PROTECTED] and > include in the body > of the message "signoff EJB-INTEREST". For general help, > send email to > [EMAIL PROTECTED] and include in the body of the message "help". > > ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
