How can I stop Java updates from breaking a legacy app?

November 18, 2026 4 answers
Asked by Ravtani.6z

We have an old application that repeatedly breaks after Java updates. Reinstalling the older Java version fixes it for a while, but attempts to disable updates have not stuck. What should we investigate for a more stable fix?

Answers

4j~bravixo_681

Start by finding out exactly which Java installation the app launches and what changes after an update. Compare the working and broken versions, then check the application and Java logs for the actual error.

If the failure is during a TLS connection, changes to disabled algorithms in java.security are one possible cause. Check the protocol and algorithm in use, along with any applicable security requirements. Don't loosen that setting blindly just to get the app running.

Reply to this answer
_4p+zunvexa.5

As a temporary containment measure, you could ask the network team to block the updater's outbound traffic for the affected host. First confirm which process and destinations are actually doing the updating. A host firewall may be more useful for devices that leave the network.

Document the rule and how to reverse it. Blocking updates leaves that Java installation exposed to known vulnerabilities, so get security approval and restrict the affected system's access where practical.

Ravtani.6z:

That gives us something specific to take to the network team. We'll need to confirm where the updates are coming from first.

Reply to this answer
7m+corvani_495

Check whether the application can be configured to use a dedicated Java installation rather than whichever version is installed system-wide. If it can, test that setup in a sandbox and make the chosen runtime part of the deployment configuration. That could avoid other Java updates changing what the app runs with, though the dedicated runtime still needs a security and maintenance plan.

Reply to this answer
_m76~zernivo.3

Track the ticket volume and the time spent reinstalling Java, then put that alongside the risk of running an old runtime. That gives the decision maker something concrete to use when prioritizing a vendor fix or replacement. Either may take time, so a documented temporary workaround is still worth pursuing.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions