As long as the current code works, you can add new features and fixes to it, there is no reason to change. For new projects you should use teh best tool for the job.
More seriously, I'm curious where you work or what parts of the industry you're privy to. It's everywhere from where I'm standing. Tons of companies are built on millions of jvms. LinkedIn, Google, Twitter, Amazon, etc. I know personally but I'm sure every third other tech company in the valley at least too.
[0]: https://rationalwiki.org/wiki/Fallacy_fallacy [1]: https://en.m.wikipedia.org/wiki/Argument_from_fallacy
Just to remind you, there was an entire industry built around Flash and Silverlight too. The people responding to me seem to think I'm advocating a quick rewrite (whatever that means), but all I'm saying is that from where I stand Java will not last in the long term without serious changes within Oracle. It would be better to have a transition plan now than no transition plan on a dying platform.
I was sort of expecting to be flamed, but I can assure you I'm not interested in revealing to flamers where I work...
Java is still free, so it can't be that.
What do you think will happen? Do you think that a sane boss will approve you wasting resources to port it to cool tech X instead of fixing the current needs. The only projects that have no choice and must do a porting are Flash based projects because soon will be probably impossible to get regular users to have Flash in a browser.
All I am saying is that good management is to look at the risks of sticking with Java and find a migration path earlier, because the longer you wait the more expensive it becomes to move away. And one day you will find you have no choice, and then it will be very expensive.
It is possible to maintain and even add essential features to a legacy system whilst migrating to a new system. Happens all the time.
First of all you have OpenJDK that is part of Debian, everyone knows that Debian is very strict about licensing so if it is part of Debian there will be nothing that will make Java retroactively unusable without a paid license.
I am not sure what your work experience is but I worked in small companies that use boring old tech, maybe it would be cool to use some cool language or cool framework but then you still get left behind when the language has a new incompatible version or the frameworks have a new version, the purpose is to keep the project working for the users, we not fix what is not broken.