Thread count setting in WLS 7

Hello,
I would like to know if I can allocate a set of 'n' threads for a particular
business process in WLS 7.0. In WLS 5.1 there used to be threads for JMS, servlets
and the execute threads. Is it possible to achieve something similar in WLS 7
Thanks,
Aswin.

Hello Aswin,
Refer to the following link for more information regarding the creation of execute
queues:
http://edocs.bea.com/wls/docs70/ConsoleHelp/domain_executequeue_config.html
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Aswin Dinakar" <[email protected]> wrote:
>
Hello,
I would like to know if I can allocate a set of 'n' threads for
a particular
business process in WLS 7.0. In WLS 5.1 there used to be threads for
JMS, servlets
and the execute threads. Is it possible to achieve something similar
in WLS 7
Thanks,
Aswin.

Similar Messages

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.

Changing thread count in WebLogic 10.3

Hi
We have migrated from WebLogic 8.1 to 10.3.
how do i change the thread count in weblogic 10.3? i saw options in weblogic 8.1 and 9.2 but not in 10.3.
Can anybody throw some light on this.

From WL9.0 onwards, the Weblogic thread management mechanism is changed.Now no need to set the thread count. WLS itself is intelligent enough to do the self tuning of the thread pool.
To prioritize and schedule your application requests,you can create work managers and can associate request classes/constraints.You can refer the below article to understand the workload management using work managers.
http://www.oracle.com/technology/pub/articles/dev2arch/2006/01/workload-management.html
Inigo Prince

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

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

Storage Thread Count

I'm trying to write up advice for Storage node thread count.
Obviously, this is dependent of the machines - we have 48G 8processor machines, running 20 x2G Storage nodes and 2 x 2G Proxy nodes.
My understand is that when you don't have a cache-store you would set the thread-count to 0 (run on service thread).
I'm wondering how one might calculate this if you have a cache store ( and whether its different if you have write through / behind ).
I can see that in write-through it will spend most of the time with the database and a higher thread count would be good (its a pity its not a variable size pool with min and max).
I'm not sure about write-behind - I can imagine that a low thread count might be reasonable here.
I'm sure Rob (or others ) have a good formula for this.
Best, Andrew.

I have a brief recollection (may be wrong about this) that there is some info (via JMX) about average thread pool usage that may be of assistance (if the average is close to your specified max it may pay off to increase it furthe and see if throughput goes up or down, if the average is close to zero it may be just as well to use zero thread count rather than what is used at the moment).
One must also decide what is most important - to max out throughput or to limit median response time. With a larger thread pool more queries can be in progress at the same time (hopefully reducing median responce time since long runing queries dont lock out other queries) but resources will be split between them (at least if the thread count is larger than the number of cores) making the total throughput lower...
/Magnus

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.

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.

Threads minimum vs Threads Count

Hi,
What's the difference in teh execute queue between threads minimum and
threads count? Any comments will help!
Docs say:
Thread Count: Specify the number of threads assigned to this queue. If
you do not need to use more than 15 threads (the default) for your work,
do not change the value of this attribute.
Thread Minimum:
Specify the minimum number of threads that WebLogic Server should
maintain in this execute queue to prevent unnecessary overflow
conditions. By default, the Threads Minimum is set to 5
I don't undersatnd what "maintain in this execute queue" means?
Obviuosly, there will be 15 threads assigned to the execute queue.
When the "queue lengthh threshold" is reached, "Thread Increase" will be
added to number of threads, until a maximum of "Thread Maximum".
I don't know how "Threads Minimum" plays a role.
Thanks!
Q

Don't run into troubles, and don't misuse threads, the only thing that decides when your thread will execute is the Thread-scheduling system (which is part of the Java system) not you. So, you never must call run() to execute your thread, instead you always must use start(). The call of start() actually makes the scheduling-system to pay attention to your thread, and the calling of start() more than once will not have effect.

Coherence Extend Thread count is decimal number monitored from JMX

Hi,
We set a thread count in the proxy server configuration as 10 and we have two proxies.
In the JMX report we getting following information,
Connections=3, Cpu=72964ms (0.0%), Messages=63354, Throughput=868.2912msg/sec, AverageActiveThreadCount=4.710551E-4, Tasks=14670, AverageTaskDuration=4.410225ms, MaximumBacklog=6, BytesReceived=46.8MB, BytesSent=88.9MB, ThroughputInbound=0bps, ThroughputOutbound=0bps
Connections=8, Cpu=16164ms (0.0%), Messages=112401, Throughput=6953.786msg/sec, AverageActiveThreadCount=0.0049326043, Tasks=34702, AverageTaskDuration=10.976889ms, MaximumBacklog=3, BytesReceived=13.2MB, BytesSent=6.62GB, ThroughputInbound=0bps, ThroughputOutbound=718Kbps
AverageActiveThreadCount=0.0049326043
can someone explain why AverageActiveThreadCount is in decimal?
Thanks
Prab

