Configuring Execute Thread Count

Hi,
I am working on a webapp thats using Weblogic 8.1 (SP2) as the application server.
The admin server for Weblogic currently provides 2 execute threads as default.
However I was wondering if I can configure the admin server for a higher number
of execute threads.
I have the following questions:
1.> Does configuring the number of threads for the admin sever provide any additional
value? has any one come across a big application where more than 2 execute threads
are required for the admin server?
2.> If yes, is it possible to configure the number of execute threads for the
admin server? I did some search on the bea website and didnt find anything that
explicitly says that the property is configurable. Is this true?
3.> If it is configurable, then how do we go about setting it up?
If anyone has worked around this and can provide me with any information or references,
that would be great.
Thanks

          Sriram,
          Take a look at the following URL for setting the thread count in WLS 6.1
          http://edocs.bea.com/wls/docs61/perform/WLSTuning.html#1112343
          Chuck Nelson
          Developer Relations Engineer
          BEA Technical Support

Similar Messages

Change the Execute Thread Count im weblogic9.2

Hi
I am trying to change the execute thread count in weblogic 9.2 but i am not able to find the location in weblogic Console to change it can any one help me

Hi,
In previous versions of WebLogic Server, processing was performed in multiple execute queues. Different classes of work were executed in different queues, based on priority and ordering requirements, and to avoid deadlocks. In addition to the default execute queue, weblogic.kernel.default, there were pre-configured queues dedicated to internal administrative traffic, such as weblogic.admin.HTTP and weblogic.admin.RMI. Now the Same thing is done using WorkManagers...
WebLogic Server, Version 8.1 implemented Execute Queues to handle thread management which allowed you to create thread-pools to determine how workload was handled. WebLogic Server still provides Execute Queues for backward compaitibility, primarily to facilitate application migration. However, new application development should utilize Work Managers to peform thread management more efficiently.
You can enable Execute Queues in the following ways:
* Using the command line option*
-Dweblogic.Use81StyleExecuteQueues=true
So in that Case ...*config.xml* entry will be like this:
<server>
<name>AdminServer</name>
<execute-queue>
<name>weblogic.kernel.Default</name>
<queue-length>256</queue-length>
</execute-queue>
<use81-style-execute-queues>true</use81-style-execute-queues>
<listen-port>7001</listen-port>
<web-server>
<web-server-log>
<file-name>../../logs/admin_access.log</file-name>
</web-server-log>
</web-server>
<listen-address>aaa.bbb.com</listen-address>
</server>
for more detailed Information Please refer to:
http://download.oracle.com/docs/cd/E11035_01/wls100/config_wls/self_tuned.html
Edited by: Jay SenSharma on Jan 20, 2010 3:42 PM

How do you modify the default Execute thread count in Weblogic Server 9.2?

How do you modify the default Execute thread count in Weblogic Server 9.2?
How can you tune the starting number of weblogic.ExecuteThread on server startup and/or set minimum number?
Is there an option from the console?
Please let me know.
Thanks

Self tuning will automatically manage the threads but however you can still control the min and max by adding the min and max values for each instance either directly adding in config.xml or through JVM settings
1) Modifying the config.xml
Just add the following line(s) to each server definition :
<server>
<name>AdminServer</name>
<self-tuning-thread-pool-size-min>100</self-tuning-thread-pool-size-min>
<self-tuning-thread-pool-size-max>200</self-tuning-thread-pool-size-max>
</server>
2) Adding some JVM parameters
It's safer the following way :
add the following option in your command line : -Dweblogic.threadpool.MinPoolSize=100
Regards
RR

Query Regarding Execute Thread Count

Hi,
My understanding of Execute Thread Count is the threads which are assigned to service
requests coming to Weblogic Server.
In our current architecture a request for generating report is directed to EJB method
which makes a call to another Server (Report Server for executing reports), the report
Server in turn calls the EJB residing on Weblogic Server for getting the data.
So, is my assumption correct that with our current architecture we are limited to
concurrency of Execute Thread Count -1. (Every request for report will consume 2
Excute threads, and others will have to wait till the first request gets completed
and 2 threads are freed).
I also read from the postings that Weblogic takes some of the threads, so it actually
will be limited to (Execute thread count - Weblogic Held- 1).
Please corect me if I am wrong.
Thanks and Regards
Rashmi

