Hi

I have an issue where my applicaion servers have recently started failing
with OOM - cannot create native thread errors. However the dump files all
show he majority of threads (over 90%) like the following:

"pool-21088-thread-1" - Thread t@36407
>
>    java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <2bc1d4f0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1079)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
>    Locked ownable synchronizers:
> - None
>
>
>
My first assumption is that these are for a connection pool, however I am
seeing close to 1000 (one thousand) and these never appear to timeout, or
close.


I could of course increase the number of threads the OS allows, but this of
course has memory implications etc and is not really solving the root cause.

Can anyone identify what these are? I see some posts online indicating
these are the connection pool waiting for new requests. But this doesnt
seem to match my configuation for acceptable connections

Any help would be greatly appreciated

Thanks

*Mitchell *

Cable & Wireless Communications Plc is a company registered in England & Wales 
with number:
07130199 and offices located at 3rd Floor, 26 Red Lion Square, London WC1R 4HQ

Reply via email to