We found out that our docker build steps failed strangely in AWS for embarrasingl long time (work-around: build locally and push manually).The most likely cause was that
lein:2.8.1 docker-container updated itself to latest ubuntu and latest jdk:8, which is
1.8.1_181, which introduced a somewhat hard to understand regression regarding a
sun.security.ssl.SSLSessionImpl. This also showed itself up as some kind of concurrent IllegalStateException regarding threadpools. Locally an older version of the lein:2.8.1 container was cached.
Trés annoying, our workaround will likely be to redo the way we pack our system to uberjar into a plain openjdk container (with strict versioning). Should have been the case from start but well it usually works.
It was neither Datomic, any apache HTTP-related, IAM-related nor Jetty that caused this.
I guess this the new
javax.xml.bind.DatatypeConverter/printBase64Binary is upon us, you’re welcome.