Thread pool execute count
Using Thread pool execute thread count measure we plot a chart but after restart also I am getting some sount on chart for every JVM where as ideally it should be zero.
Please find the attachment for further information, We are having 4 JVM's and after restart also it is showing me some count for each JVM.
Best Regards,
Jaydatt.
Jaydatt,
I am not sure I fully understand your question, but try to answer it anyway:
The fact that the thread count is not zero after startup sounds normal to me. WebLogic most likely starts with a minimum number of threads in the pool. Only once you exceed those would it grow the pool until it reaches the configured maximum.
You might of course configure the pool to have a minimum size of 0, but that does not really have a benefit, and might lead to slower response times after the startup.
Idle Threads have very minimal overhead, a bit of memory (depending on your system anywhere between 256K to 1MB per thread) and if we are talking about windows a thread handle.
Best
Michael
I think you should not worry about this as what Michael said is very near to the situation what happens with any standard java container. Especially in weblogic those threads are default execute threads responsible for maintaining the processes of weblogic and other deployed application. If you take a thread dump after restart and then group them based on thread type you will see they will be mostly sleeping/waiting on something.
Generally these threads come from the default work manager of weblogic and are associated with the MDBs/EJBs deployed on weblogic.
Regards
Raman
thanks guys.
