W dniu 21.05.2016 o 17:25, Andrea Aime pisze:
> If that's not your case, looking at a jstack output may help identify
> the issue.
> Normally this lockups are due to control-flow not receiving the notification
> that a request completed, or by requests not completing at all.
I have now:
INFO [geoserver.flow] - Running requests: 0, blocked requests: 23
and jstack gives me 52 threads with TIMED_WAITING state
with two kinds of stack:
"http-apr-8443-exec-21" #25008 daemon prio=5 os_prio=0
tid=0x00007f42d8021000 nid=0x655 waiting on condition [0x00007f423bffe000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000004c5330050> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:86)
at org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:32)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
or
"http-apr-8443-exec-12" #24999 daemon prio=5 os_prio=0
tid=0x00007f42d8016800 nid=0x64c waiting on condition [0x00007f423b4f1000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000004c1d9dac0> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.ArrayBlockingQueue.offer(ArrayBlockingQueue.java:379)
at
org.geoserver.flow.controller.SingleQueueFlowController.requestIncoming(SingleQueueFlowController.java:58)
at
org.geoserver.flow.ControlFlowCallback.operationDispatched(ControlFlowCallback.java:139)
at
org.geoserver.ows.Dispatcher.fireOperationDispatchedCallback(Dispatcher.java:800)
at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:795)
at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:265)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
...
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
