This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-06
Channels
- # admin-announcements (1)
- # alda (2)
- # beginners (5)
- # boot (59)
- # clara (6)
- # cljs-dev (40)
- # cljsrn (32)
- # clojure (28)
- # clojure-austin (1)
- # clojure-belgium (67)
- # clojure-greece (60)
- # clojure-ireland (1)
- # clojure-japan (1)
- # clojure-russia (55)
- # clojure-spain (14)
- # clojure-spec (39)
- # clojure-uk (26)
- # clojurescript (152)
- # clojurewerkz (1)
- # cursive (21)
- # datomic (3)
- # dirac (15)
- # emacs (7)
- # events (2)
- # funcool (4)
- # hoplon (43)
- # immutant (1)
- # lambdaisland (1)
- # lein-figwheel (6)
- # leiningen (1)
- # off-topic (1)
- # om (23)
- # onyx (67)
- # other-languages (6)
- # pedestal (7)
- # planck (13)
- # proton (3)
- # protorepl (2)
- # re-frame (6)
- # reagent (5)
- # ring-swagger (6)
- # spacemacs (1)
- # specter (2)
- # yada (27)
Does anyone else get these kinds of warnings from tomcat when stopping a pedestal war?
06-Jun-2016 18:14:02.800 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [clojure.lang.Var$1] (value [clojure.lang.Var$1@1337b298]) and a value of type [clojure.lang.Var.Frame] (value [clojure.lang.Var$Frame@28c976d]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
I’ve been able to create a sample war that gives a related warning:
03-Jun-2016 15:04:12.628 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [sample] appears to have started a thread named [clojure.core.async.timers/timeout-daemon] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.DelayQueue.take(DelayQueue.java:211)
clojure.core.async.impl.timers$timeout_worker.invokeStatic(timers.clj:60)
clojure.core.async.impl.timers$timeout_worker.invoke(timers.clj:56)
clojure.lang.AFn.run(AFn.java:22)
java.lang.Thread.run(Thread.java:745)
But not the SEVERE warning
apologies if this is a simple question, but are there any helper functions for the following:
- enqueuing an interceptor as the next one in the chain (`io.pedestal.interceptor.chain/enqueue` adds it at the end)
- enqueuing an interceptor during the leave phase (i.e. pushing it on to the :io.pedestal.interceptor.chain/stack
)