Well, this behavior is documented _somewhere_, but not in the doc string or on clojure.org that I know of (happy to be corrected if I'm wrong there).
On the ClojureDoc.org web site, the docs for pmap: http://clojuredocs.org/clojure.core/pmap suggest looking at the docs for future for info about a 1-minute wait and how to avoid it, where there are lots of details: http://clojuredocs.org/clojure.core/future Andy On Tue, Dec 19, 2017 at 1:15 PM, Mike <145...@gmail.com> wrote: > last line in -main should be (System/exit 0) or (shutdown-agents). > 1 min awaiting it is documented behaviour of clojure. > > вторник, 19 декабря 2017 г., 23:08:09 UTC+3 пользователь Justin Smith > написал: >> >> any Clojure program that uses the built in thread pools (future, agent, >> pmap, core.async, etc.) should call (shutdown-agents) if prompt exit is >> needed >> >> On Tue, Dec 19, 2017 at 12:05 PM Jacek Grzebyta <grzeby...@gmail.com> >> wrote: >> >>> Hi, >>> >>> I have multi -mains project. Thus the execution looks like: >>> >>> java -cp location/file.jar some.method ...... >>> >>> >>> One -main method looks like: >>> >>> (defn -main >>> [& args] >>> (let [validated (validate-args args)] >>> (if (:msg validated) >>> (println (st/join \newline (:msg validated))) >>> (run validated)) >>> (log/debug "finish"))) >>> >>> >>> There is nothing special in that except in the run time I have displayed >>> the last log "finish" and the program termination is done after ~1 min >>> later what is annoying. I found it is caused by deeply hidden pmap even if >>> it is wrapped by doall. I thought after pmap returns results all threads >>> are finished i.e. the main thread waits until all sub threads will be >>> finished. If I am right what else can cause the delay? The threads pool >>> manager? >>> >>> Tanks a lot, >>> Jacek >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@googlegroups.com >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+u...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+u...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
