Register or Login to Your Account
We are getting the below error(stack trace) quite often from IS and service mails, could any one let us know how can we resolve these error permanently.
Cache Invalidation Thread started with sleep of 60000ms
2012-06-29 10:25:00 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue 'Security Queue' failed to log event to destination 'CoreAuditDBDest'; reason 'unable to create new native thread'; stack trace follows
2012-06-29 10:25:00 CEST [WmAuditingSC.destination.1122E] Destination 'CoreAuditDBDest' caught unexpected Throwable logging audit event: unable to create new native thread
[b]java.lang.OutOfMemoryError: unable to create new native thread[/b]
at java.lang.Thread.start0(Native Method)
at com.wm.dd.jdbc.oraclebase.BaseConnectionStartup.(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseConnection$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.wm.dd.jdbc.oraclebase.BaseConnection.setupImplConnection(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseConnection.open(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseDriver.connect(Unknown Source)
Solution is to restart the IS to release all the threads :) . Refer:
If we keep restarting IS whenever we get this error it will not resolve the issue permanantly. I want a permanent solution, let me know if you got any experience resolving these errors.
Available Thread Warning Threshold Exceeded
2003-04-25 14:22:20 PDT [ISS.0014.0020D] Available Thread Pool Warning Threshold Exceeded: 0% available
Based on the stack trace its clear that your IS was unable to create new native thread. Go to IS Admin page -> Resources -> Server thread pool, you can find your configuration for Available threads, maximum threads and minimum threads. Check how many running/available threads when this happens. if you still have free memory when it's happening, and you running out of thread, you can increase the max thread setting.
If you have set to maximum threads and you get these errors then you have to analyze your thread configurations, services and other IS resources and make sure IS will be not exceeding maximum configured threads.
Go to IS Admin console -> Messaging -> and checkout the maximum threads for your triggers for each of your application/Queue/message. Since these threads you configure here can in turn form child threads in multiples, so its bit risk involved if you are processing heavy volumes of feed. Analyze these properly and try to limit the count.