This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-16
Channels
- # announcements (22)
- # beginners (4)
- # biff (4)
- # cider (5)
- # clerk (3)
- # clojure (28)
- # clojure-chennai (1)
- # clojure-europe (23)
- # clojure-gamedev (7)
- # clojure-korea (5)
- # clojure-madison (3)
- # clojure-my (1)
- # clojure-nl (1)
- # clojure-norway (49)
- # clojure-sweden (7)
- # clojure-uk (4)
- # clojuredesign-podcast (14)
- # clojurescript (10)
- # clr (5)
- # cursive (4)
- # datascript (17)
- # datomic (2)
- # events (1)
- # garden (1)
- # introduce-yourself (2)
- # jobs-discuss (14)
- # lsp (23)
- # malli (14)
- # missionary (9)
- # off-topic (109)
- # overtone (7)
- # polylith (5)
- # releases (5)
- # shadow-cljs (7)
- # sql (13)
- # testing (30)
- # xtdb (10)
- # yamlscript (44)
we recently started getting the following error a few times a day from our Datomic cloud environment:
{:status 0, :headers {}, :cognitect.anomalies/category :cognitect.anomalies/fault, :cognitect.anomalies/message "Abruptly closed by peer", :cognitect.http-client/throwable #error {
:cause "Abruptly closed by peer"
:via
[{:type javax.net.ssl.SSLHandshakeException
...
I can file a support ticket for support from the datomic team, but wanted to see if anyone has ran into this before and has any suggestions?
The only large change we've made recently is migrated some of our webservers that connect to datomic into a private subnets connected to the internet via a NATGateway, rather than sitting in public ones, but not sure if the timing lines up, and its very intermittent / spurious
We're 1067-9276