• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Maximum Connections in Weblogic.. please Help

Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
I am doing a kind of server push mechanism for which i need to make teh HTTp connection active throughout.
Can somebody tell me what is teh maximum number of HTTP Connections could be open at a time in WEBlogic.
I read some where it depends on Execute Threads ,
Can somebody tel me a very good approximation on this.
TEH situations demands that conenction will never be closed.
Thnaks in advance ,
Hope to hear from you all Soon
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The total number of simultaneous operations that may be performed is dependent on the default Execute Queue Thread Count, unless you specify a different Execute Queue for your application. JMS threads pull from a different Thread Pool, so they don't figure into the total. The Administration Console has its own Execute Queue, so it also does not figure into the total. Since you are keeping operations active for your server push, I am assuming you will need at least one thread for each connection that must be maintained plus extra for any other processes that must run.
My suggestion is to set the thread count to a mildly high number and monitor the thread use. In the Performance tab of the Monitoring Option for your Server there is an idle thread count. If you are constantly seeing a large number of idle threads then you will know the thread count is too high. On the other hand, if the idle count is always zero than you will know the number is too low.
Be warned, putting the thread count too high can severely impact performance.
I also suggest you read this document: WebLogic Server Performance and Tuning.
Let me know how things go.
[ December 27, 2002: Message edited by: Chris Mathews ]
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic