This content has been marked as final. Show 1 reply
Yes wlss.timer work manager handles execution of all the timers (application or container/protocol level)
Similarly wlss.transport is workmanager for handling all the sip messages
Regarding WM's, it is more of core weblogic query. But IMO
Minimum Threads Constraint : Essentially means that at least that many threads will be working for the given WorkManager out of common pool of threads
Maximum Threads Constraint on workmanager essentially means at most that many threads will be working for the given WorkManager out of common pool of threads
IMO If no Minimum Threads Constraint is specified then still that WM will get threads as per need till pool has some idle threads and/or we are still below pool capacity where in new thread will be spawned.