Hi,
Thanks very much for the suggestion. I tried, and it is using 2 Execute Threads.
Thanks
Rashmi
"Dave Martin" <[email protected]> wrote:
>
Rashmi:
If you are interested in answering the question rigorously, why not just
throw a
fake exception along both the report generation path and the runReport method
of
the ReportServer, then record their stack traces to a file for comparison?
From the sounds of it, your app wants to make the actual report generation
asynchronous
from the post of the reporting request. If they're really asynchronous,
then your
ReportServer must have some kind of blocking queue that will "wake up" when
it has
work to be done. Depending on how you implemented this, your runReport
method may
not be running a WebLogic execute thread at all.
Seems to me that you should be thinking of this as consuming one execute
thread regardless.
Even if the two pieces of work are asynchronous, the first thread finished
its work
at the point that it posts to the second thread (at least, per your description).
So at any one time, at max one execute thread is being consumed per request.
But capture the stack traces and have a look for yourself.
Dave Martin
"Rashmi S" <[email protected]> wrote:
Hi,
Thanks for your reply.The reason why I say 2 threads will be consumed is
as follows
1. First execute thread will be used for the request to Weblogic Server
to run the
report originating from a client.
2. Now, within the ReportServices EJB there is a call to Report Serverto
run the
report. The running of report is done on the Report Server which is ona
separate
m/c. Within the runReport method of the Report Server ,the data is fetched
for the
report by making a context look-up of another session EJB which fetches
the data.
So, the second Execute thread will be consumed for executing the EJB that
fetches
the data.
Am I correct?
Thanks and Regards
Rashmi
"Cameron Purdy" <[email protected]> wrote:
Incoming requests (from outside the server) use one thread for the duration
of their processing. Previous to their processing they are queued until
a
thread is available. So you would use one thead per concurrent request,
not
two. Otherwise, it sounds right.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Rashmi S" <[email protected]> wrote in message
news:[email protected]...
Hi,
My understanding of Execute Thread Count is the threads which are assignedto service
requests coming to Weblogic Server.
In our current architecture a request for generating report is directedto EJB method
which makes a call to another Server (Report Server for executingreports), the report
Server in turn calls the EJB residing on Weblogic Server for getting
the
data.
So, is my assumption correct that with our current architecture we arelimited to
concurrency of Execute Thread Count -1. (Every request for report willconsume 2
Excute threads, and others will have to wait till the first request
gets
completed
and 2 threads are freed).
I also read from the postings that Weblogic takes some of the threads,so
it actually
will be limited to (Execute thread count - Weblogic Held- 1).
Please corect me if I am wrong.
Thanks and Regards
Rashmi

Thread count tuning

Hi!
We are running a weblogic 5.1 server for jsp/servlet/ejb behind an apache web
server, via the wls/apache bridge. As the number of users increased we expereienced
slow response times. We checked thread dumps from peak hours and saw that all
servlet threads were busy writing to network sockets. Still, if we check the internet
line usage, we are not using up all our bandwith.
We've managed to solve this by adding more threads to our wls server (36 servlet
threads, 46 totally). This has however slowed down our database somewhat since
we have to increase the connection pool size with the number of server threads.
So my question would be: is there some other, more elegant, way to solve this?
Having 46 execute threads seems pretty much (15 is recommended from BEA). Ideally
I would like the wls threads to write their results as quickly as they can to
the apache server, disconnect from the socket and leave actual work of writing
all the data back to the end user's browser to apache. My network knowledge is
pretty limited so I'm not sure if this is possible.
/Mattias

