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.

Similar Messages

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.

Identifying Execute Queue 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:
weblogic.transaction.internal.ServerCoordinatorDescriptor$2@138786
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)

Execute Queue configguration reset.

Suppose if one has a WL domain with admin server and managed server as01 running
on host1, managed server as02 on host2, as03 on host3 and as04 on host4.
While rstarting the domain after a code update...
1. started admin server on host1
2. started as01 on host1
3. started as02 on host2
4. started as03 on host3
5. accidently tried starting as04 on host1 as opposed to host4.
Wl server bailed out after attempting to start as04 on host1 with the following
exception:
<Nov 12, 2003 8:49:57 AM PST> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for:
113.130.234.101, port: 8001. java.net.BindException: Cannot assign requested address
Perhaps the address 113.130.234.101 is in
correct or another process is using port 8001.>
<Nov 12, 2003 8:49:58 AM PST> <Emergency> <Security> <090085> <Server failed to
bind to any port such that it is not reachable
from the console.>
<Nov 12, 2003 8:49:58 AM PST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exc
eption>
The WebLogic Server did not start up properly.
Reason: Fatal initialization exception
Exception: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
- with nested exception:
As a side affect, WL admin server reset execute queue the config setting for all
the managed servers. The config file got changed from
<ExecuteQueue Name="default" ThreadCount="300"
ThreadPriority="6" ThreadsIncrease="10"/>
<IIOP Name="as01"/>
to
<ExecuteQueue Name="default" ThreadCount="15"/>
in the config.xml file after the failed start of as04.
Any idea why WL did such a thing?

Hi Dhilip,
Please post this question to the following newsgroup:
weblogic.developer.interest.general
Vitaly Yurik
"Dhilip Krishnan" <[email protected]> wrote:
>
Suppose if one has a WL domain with admin server and managed server as01
running
on host1, managed server as02 on host2, as03 on host3 and as04 on host4.
While rstarting the domain after a code update...
1. started admin server on host1
2. started as01 on host1
3. started as02 on host2
4. started as03 on host3
5. accidently tried starting as04 on host1 as opposed to host4.
Wl server bailed out after attempting to start as04 on host1 with the
following
exception:
<Nov 12, 2003 8:49:57 AM PST> <Emergency> <WebLogicServer> <000350> <Unable
to
create a server socket on Channel Default for:
113.130.234.101, port: 8001. java.net.BindException: Cannot assign requested
address
Perhaps the address 113.130.234.101 is in
correct or another process is using port 8001.>
<Nov 12, 2003 8:49:58 AM PST> <Emergency> <Security> <090085> <Server
failed to
bind to any port such that it is not reachable
from the console.>
<Nov 12, 2003 8:49:58 AM PST> <Emergency> <WebLogicServer> <000342> <Unable
to
initialize the server: Fatal initialization exc
eption>
The WebLogic Server did not start up properly.
Reason: Fatal initialization exception
Exception: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected
Exception
- with nested exception:
As a side affect, WL admin server reset execute queue the config setting
for all
the managed servers. The config file got changed from
<ExecuteQueue Name="default" ThreadCount="300"
ThreadPriority="6" ThreadsIncrease="10"/>
<IIOP Name="as01"/>
to
<ExecuteQueue Name="default" ThreadCount="15"/>
in the config.xml file after the failed start of as04.
Any idea why WL did such a thing?

Different execute queues with different thread priorities

