Worst of all, Oracle refuses to propagate patches backwards, so if you are running even a mildly old (like a year) JDK, you will suffer for it. Enterprise Java doesn't move that fast, so you end up having bootclass hacks to get around these shortcomings.
And oh yeah, if you also support Android, you might as well hire someone full time to deal with this, since it is that time consuming to deal with.
It's not a fair comparison: Go has a TLS stack that is shepherded by Adam Langley, who is one of the Internet's foremost experts on TLS.
Here are a couple of examples of what I mean. [2] cites use of Go in financial apps without a single mention of security.
[1] http://thenewstack.io/a-closer-look-at-golang-from-an-archit...
[2] http://www.techworld.com/apps/why-googles-go-programming-lan...
But maybe I'm missing your point.
Ironically just before reading this article I was reviewing a Java code change to force TLS 1.1+. The logic to set security protocols and ciphers correctly is quite tangled in part because it's not consistent across different libraries e.g., for JMX and SSL sockets. I still can't tell if the code I was reviewing will work in production.
Has anyone posted a general comparison of Java vs. Go on security? This deserves a closer look.