Yes, because each "sample" changes the average, such that after 10 samples, if 5 times there were 2 threads busy and 5 times there were 3 threads busy, the average would be 2.5.
Peace,
Cameron Purdy | Oracle Coherence
http://coherence.oracle.com/

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-

Thread count higher than max worker threads... Large number of suspended worker threads

I have a SQL 2012 SP2 server that is getting High Thread count alerts in SCOM. looking into the issue I found some interesting things that I am now at a loss for. I have been searching around for a few hours now and havent found much other than
making it more confusing. I found this MSDN blog:
Are my actual worker threads exceeding the sp_configure 'max worker threads' value?
Running through that I found some interesting things.
-Max worker threads is set to default for x64 of 512 threads
running a thread count query found 547 current worker threads:
SELECT
SUM(current_workers_count) as [Current worker thread] FROM sys.dm_os_schedulers
Taking it a step further found that there was 523 worker threads in a suspended state with a last_wait_type of MISCELLANEOUS:
select is_preemptive,state,last_wait_type,count(*) as NumWorkers from sys.dm_os_workers
Group by state,last_wait_type,is_preemptive
order by count(*) desc
is_preemptive state last_wait_type NumWorkers
0 SUSPENDED MISCELLANEOUS 523
This is not yet a production server, no one is connecting to the database and the front end software application is not being used on this server yet. Essentially this is just an idle database server so I thought it might be a fluke, so I restarted
the sql services and the thread counts cleared. I left it alone and overnight the high thread count alert popped back up. I looked at it again this morning and the exact same thing happend. Same number of suspended workers etc and total worker
threads of 523 and 547 respectively.
Other than the one article I have found above I have not been able to find anything to help explain this or what the heck suspended miscellaneous worker threads are. Any help would be appreciated...Thanks!

Hello,
Please run the following query. The text column should tell us what is running.
SELECT
task.task_address,
task.parent_task_address,
task.task_state,
REQ.request_id,
REQ.database_id,
REQ.session_id,
REQ.start_time,
REQ.command,
REQ.connection_id,
REQ.task_address,
QUERY.text
FROM
SYS.dm_exec_requests
req
INNER
JOIN sys.dm_os_tasks
task on
req.task_address
= task.task_address
or req.task_address
= task.parent_task_address
Cross
apply sys.dm_exec_sql_text
(req.sql_handle)
as query
WHERE
req.last_wait_type
= 'MISCELLANEOUS'
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

When thread-count 65 /thread-count can imporve the performance

We are using very classical way get / put object with key for our application on embedding mode.
Application run on top Weblogic Server, Tangosol as embedding Lib.
in this case, tunning this parameter can improve performance or non?
Best regards.
Jerome
<invocation-scheme>
<scheme-name>InvocationScheme</scheme-name>
<service-name>InvocationService</service-name>
<thread-count>65</thread-count>
<autostart>true</autostart>
</invocation-scheme>

