If the bind address chosen by JGroups software for SAS Remote Services does not match the bind address chosen by JGroups in the Web application server for the SAS middle-tier applications, the communication protocol used by JGroups might not function correctly. As a result, the following errors might appear in the Web application server's log:

ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean
definition with name 'dashboardServices' defined in ServletContext resource
[/WEB-INF/spring-config/services-config.xml]: Could not resolve 
placeholder 'metadata.user'


ERROR [main] – ****************************************************************
ERROR [main] – Required entry, '/sas/properties/environment', not found in the cache.
ERROR [main] – Possible causes include: the RemoteServices VM is not started or
ERROR [main] – there is a multicast address/port mismatch; using 
ERROR [main] – address=239.168.68.1 and port=8561.
ERROR [main] – ****************************************************************

This issue can be caused by the following factors:

• Your system has multiple network interface cards (including virtual cards).
• You are logged on to a Virtual Private Network (VPN).

To resolve this problem, you must set the following Java Virtual Machine (JVM) option to ensure that the Web application server and SAS Remote Services use the same bind address:

The following sections explain how to set this option on the Red Hat JBoss application server and in the SAS Remote Services application.

Note: In the steps that follow, <ip-address> should be replaced with an actual IP address, as shown in these examples:

• −Djgroups.bind_addr=10.10.10.1
• −Djgroups.bind_addr=localhost
• −Djgroups.bind_addr=127.0.0.1

Setting the JVM Option on the JBoss Application Server

If JBoss is starting from the SASServer1 script file, perform the following steps:

1. Open the SASServer1.bat(.sh) file in the following directory:
2. Edit the JAVA_OPTS variable to include the following option:

If JBoss is starting as a Windows service, perform the following steps:

In this property, the value that is specified for nn is the next sequential number.

1. Open the wrapper.conf file that is located in the following JBoss directory:
2. Add an additional Java property to this file that is similar to the following example:

Setting the JVM Option in SAS Remote Services

If SAS Remote Services is starting as a Windows service, perform the following steps:

1. Open the wrapper.conf file that is located in the following configuration directory:
2. Add an additional Java property to this file that is similar to the following example:
   wrapper.java.additional.nn=−Djgroups.bind_addr=ip-address

   In this property, the value that is specified for nn is the next sequential number.

If SAS Remote Services is starting from the RemoteServices script file, perform the following steps:

1. Open the RemoteServices.bat(.sh) that is located in the following directory:
2. Add the following option to the :start2 section:
   −Djgroups.bind_addr=ip-address

   Note: On Unix operating systems, this option must be added after the nohup command in start2.

Also see SAS Note 40481 for more information regarding SAS BI Report Services and the jgroups.bind_addr property.

You also need to make the same changes to the SAS Analytic Platform’s wrapper and script files as well, if they are installed.

Operating System and Release Information