KB-1012 "HQ119015: The connection was disconnected because of server shutdown" error after JBoss startup

Parmida Borhani — Mon, 30 Jul 2018 04:13:42 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 4:13:42 AM

Symptoms

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.

Cause

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.

Action

Add the custom username and password (defined in standalone.xml) to application-roles.properties file located in the <JBOSS_HOME>/standalone/configuration directory.

Affected Versions

This article applies to Appian 16.3 and earlier with JBoss EAP 6.4.x as an application server.

Last Reviewed: July 2017

Tags: installation, application server, infrastructure, jboss

KB-1012 "HQ119015: The connection was disconnected because of server shutdown" error after JBoss startup

Nick Vigilante — Tue, 25 Jul 2017 10:28:38 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 7/25/2017 10:28:38 AM

Symptoms

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.

Cause

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.

Action

Add the custom username and password (defined in standalone.xml) to application-roles.properties file located in the <JBOSS_HOME>/standalone/configuration directory.

Affected Versions

This article applies to Appian 16.3 and earlier with JBoss EAP 6.4.x as an application server.

Last Reviewed: July 2017

Tags: application server, jboss

KB-1012 "HQ119015: The connection was disconnected because of server shutdown" error after JBoss startup

Nick Vigilante — Fri, 10 Feb 2017 15:44:24 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/10/2017 3:44:24 PM

Symptoms

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.

Cause

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.

Action

Add the custom username and password (defined in standalone.xml) to application-roles.properties file located in the <JBOSS_HOME>/standalone/configuration directory.

Affected Versions

This article applies to Appian 16.3 and earlier with JBoss EAP as an application server.

Last Reviewed: February

Tags: application server, jboss