Why do you need to have the maximum thread count equal to the maximum number of simulatneous users? You'll never end up with a system that has 60,000 threads.
If you are doing traditional-style HTTP, then typically you can support many thousands of users with just a few threads. For example, our SPECjAppServ er submissions use about 40 threads to handle 4000 clients. It all depends on how many requests each client actually makes per second, and how long each request takes. If the clients are idle for long periods of time, you could handle 10s of thousands with just a few threads.
The keep-alive tuning is also critical in that scenario, as the server will eventually start disconnecting clients, who will re-create the TCP connections. That works seemlessly from a functional point of view, but isn't necessarily the optimal thing for performance.
On the other hand, if you're trying to use a Web 2.0-style HTTP request where you simulate server pushes by having the servlet request block, then yes, in 8.1 you will need one thread per client, but you'll be bound by OS and other system constraints on the number of threads the process can have. You'd be much better off in that case using the Asynchronous Request processing features being added to AS 9.1 (see Sun's project glassfish for details).
For information on configuring the thread count for 8.1, see:
http://docs.sun.com/source/819-0215/httpservice.html
In particular -- the section on Configuring HTTP Service Request Processing Threads.

Oc4j thread count under linux

hi all !
i have a memory problem on my as903 on linux and now i'm confused about why there are 18 oc4j threads started for my 5 deployed applications (not to mention the others for administration!??).
right now i wonder if there is a way to configure this thread count ?
anyone of you solved this problem ?
alois

OC4J 903 releases and later have a configurable thread-pool, where you can set the upper and lower bounds for the number of threads to use.
I don't know that this will be the cause of the memory problem you mention, but if you want to tune it, then see: http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97677/advanced.htm#1011968
cheers
-steve-

Execute queue thread count set back?

I have a script which automatically sets up execute queues (and their thread counts) for either an admin server or two managed servers in a cluster (depending on whether it's a standalone deployment). Upon building a domain, the script connects to a temporary server and sets everything up, at this point it appears all the queues and thread counts are set correctly. However once the build has completed and the generated config.xml is checked, three queues don't have any thread counts associated with them at all; these queues are:
ThreadQueue (Count)
wli.internal.ProcessInstanceInfo (15)
wli.internal.ProcessTracking (15)
wli.process.event.thread.pool (15)
The other queues have all their thread counts set correctly. Does anybody know how these queues are used and if this will have an impact on the above problem?

No worries about this post, the reason has been solved.
Reason
The default thread count for execute queues in development mode is 15 threads, therefore if a queue is specified with this value it won't be set in the config.xml (when an execute queue doesn't have a ThreadCount attribute, the default is used instead). The trouble is that when the server is started we enter production mode where the default thread count is 25 threads instead.

OnAlarm/wait thread count configuration in BPEL

BPEL 10g, We have a com.oracle.bpel.expirationAgent.threadCount property to set the thread count for OnAlarm/wait. ORACLE_HOME/bpel/domain/DOMAIN_NAME/config/resources-quartz.properties.
BPEL 11g, Can you please point me the configuration file to set the thread count for OnAlarm/wait. I could not find the resources-quartz.properties in SOA 11g.

Have you been able to find the file or a similar properties location in 11g? I am also looking for it.

Thread count in a distributed service

Hi,
     i needed some information on the thread-count attribute in a distributed service. i would like to know how do we decide on the thread count. would increasing the thread count in the tangosol-coherence.xml increase the performance of tangosol as well.
     looking forward to your help
     Thanks
     Jigs

