Unable to allocate a new thread in the time specified

, ,
1

Hi All,

Our IS logs are flooded with the below error.how can it be stopped?.

errorlog:
9119] Unable to allocate a new thread in the time specified

com.wm.app.b2b.server.ISRuntimeException: [9119] Unable to allocate a new thread in the time specified
at com.wm.app.b2b.server.ThreadManagerImpl.runTarget(ThreadManagerImpl.java:152)
at com.wm.app.b2b.server.ThreadManagerImpl.runTarget(ThreadManagerImpl.java:126)
at com.wm.app.b2b.server.ThreadManager.runTarget(ThreadManager.java:83)
at com.wm.app.b2b.server.scheduler.ScheduleDB.runNextTask(ScheduleDB.java:1482)
at com.wm.app.b2b.server.scheduler.ScheduleManager.run(ScheduleManager.java:133)
at com.wm.util.pool.PooledThread.run(PooledThread.java:131)
at java.lang.Thread.run(Unknown Source)

server log:
[2050]2014-07-10 07:38:39 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 0% available
[2049]2014-07-10 07:38:37 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 13% available
[2048]2014-07-10 07:38:35 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 10% available
[2047]2014-07-10 07:38:33 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 12% available
[2046]2014-07-10 07:38:31 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 13% available
[2045]2014-07-10 07:38:29 BST [ISS.0014.0020I] Available Thread Pool Warning Threshold Exceeded: 0% available
[2044]2014-07-10 07:38:29 BST [ISS.0137.0010E] Scheduler: Resources unavailable: [9119] Unable to allocate a new thread in the time specified

Thanks,
Shiva

2

Options would be:

You should raise the IS Settings–>Resources–> Server Thread Pool–> max threads (increase this) --I believe your system is running heaving volumes and schedulers hung state situations.

Restart the IS (even after the above settings not rectified and schedulers page Next Run shows (0.0) etc…

HTH,
RMG

3

Increase your server thread pool and that should fix the issue.

Are you facing this issue on PROD servers?