On Sat, May 21, 2016 at 8:44 PM, Maciej Filocha <[email protected]>
wrote:
> 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)
>
Ok, this may suggest the ControlFlowCallback never received the finished
event for some requests, and thus
it did not return their tokens: the system is based on a finite number of
tokens in a pool, each request starting
grabs one, each one finishing returns one back, requests not finding a free
token wait.
If the end of request message never reaches the callback, we lose tokens
and as a result the pool depletes.
Do you have stack traces in the logs or otherwise any indication as to what
might have gone wrong there?
Wondering in particular if any tiling request failed, those are the
nastiest ones to handle because if they don't
find a tile they circle back and issue another fake request back to
geoserver wms, that's the most problematic
bit to handle, the most likely to cause a misbehavior. We already have
machinery to handle the double request
without getting into a deadlock, but I'm wondering if maybe something is
happening if a tile build fails.
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
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