SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 55904: You cannot access any SAS® 9.4 web applications when the secondary middle-tier node is in a clustered environment

DetailsAboutRate It

When you start the SAS 9.4 secondary node for the middle-tier node in a clustered environment, you cannot load any SAS 9.4 web applications after you enter your user ID and password. When this problem occurs, the Microsoft Internet Explorer browser runs in a continuous loop, and the following errors appear in the SAS Web Server log file:

[Thu May 28 16:15:56 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:00 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:00 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:04 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:04 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:08 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:08 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:09 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:09 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:12 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:12 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:16:16 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:8080 (xxx.xxx.com) failed
[Thu May 28 16:16:16 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:18:15 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:18:15 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:18:53 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:18:53 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:19:06 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:19:06 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:19:12 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:19:12 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:20:12 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:20:12 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:21:12 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:21:12 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)
[Thu May 28 16:22:12 2015] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 10.53.222.108:9180 (xxx.xxx.com) failed
[Thu May 28 16:22:12 2015] [error] ap_proxy_connect_backend disabling worker for (xxx.xxx.com)

However, you can access the SAS 9.4 web applications when only the primary node in the middle tier runs in a clustered environment.

To solve this problem, follow these steps:

  1. Add the following Java virtual machine (JVM) argument to the JAVA_ARGS option on your middle-tier machine:
    -Dgemfire.conserve-sockets=false
    • For UNIX operating environments, add the argument to the section that is labeled # Java Additional Parameter in the gemfire-start-locator-sas.sh script file, which resides in the SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/ directory.
    • For Microsoft Windows environments, add the argument to the section that is labeled # Java Additional Parameter in the wrapper.conf file, which resides in the SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/ directory.
  2. Add the same argument (-Dgemfire.conserve-sockets=false) JVM_OPTS arguments for all instances of the SAS 9.4 Web Application Server (for example, SASServer1_x, SASServer2_x, and so on).
    • Under UNIX, add the argument to the section that is labeled # Java Additional Parameter in the setenv.sh script file, which resides in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_x/bin/ directory.
    • Under Windows, add the argument the section that is labeled # Java Additional Parameter in the wrapper.conf file, which resides in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_x/conf/ directory.
  3. Restart the SAS 9.4 middle-tier services in the clustered environment.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Cache LocatorSolaris for x649.49.4 TS1M2
Linux for x649.49.4 TS1M2
Microsoft® Windows® for x649.49.4 TS1M2
64-bit Enabled AIX9.49.4 TS1M2
* 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.