2022-08-03 duct | Clojure Slack Archive

duct 2022-08-03

erwinrooijakkers 2022-08-03T08:59:06.684249Z

Hi all, we noticed that our application does not restart when there’s an exception in HikariCP (it cannot connect) on startup

erwinrooijakkers 2022-08-03T08:59:24.728209Z

We use startup code similar to

(defn -main [& args]
  (let [keys     (or (duct/parse-keys args) [:duct/daemon])
        profiles [:duct.profile/prod]
        config (-> (duct/resource "simple/config.edn")
                   (duct/read-config)
                   (duct/prep-config profiles))
        system (ig/init config keys)]
    (reset! stored-config config)
    (reset! stored-system system)
    (duct/await-daemons system)))

(I still work at that company ;))

😬 1

erwinrooijakkers 2022-08-03T09:00:29.141729Z

HikariPool-1 - Exception during pool initialization

erwinrooijakkers 2022-08-03T09:00:42.081609Z

We want to restart the application when that happens, how can that be accomplished?

ts1503 2022-08-04T07:53:29.691479Z

I see in your message HikariPool-1 it seems like exception was in thread 1. I’m not an expert but assume that hikary launching separate threads and not joining them to the main application thread. So if one thread dies others will still continue to work

erwinrooijakkers 2022-08-04T07:53:48.190879Z

aha

ts1503 2022-08-04T07:53:56.316829Z

so this exception doesn’t happening during Duct initialization

erwinrooijakkers 2022-08-04T07:54:26.524719Z

so maybe an exception on a separate thread that only crashes the thread

ts1503 2022-08-04T07:54:41.947149Z

yes

erwinrooijakkers 2022-08-04T07:54:42.415389Z

but fact of the matter is there’s no database connection after the exception, it does not retry

erwinrooijakkers 2022-08-04T07:55:05.145359Z

but not a duct issue then, but hikari