This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-12
Channels
- # aleph (1)
- # announcements (13)
- # asami (4)
- # babashka (47)
- # beginners (22)
- # calva (11)
- # circleci (1)
- # clj-kondo (14)
- # clojure (43)
- # clojure-europe (43)
- # clojure-gamedev (1)
- # clojure-nl (1)
- # clojure-uk (6)
- # clojurescript (13)
- # core-async (5)
- # cursive (8)
- # datomic (20)
- # events (3)
- # fulcro (12)
- # graalvm (1)
- # graphql (4)
- # gratitude (3)
- # java (2)
- # juxt (2)
- # leiningen (12)
- # off-topic (30)
- # pathom (33)
- # pedestal (5)
- # podcasts-discuss (1)
- # polylith (14)
- # rdf (2)
- # re-frame (12)
- # reagent (3)
- # releases (2)
- # shadow-cljs (24)
- # spacemacs (13)
- # sql (2)
- # tools-build (16)
In lacinia-pedestal, the default timeout for the websocket server is 30s, however, there appears to also be a timeout in jetty used by pedestal of 30s. So in its default configuration its a bit race’y whether your websocket gets closed by jetty (if the subscription go loop is slightly too slow). Would it make sense to change the default / configure jetty to not have a timeout / …?
👀 1
It’s a bit unfortunate how it is now; using the default timeout causes you to get a websocket server that kills its client connection every few keep alives :’).