SASServer1_1 on Lev2 might fail to start and return a "Failed to start component [Connector["http-nio-8082"]]" socket error


After you install the Q1 BigFix SECUPD17D hot fixes in an environment that contains two different configuration directories (Lev1 and Lev2), the SASServer1_1 service in Lev1 starts successfully, but the SASServer1_1 in Lev2 might fail to start. 

As a result, the following error occurs:

07:11:04,380 | INFO  | [HostConfig] | Deployment of web application directory {*}[<SAS_CONFIG>/Lev2/Web/WebAppServer/SASServer1_1/webapps/ROOT\\\\{*}] has finished in [3,439] ms
07:11:04,405 | ERROR | [LifecycleBase] | Failed to start component [Connector["\\\\{*}http-nio-8082{*}"]]
org.apache.catalina.LifecycleException: Protocol handler start failed
...
...
Caused by: java.net.BindException: The socket name is already in use

Workaround

Check whether the sas.webreportstudio.war file exists in both <SASConfig>/LevN directories. Then, change the ports as follows in the axis2.xml file:

Note: The axis2.xml file is located at <SASConfig>/LevN/WebAppServer/SASServer2_1/sas_webapps/sas.webreportstudio.war/WEB-INF/conf/.

Here is an example:

Lev1:

<transportReceiver name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer">

              <parameter name="port">8281</parameter>

              <parameter name="requestTimeout">3600000</parameter>

</transportReceiver>

<transportReceiver name="https" class="org.apache.axis2.transport.http.SimpleHTTPServer">

              <parameter name="port">8282</parameter>

              <parameter name="requestTimeout">3600000</parameter>

</transportReceiver>

Lev2:

<transportReceiver name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer">

              <parameter name="port">8283</parameter>

              <parameter name="requestTimeout">3600000</parameter>

</transportReceiver>

<transportReceiver name="https" class="org.apache.axis2.transport.http.SimpleHTTPServer">

              <parameter name="port">8284</parameter>

              <parameter name="requestTimeout">3600000</parameter>

</transportReceiver>