Hello Holger/Gerardo,
As, of now I’m not making any changes on changing my JVM points to Oracle SDK.
Because, we’ve to demostrate to my client. If the server is not up after making the changes it would be a big headache for us.
I’ll probably make the changes once we’re done with the final demonstration is done.
Till then I’ll manage the server up when it’s not responding.
@Gerardo, The trigger queue capacity size is “100”.
As, I’m using UM as messaging component the refill size is left with default value 4 only. Because UM doesn’t process documents based on Refil level.
Also, I observed that none of the threads are not killing, even after I’ve disabled all the polling notifications & Schedulers since more than 30 hours.
The polling interval is 10 seconds we have given. As I mentioned in the previous messages below are my thread pool settings.
My current System Thread Pool settings were as follows:
Available Threads: 78 % (78 Threads)
Maximum Threads: 100 (I increased Max thread count to 100, default is 75)
Minimum Threads: 10
Available Threads Warning Threshold : 15 % (15 Threads)
Scheduler Thread Throttle : 100 % (100 Threads)
Scheduler Current Threads : 0
I didn’t receive any alerts regarding the available threads or memory.
As you said, I try Java Mission Control to know which service is causing to make the threads in TIMED_WAITING state.
Can anyone give me that java parameter -Xss configuration property. I’ll try add that in my custom_wrapper.conf for time being to see whether it’s control the stack size.
Thanks,
Pradeep.
#Integration-Server-and-ESB#webMethods-General#webMethods