To go into this a bit further...
     Each service instance has its own primary thread. This thread has the option of using its own isolated thread pool if the thread-count is greater than zero. If the thread-count is zero, then all work will be performed by the primary service thread. If the thread-count is greater than zero, then all work will be performed by the thread pool (the primary thread acts as a task coordinator).
     Note that the thread-count is per-service and per-cluster-member. Each cache service has a unique name. The CacheFactory class uses a single cache service instance for each cache type (Replicated/Distributed/etc). If you manually create additional cache services, they will each have their own isolated thread pools.
     Additionally, each Invocation service has its own thread pool. This setting is very important as the Invocation service is quite often used to execute long-running user tasks. If the thread pool is saturated with user tasks, then further calls to the Invocation service will block until user tasks complete and threads become available. Using named Invocation service instances will allow you to isolate critical tasks for better application availability.
     Note that this information is current as of Coherence 2.5, but may change in future releases as threading models have a huge impact on performance and scalability. Having said that, there are no significant changes planned at this point in time.
     Jon Purdy
     Tangosol, Inc.
     =================
     Added 2004-12-02 by JP:
     Also, as a very specific instance, the backup copy(ies) of a distributed cache are created on the service thread ... this means that while backup copies are being created on a node, no new tasks will be dispatched to that service's thread pool. For in-memory backup copies, this is actually optimal as adding an item to a HashMap/HashTable is roughly as fast as handing it off to another thread. However, if the backup-copy is configured to disk-based storage (or other high-latency resource), an asynchronous backup implementation should be used to eliminate latency. See AsyncBinaryStore for more information.

How to Increase min number of executable threads in Weblogic 10.3.0

Hi,
I was trying to increase the Min number of executable threads using the following startup argument
"set USER_MEM_ARGS=-Dweblogic.threadpool.MinPoolSize=30" in startWeblogic.cmd. But doing so haven't increased the "execute thread total count" to the desired number when I verified it in console.
Kindly help me to configure this.
PS: Changing the configuration file (config.xml) is not recommended.
Thanks
Prasanth

