Usage Note 57507: Submitting the sas.servers command indicates incorrectly that the SASĀ® 9.4 JMS broker is not running
After you apply Hot Fix W43001 and you complete the post-installation steps, an issue occurs in the sas.servers.mid script. When you execute the command ./sas.servers status command, the results show that the SAS 9.4 Java Message Service broker (activemq) is not running when, in fact, it is. You can verify the actual status of the activemq by submitting the command ./activemq status.
This issue does not impact the running of SAS web applications, and it occurs only in Linux and UNIX operating environments.
To work around this issue, perform the following steps:
- Make a backup copy of SAS-configuration-directory/ev1/sas.servers.mid.
- Locate the following line (two occurrences of this line) in the sas.servers.mid script file:
PIDFILE="$ACTIVEMQ_DIR/data/activemq-${SHOSTNAMEUNX}.pid"
- Change those two lines to the following:
PIDFILE="$ACTIVEMQ_DIR/data/activemq.pid"
Operating System and Release Information
SAS System | SAS JMS Broker | Solaris for x64 | 9.4 | | 9.4 TS1M3 | |
Linux for x64 | 9.4 | | 9.4 TS1M3 | |
HP-UX IPF | 9.4 | | 9.4 TS1M3 | |
64-bit Enabled Solaris | 9.4 | | 9.4 TS1M3 | |
64-bit Enabled AIX | 9.4 | | 9.4 TS1M3 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
After you apply Hot Fix W43001 and you submit the ./sas.servers status script, the results indicate, incorrectly, that the SAS 9.4 Java Message Services broker is not running when, in fact, it is running. This issue does not impact the ability to run SAS web applications.
Date Modified: | 2016-01-25 13:44:46 |
Date Created: | 2016-01-25 10:14:44 |