When JBoss tries to initialize the Java Messaging Service (JMS), the following errors are shown in the application server log:
[ServerService Thread Pool -- 68] INFO com.appiancorp.common.initialize.PingJMS - Sending ping to JMS from <machine_name>/X.X.X.X [ServerService Thread Pool -- 68] ERROR com.appiancorp.common.initialize.PingJMS - Could not send ping to JMS: javax.jms.JMSSecurityException: HQ119032: User: null doesn't have permission=SEND on address {2} ... [ServerService Thread Pool -- 68] ERROR com.appiancorp.core.persist.JmsCacheUpdateDistributor - Could not propagate: [DistributedCacheUpdate cacheName="administeredConfiguration" keys=[appian.feature.engineering.enableSysAppsEditing]]
Users in the JBoss security realm have not been correctly defined in application-roles.properties, located in <JBOSS_HOME>/standalone/configuration.
<JBOSS_HOME>/standalone/configuration
Perform the following to fix this issue:
guest=guest
This article applies to Appian 16.3 and earlier using JBoss EAP as an application server.
Last Reviewed: February 2017