I see so many threads stucking at
“flowable-task-Executor-8757” #113541 prio=5 os_prio=0 tid=0x000000002e03e800 nid=0x3330 runnable [0x0000000068e3e000]
at java.net.SocketInputStream.socketRead0(Native Method)
I am doing some rest calls in my custom servicetasks but although I set socketTimeout this socketTimeout is not working in some cases that i can not reproduce and the thread keeps stucking there. There seems to be a bug on jdk related to socketRead on windows environments. This is a out of flowable-context problem.
What really a flowable-context problem is; I expect these hanging threads to kill themselves after a certain period of time becasuse as long as these stucked thread count increases, at one point there remains no availavle async threads to execute my upcoming tasks.
Is there such a property to set timeout for these situations, if there is not, how can i implement my own solution for this kind of problems?
Is this property something related to my problem?
* The time (in milliseconds) a thread used for job execution must be kept
* alive before it is destroyed. Default setting is 0. Having a non-default
* setting of 0 takes resources, but in the case of many job executions it
* avoids creating new threads all the time.
protected long keepAliveTime = 5000L;