Java is in a rather secure place right now. Everyone that chases the new shiny is long gone but it’s not yet at the point where it is difficult to hire for (e.g. COBOL).
So young buck comes to the CTO and says 'let's do a rewrite in Go' and the CTO says 'why in the world would I want to do that?' Then young buck says 'okay, what about just coding the new frobinator in Go?' CTO still says no, because then he’d have to hire Go programmers and Java programmers or at least waste time cross training. Young buck's less honest compadres have probably gone ahead and put Go into production here or there without permission, but I don’t think that’s a danger to Java.
What really changes this dynamic is when schools stop teaching Java.
Java is what you write in, if what you're selling isn't the code but some service that the code provides, and you aren't a startup, and you can afford a support team and want a lot of devs.
Go is what you write in when you're selling the thing you made directly, like say it's a DB engine, or you're a startup and want low effort support and only want a few devs.
Java makes maintaining a feature easy, and the programmers hired can be average and still be able to make something of acceptable quality, in an acceptable timeframe.
A startup rather wants to move fast. Java is harder to move fast at - but Go probably has that in spades. I do believe Go will not succeed in a large, beaurocratic place. And as a start up grow out to become more and more beaurocratic, the tech transitions with it.
Meanwhile there are lots of frameworks in the JVM world, some of them "heavy" with features, but if you want frameworks that are much smaller, github is overflowing with them.
Kotlin eliminates most of the boilerplate, leaving you with a slimline language, a powerful runtime and a wide choice of libraries. Go doesn't have much to compete with that.
+ or software engineering, etc.