Make thread pools in DefaultDpwsModule more flexible
We noticed that at least @NetworkJobThreadPool
and @ResolverThreadPool
(cf. DefaultDpwsModule
) may become bottlenecks when connecting to multiple devices at once. These thread pools currently have a fixed size of 10. They are used for device connect
and resolve
operations (cf. ClientImpl
; @ResolverThreadPool
is used indirectly to resolve the HostingService during connect
).
We propose to make these "breathing" thread pools using CachedThreadPools
(=ThreadPoolExecutors
) with a configurable maximum limit of threads.
The other 2 thread pools in DefaultDpwsModule
seem to be less problematic.
Edited by Winfried Gerlach