We are running WebLogic 6.1, SP2 on Solaris 2.8 and I have a question related to the
use of Execute queues
I'm aware that the administration console servlets, and the rest of requests given
to the server run in separate execution queues each with their own pool of threads.
There is an <executequeue> element in the config.xml that allows you to change the
parameters of the default execute queue that most requests are handled in.
My question is is it possible to create new execute queues, each with a given number
of threads running at a different priority. Then one could assign a particular WAR
deployment to a queue and hence control the priority that certain requests run at
governed by the deployment that received the initial request.
Essentially the problem that I'm trying to address is that I have a JAR with MDBs
in it. I also have JARs with Entity and Session EJBs and WARs. They are all using
the same pool of threads to execute. I want to be able to throttle the MDBs as they
receive messages so they don't take over the machine and interfere with interactive
use. Now I can limit the number of MDBs in the MDB pool, but then if the machine
is not being used by users, then the machine resources are wasted only allowing one
MDB to be active at a time when there are a lot of messages in the queue.
What I want to be able to do is to have as many MDBs run as I can, up to a certain
limit, say 15 for example, but not to pull from the same thread pool/execute queue
as the requests for URLs in the WAR. Also I want the MDB threads to run at a much
lower priority and always give preference to interactive requests.
So interactive threads will always win and grab the processors if interactive use
is high, but if it's not, the MDBs can run instead.
Regs,
Paul

Hi,
I had a chat with BEA support about my issue. You can create multiple ExecuteQueues
and assign them to servlet definitions in WARs in the web.xml, and with an option
to the EJBC compiler, you can assign a particular class of EJB to an ExecuteQeueue.
For details see http://e-docs.bea.com/wls/docs61/perform/AppTuning.html#1106284
Presumably it's the thread of the initial request that counts, i.e. if a WAR calls
an EJB, then it's the thread in the execute queue of the WAR that will be used right
the way through the request, not that of the EJB being called, assuming they are
both deployed in the same WebLogic instance. If they were in different instances,
you would obviously have a thread from the WAR queue on one instance, and a thread
from the EJB queue on another instance.
If a plain Java command-line client connected directly to an EJB, then it would be
the thread from the ExecuteQueue of the EJB that would get used.
I've been told that MDBs always run in the default queue, so it seems that the way
for me to do what I want is just to create an ExecuteQueue, set the priority of the
threads in this queue to be higher than that of the default queue, and assign this
queue to my WARs. I can leave my EJBs running in the default queue.
Regs,
Paul
"Dimitri I. Rakitine" <[email protected]> wrote:
Don't know about 6.1 (One can find out very easily what the possible config
parameters
are by deploting
http://dima.dhs.org/misc/listMBeans.jsp and
http://dima.dhs.org/misc/showMBean.jsp
abd looking at the XXXConfig mbeans), but in 7.0 there are quite a few
things which
can be tuned in the executequeue config (and priority is one of them. also
interesting
is that it is possible to configure it to increase number of execute threads
when queue
length exceeds some specified threshold) :
QueueLength
Returns the maximum length of this queue.
ThreadPriority
Returns the priority of the threads associated with this queue.
ThreadCount
Returns the number of threads assigned to this queue.
QueueLengthThresholdPercent
Returns the threshold percent for length of this queue, set in QueueLength.
ThreadsIncrease
Returns the number of threads to grow when a queue is within QueueLengthThresholdPercent
of the set QueueLength.
ThreadsMaximum
Returns the maximum number of threads in the pool.
ThreadsMinimum
Returns the minimum number of threads in the pool.
Dimitri

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

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

Thread pools for execute queues

We've set up thread pools for several execute queues dedicated to high-load servlets
in our application. Once in a while, we get into a condition in which none of
these threads are available and then the threads never become available - we have
to restart the server.
I realize that this is a pretty generic description of the problem :-) but I wonder
if anyone else has encountered this and has an idea what might be causing it ?
Right now I am guessing that something in our code causes a resource contention
that eventually deadlocks all the threads. But that is just a guess.

Ethan,
"Ethan Allen" <[email protected]> wrote in message
news:3e0220a1$[email protected]..
Thanks, Dimitri and Slava !
I will do this and learn a little emore ...FYI, there is a web site dedicated to weblogic documentation -
http://e-docs.bea.com/
Pick your server version, go to "Search", type "thread dump".
Regards,
Slava Imeshev
>
ethan
"Slava Imeshev" <[email protected]> wrote:
Hi Ethan,
For windows press <Ctrl>+<Break> in the server shell window,
for *nix send kill -3 {server PID}.
Regards,
Slava Imeshev
"Ethan Allen" <[email protected]> wrote in message
news:3e020fb4$[email protected]..
Thanks for your reply, Dimitri.
We have not looked at thread dumps. How may we do this ?
Ethan
"Dimitri I. Rakitine" <[email protected]> wrote:
Did you try looking at thread dumps when this happens ?
Ethan Allen <[email protected]> wrote:
We've set up thread pools for several execute queues dedicated to
high-load
servlets
in our application. Once in a while, we get into a condition in
which
none of
these threads are available and then the threads never become
available
- we have
to restart the server.
I realize that this is a pretty generic description of the problem:-) but I wonder
if anyone else has encountered this and has an idea what might be
causing
it ?
Right now I am guessing that something in our code causes a
resource
contention
that eventually deadlocks all the threads. But that is just a
guess.
>>>>
Dimitri

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 to find the Current threads idle in each execute queue

