jboss.qualified.host.name is no longer the FQDN after updating to OpenJDK 1.8.0u462+

Solution Verified - Updated -

Issue

  • We recently updated the OpenJDK to 1.8.0u462+. And after this, we see the jboss.qualified.host.name has changed from the FQDN to just the short hostname.
  • This causes issues as the messaging http-connector now uses the short hostname and our clients to resolve and connect with just the short hostname now instead of the FQDN used previously:
20.07.2025 03:23:37,922 WARN  [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 90) AMQ122005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "shorthostname". If this new address is incorrect please manually configure the connector to use the proper one.

The application worked fine before the update. After the update the client can not connect to the server and throws the following exception:
2025-07-22T11:00:52,867|ERROR|AWT-EventQueue-0|artemis.core.client||AMQ214016: Failed to create netty connection|||
java.net.UnknownHostException: shorthostname

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x
  • Red Hat OpenJDK 1.8.0u462+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content