HornetQ warning messages appear in the application server log after JBoss starts up:
WARN [org.hornetq.core.client] (Thread-4 (HornetQ-client-global-threads-1399271844) HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED]
WARN [org.hornetq.core.server] (Threas-18 (HornetQ-server-HornetQServerImpl::serverUUID=ae275a93-b6c3-11e4-b13d-b98754463762-493636167)) HQ22 138: Local Member is not set at on ClusterConnection
This is seen as a warning message just after the "services are lazy, passive, or on-demand" line.
The <cluster-user> child element under the <hornetq-server> element in standalone.xml has a custom username and password which was not defined in application-roles.properties.
For more information, search for JMS Clustering in the Appian documentation.
Add the custom username and password (defined in standalone.xml) to application-roles.properties file located in the <JBOSS_HOME>/standalone/configuration directory.
This article applies to Appian 16.3 and earlier with JBoss EAP 6.4.x as an application server.
Last Reviewed: July 2017
© 2022 Appian. All rights reserved.