In 10.3 usually work managers are used for this purpose. (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/upgrade/compat.html#wp1117123)
You can use the 8.1 thread pool if you want (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/perform/appb_queues.html#use81)
but generally work managers are the preferred way: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_wls/self_tuned.html
Coming back to your original question:
"I was trying to increase the Min number of executable threads using the following startup argument "set USER_MEM_ARGS=-Dweblogic.threadpool.MinPoolSize=30" in startWeblogic.cmd. But doing so haven't increased the "execute thread total count" to the desired number when I verified it in console."
Can you add the option in the setDomainEnv file, located in the ${DOMAIN_HOME}/bin directory, for example,
@REM *************************************************************************
set WL_HOME=C:\bea\wlserver_10.3
for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
set BEA_JAVA_HOME=C:\bea\jrockit_160_24_D1.1.2-4
set USER_MEM_ARGS=-jrockit -Xms512m -Xmx512m -Xgc:throughput -Dweblogic.threadpool.MinPoolSize=100
set SUN_JAVA_HOME=To check if it indeed shows the number of threads you can follow the steps presented here: http://m-button.blogspot.com/2009/02/tuning-default-workmanager-on-weblogic.html

Consumers count = thread count ?

          Hello,
          I've implemented on a wl cluster (10 6.1sp4 instances, patched with CR091195)
          the approximated distributed destination pattern.
          In my case the destination is a queue.
          Every wl instance has thread count = 100.
          I have 1 mdb, non transactional, and I haven't configured the max-beans-in-free-pool.
          It happens, when I deploy the MDB, targetting it to the cluster, that I can see
          on every wl instance (I have a monitoring program):
          JMSRuntime.connectionsCurrentCount = 1
          JMSConnectionRuntime.sessionsCurrentCount = 100 (I have only a "connection4116")
          JMSDestinationRuntime.consumersCurrentCount = 100 (I have only 1 queue)
          Why do I have all of these active consumers/sessions ?
          (and I haven't yet run my jms client)
          Thanks in advance
          Best Regards
          Mark


          Hi Mark,
          Before 6.1SP5, each MDB pool initializes
          Math.min(default-execute-thread-pool-size,
          max-beans-in-free-pool)
          consumers and sessions.
          For 6.1SP5 and later, each MDB pool initializes
          Math.min(default-execute-thread-pool-size/2 + 1,
          max-beans-in-free-pool)
          consumers and sessions.
          WL 7.0SP? (SP3 maybe?), and 8.1
          allow MDBs to use the "dispatch-policy" descriptor field
          and so assign themselves to a different
          thread-pool. In which case initialized max concurrent
          instances becomes:
          Math.min(custom-thread-pool-size,
          max-beans-in-free-pool)
          I think that the max-beans-in-free-pool default is
          some very high number. (At one point it was 1500).
          The consumer instances will not necessarily all use
          a thread at the same time, as they do not use
          up a thread when they are not operating on a
          message. In essence, thread usage depends on how
          slow the receivers are, how fast the producers are, and
          what other resources are also using
          the thread pool.
          I recommend tuning max-beans-in-free-pool so that total
          instance count on a server is somewhat less than
          the the thread count. This helps prevent dead-locks
          where all threads are running app code, and none
          are left to do other work.
          In case you are unaware, I also recommend
          using less than 100 threads unless the the
          app typically blocks a thread for long periods of time.
          The reason is that lots of threads may negatively
          impact performance, the operating system ends up
          burning CPU switching itself between threads
          rather than doing actual work.
          Each MDB deployment uses a single connection.
          Hope this helps,
          Tom, BEA
          P.S. The above information will be in the next
          iteration of the JMS Performance Guide white-paper,
          which I've currently started working on again.
          "Mark Cordobal" <[email protected]> wrote:
          >
          >Hello,
          >
          >I've implemented on a wl cluster (10 6.1sp4 instances, patched with CR091195)
          >the approximated distributed destination pattern.
          >In my case the destination is a queue.
          >
          >Every wl instance has thread count = 100.
          >
          >I have 1 mdb, non transactional, and I haven't configured the max-beans-in-free-pool.
          >
          >It happens, when I deploy the MDB, targetting it to the cluster, that
          >I can see
          >on every wl instance (I have a monitoring program):
          >
          >JMSRuntime.connectionsCurrentCount = 1
          >JMSConnectionRuntime.sessionsCurrentCount = 100 (I have only a "connection4116")
          >JMSDestinationRuntime.consumersCurrentCount = 100 (I have only 1 queue)
          >
          >Why do I have all of these active consumers/sessions ?
          >(and I haven't yet run my jms client)
          >
          >
          >Thanks in advance
          >
          >Best Regards
          >
          >
          >Mark

Identifying Execute Threads as Socket Readers

Hi All,
Preface: I am trying to identify at any given instance the percentage of
socket reader threads that are in use - this will help me to identify when
all threads are in use and unable to service user requests. Thus my goal is
to identify threads that are socket readers and whether they are active or
idle.
Through JMX I can obtain an instance of each
weblogic.management.runtime.ExecuteThread, which lists the same information
that you see in the console if you drill down to the thread level, for
example:
mydomain> Servers> myserver> Active Execute Queues> default> Execute Threads
That information includes:
- thread number
- total requests
- last request
- current request
- transaction
- user
- is the thread idle?
Now my question is from this information can you identify which of these
threads are being used as socket readers?
Here are some excerpts from my JMX calls:
Name: ExecuteThread: '0' for queue: 'default'
Execute Queue Runtime Name: default
Current Request: null
Last Request: Http Request: /bookstore/en/authors/showauthors.jsp
User: null
Is Idle?: true
Name: ExecuteThread: '15' for queue: 'default'
Execute Queue Runtime Name:default
Current Request: null
Last Request: Scheduled Trigger
User: null
Is Idle?: true
Name: ExecuteThread: '26' for queue: 'default'
Execute Queue Runtime Name:default
Current Request: null
Last Request: ListenRequest for a new connection on: 'Socket
addr=127.0.0.1,port=2061,localport=7001]'
User: null
Is Idle?: true
Name: ExecuteThread: '59' for queue: 'default'
Execute Queue Runtime Name:default
Current Request: Socket Reader Request
Last Request:
we[email protected]
User: null
Is Idle?: false
It would appear that the "ListenRequest" last request would identify a
socket reader, only I have 60 threads in my default execute queue with 70%
dedicated to socket readers and the number of threads that say their last
request was "ListenRequest ..." is only 5.. Furthermore there is only one
"Socket Reader Request" identified thread.
Are threads identified as socket readers permanently or constantly reused
for whatever purpose is required (with a cap of use based off of the socket
reader perspective)?
Thanks in advance for your help!
Steve

Hi Achhi,
Socket Reader Threads are the Threads which are responsible for reading the incoming request data. We can divide the Socket reader threads in two categories:
Pure Java Socket Reqders: The pure-Java socket reader implementation, where the socket reader threads continually poll all opened sockets to determine whether they contain data to be read, even if the sockets have no data to read. (From Performance Point This is Not Good that the Sockets will be in Opened Mode even if there is no Data to read)
Native Socket Readers: (These are the Dafault Socket Readers) The native IP socket reader provided by the host machine's operating system, where the socket reader threads target only active sockets that contain data to be read. Native socket readers never poll sockets because they are immediately notified when a socket needs to be serviced. For Better Performance You should always prefer using Native Socket Readers.
To Enable Native Socket Readers You can Login to AdminConsole--->Servers ---><SERVER_NAME>--->configuration (Tab)--->Tuning (SubTab)---> "Enable Native IO" (This checkbox must be checked)
Still If you want to use the Java Socket Readers .... still you can improve the performance of socket communication by configuring the proper number of socket reader threads for each server instance. For best performance, the number of socket reader threads in WebLogic Server should equal the potential maximum number of opened sockets.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

Why are the weblogic.kernel.Default Execute Threads used by WLS Kernel

In my Admin Console, it's displaying 10 out of the 15 weblogic.kernel.Default Execute Threads are used by the WLS Kernel user. The total requests column for these threads are showing 0. The other 5 threads are showing 20K to 40K requests. Why is the WLS Kernel users hogging these threads and not allowing the applications to use them?

Hi,
As work enters a WebLogic Server, it is placed in an execute queue. This work is then assigned to a thread within the queue that performs the work.
By default, a new server instance is configured with a default execute queue, weblogic.kernel.default, that contains 15 threads.
Go through the following link and find the usefull information on this issue.
http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_executequeuetable.html
Regards
Anilkumar kari

Thread Count Vs no of simultaneous users

Hi,
I have been testing my customer made adapter on WLI2.1 and WLS6.1SP1 for
simulataneous users access.
I found that as long as the no of simultaneous users is less than the Thread
Count defined for WLI, it works fine.
But if the no of users exceed the thread count, the server hangs.....idle
threads become 0.
Does my Thread Count always have to be greater than the no of simulatneous
users am expecting ?
Thanks
Amit

In my openion, yes, number of threads configured should be greater than simultaneous users.
Thanks
Niranjan

Thread Count and Out Of Memory Error

Hi,
I was wondering if setting the ThreadPoolSize to a value which is too low can
cause an out of memory error. My thought is that when it is time for Weblogic
to begin garbage collection, if it does not get a thread fast enough it is possible
that memory would be used up before the garbage collection takes place.
I am asking this because I am trying to track down the cause of an out-of-memory
occurrence, while at the same time I believe I need to raise the ThreadPoolSize.
Thanks,
Mark

Oops ...
I was wondering if setting the ThreadPoolSize to a value which is too
low can cause an out of memory error.No, but the opposite can be true.
My thought is that when it is time for Weblogic
to begin garbage collection, if it does not get a thread fast enough it is
possible that memory would be used up before the garbage collection
takes place.Weblogic doesn't do GC ... that's the JVM and if it needs a thread it will
not be using one of Weblogic's execute threads.
> I am asking this because I am trying to track down the cause of an
out-of-memory occurrenceIt could be configuration (new vs. old heap for example), but it is probably
just data that you are holding on to or native stuff (e.g. type 2 JDBC
driver objects) that you aren't cleaning up correctly.
while at the same time I believe I need to raise the ThreadPoolSize.Wait until you fix the memory issue.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Mark Glatzer" <[email protected]> wrote in message
news:[email protected]..

Configuring Execute Thread Count

Similar Messages

Maybe you are looking for