KB-1133 Users not defined in application-roles.properties resulting in JMS-related errors in the application server log

Parmida Borhani — Mon, 30 Jul 2018 04:09:11 GMT

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

Symptoms

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]]

Cause

Users in the JBoss security realm have not been correctly defined in application-roles.properties, located in <JBOSS_HOME>/standalone/configuration.

Action

Perform the following to fix this issue:

Stop JBoss.
Open application-roles.properties, located in <JBOSS_HOME>/standalone/configuration.
If using default configurations, uncomment or add the following line if not already present in this file:
```
guest=guest
```
Save changes and start JBoss.

Affected Versions

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

Last Reviewed: February 2017

Tags: application server, infrastructure, jboss