Hi,
if I understand well: When we are using embedding mode with Weblogic Server, we are using the thread distributed by WLS, we don't need any thread by invocable Service thread, Am I right?
attached is one Thread dump, we are seeing a lot of wait lock, some one can give a more clear explanation? Sorry, it's quite long, but i can't use attach mode. I can send the summary
Best regards.
Jerome
========================================================================
Dump Files
Stat Count
Thread/Locks     Dump_0     Dump_1     Dump_2     Dump_3     Dump_4     Total      Average     Lock Type
Total Active ExecuteThread     25     18     31     119     138     331
Total Waiting thread among Active ExecuteThread and with respect to Coherence related locks     22     15     28     116     134     315
1. Locks waiting by IMPI_IMPU_DAO.get_all_IMPU_of_IMSU_with_User_State(IMPI_IMPU_DAO.java:178)          25          DistributedCache$GetRequest$Poll
2. Locks waiting by IMPI_IMPU_DAO.get_all_IMPU_of_IMSU_with_User_State(IMPI_IMPU_DAO.java:186)          33          DistributedCache$GetRequest$Poll
3. Locks waiting by IMPI_IMPU_DAO.get_all_IMPU_of_IMSU_with_User_State(IMPI_IMPU_DAO.java:201)          40          DistributedCache$GetRequest$Poll
4. Locks waiting by IMPI_IMPU_DAO.get_by_IMPI_and_IMPU_ID(IMPI_IMPU_DAO.java:74)          8          DistributedCache$GetRequest$Poll
5. Locks waiting by IMPU_DAO.get_by_Identity(IMPU_DAO.java:201)     0     0     3     10     16     29     5.8     DistributedCache$GetRequest$Poll
6. Locks waiting by IMPU_DAO.get_by_Identity(IMPU_DAO.java:206)     0     0     7     23     1     31     6.2     DistributedCache$GetRequest$Poll
7. Locks waiting by IMPI_DAO.get_by_Identity(IMPI_DAO.java:105)     0     0     1     6     3     10     2     DistributedCache$GetRequest$Poll
8. Locks waiting by IMPI_DAO.get_by_Identity(IMPI_DAO.java:110)     0     0     0     3     7     10     2     DistributedCache$GetRequest$Poll
9. Locks waiting by IMSU_DAO.get_by_ID(IMSU_DAO.java:86)     2     0     2     4     9     17     3.4     DistributedCache$GetRequest$Poll
10. Locks waiting by Preferred_SCSCF_Set_DAO.get_all_from_set(Preferred_SCSCF_Set_DAO.java:81)     2     5     2     20     9     38     7.6     distributedCacheRequest.PartialRequest$Poll
11. Locks waiting by Preferred_SCSCF_Set_DAO.get_all_from_set(Preferred_SCSCF_Set_DAO.java:77)     1     5     0     0     12     18     3.6     distributedCacheRequest.PartialRequest$Poll
12. Locks waiting by CapabilitiesSet_DAO.get_all_from_set(CapabilitiesSet_DAO.java:77)     0     2     3     10     5     20     4     distributedCacheRequest.PartialRequest$Poll
13. Locks waiting by VisitedNetwork_DAO.get_by_Identity(VisitedNetwork_DAO.java:73)     0     0     2     15     5     22     4.4     distributedCacheRequest.PartialRequest$Poll
14. Locks waiting by IMPU_VisitedNetwork_DAO.get_by_IMPU_and_VisitedNetwork_ID(IMPU_VisitedNetwork_DAO.java:65)     1     0     3     4     6     14     2.8     DistributedCache$GetRequest$Poll
========================================================================

High thread count on store.exe

I understand that the mdb store process utilizes as much memory as is available. My question is regarding the thread count on the process. One of the three mailbox servers tends to have a higher thread count than the other two. It
usually ranges from 150 to 200 (while the other two are usually 130 to 150) but today it is a little over 300. The rpc thread count on all the mailbox servers stays pretty low (60 or under) and the rpc thread count on the CAS servers usually
hang out around 55-65, so that's all good. All three mailbox servers also use VERY close to the same amount of memory all the time, so that doesn't seem to be making a difference. I am just trying to determine why the thread count is noticably
higher. This server and one of other mailbox servers replicate the public folder database, and I can understand why that would account for some additional activity, but you would think the thread count would be higher on the other server with the public
folder database as well, but it stays pretty low. Hardware-wise these servers are all identical. So is there something I can monitor in perf mon for instance? I don't want to use experfwiz because that monitors everything under the sun and
I need it a bit more centralized. I have googled all over the place and the only thing I can find is that with newer versions of exchange this thread count ranges from 200-300 on heavy usage, and exch07 can handle up to 500 threads, so I can't even find
which specific things to monitor that directly correlate with this issue. So while I understand that it's not really too high, I would like to find out why it deviates from the norm if the other two servers are equal for all intents and purposes (same
hardware, balanced DAG. etc). I would like to mitigate any potential issues. Thank you.

Hi pchw,
Thank you for your question.
I am sorry that we could not find the specific things to monitor this issuer directly, because there are many reason which caused it. For example: virus, big size attachment in queue, hardware performance and so on. We could refer to the following steps
to troubleshoot:
Restart the service of “Microsoft Exchange transport”;
Create a new database and move mailbox to new mailbox;
We could do some disk health check if the load test is normal;
Collect related application log and system log to
[email protected] for our troubleshooting.
We could run SDP on Exchange server and send it to
[email protected] for our troubleshooting.
http://blogs.msdn.com/b/askie/archive/2012/05/22/introduction-to-support-diagnostics-platform-sdp.aspx
We could use tools and logs to analysis if there are anything wrong or abnormal on Exchange server 2013. our bottle neck is disk IO latency, store.exe do require some CPU usage, but if our disk IO speed can keep in a normal range, the
CPU usage will be smaller. Exchange is highly rely on disk IO performance because it need lots of IO operation regarding to transaction log and database file. If Disk IO has a high latency, I will definitely impact store.exe, if it`s getting seriously sometimes
it may cause store.exe no response.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/ee832791(v=exchg.141).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Thread count setting in WLS 7

Similar Messages

Maybe you are looking for