Hi,
Currently I am able to get the idle threads in the default queue.
I would like to find out if it is possible to find out the no of threads
that are idle in each of the execute queues in the wls server.
Thanks
Senthil

Senthil Kumar wrote:
Hi,
Currently I am able to get the idle threads in the default queue.
I would like to find out if it is possible to find out the no of threads
that are idle in each of the execute queues in the wls server.
Thanks
Senthil
Senthil, the easiest way from the command-line is by using a
ExecuteQueueRutime MBean. You could use the simple syntax below or use
the more specific domain oject name. You could also omit the -property
option and get a list of every attribute for the bean.
%java weblogic.Admin -url t3://127.0.0.1:7001 -username system -password
weblogic -get -pretty -type ExecuteQueueRuntime -property
ExecuteThreadCurrentIdleCount
HTH
~Ryan

Can I get the thread count back in ios7

After upgrading to ios7, I realized that when inside my inbox the total of unread emails is no longer at the top of the screen. Also in my threaded email conversations, it does not give me the number of emails in the thread, which it did prior to ios7. Is there a way to get this back or has it been removed. This is an aweful change, Why would apple get rid of the thread count.

No, the Disk Usage and Memory Usage pie charts are gone. Also gone is the Memory Usage Dock icon. (New graphs are much more useful, imo.)

Any way to create Execute Queues or set Load Order using ANT?

Hello All,
Does anyone know whether wlconfig or some other Ant tasks can be used
in order to automate the creation of specific Execute Queues? We'd like
to script and package this so as to avoid having the user configure
queues through the admin console.
I'd also like to find out if there is some way to set the application
Load Order through wlconfig or wldeploy.
I have looked at the WebLogic command reference here: http://e-
docs.bea.com/wls/docs81/admin_ref/ant_tasks.html but don't see anything
promising.
Am I missing something? I'm not too familiar with all the scripting
possibilities so any help would be much appreciated. We are using
WebLogic Server 8.1 SP3 on Windows and UNIX.
Thanks

Thanks Anilkumar, but I was trying to figure out how to create these using
Ant scripts and NOT the admin console which is what your link seems to be
pointing to.
<akari> wrote in message news:[email protected]..
Hi,
go through the following link,In that you will find information about how
to create execute Queues.
http://e-docs.bea.com/wls/docs81/perform/AppTuning.html#1105201
-----Anilkumar kari

Thread Count Queue Length in Negative and Too many standby Thread

We are using Weblogic server 9.2.2 with 1 admin server and 4 managed server . Currently in one of the servers I could observe that there are around 77 standby threads.
Home > Summary of Servers > server1 > Monitoring > Threads > Self-Tuning Thread Pool
I could see that the "queue length" is negative (-138) and self tuning standby thread count is 77. Large number of threads STANDBY thread persists during the busy time of the business hours where as other servers are fully utilized.
Is it normal to have negative queue length and so many STANDBY threads? As for JMS queue negative oracle had already acknowledged that it is a bug. Thanks.
Edited by: 855849 on May 1, 2011 7:19 AM
Edited by: SilverHawk on May 12, 2011 8:12 AM

Yesterday an Oracle Consultant acknowlegded that it is a bug. There was a patch issued for Negative count in the JMS queue count and now this. Thanks for the reply by the way.

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.

Execute queue thread count set back?

Similar Messages

Maybe you are looking for