SAS Web application issue

[sathya66]

Hi All,

When I am restaring SAS Web apps , I am getting below warnings in SASServer1_1. can you suggest.

10:19:17,485 | INFO | [HostConfig] | Deployment of deployment descriptor [config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASTemplateEditor.xml] has finished in [23,286] ms
10:19:17,486 | INFO | [HostConfig] | Deploying deployment descriptor [config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASDeploymentBackup.xml]
10:19:17,488 | WARN | [HostConfig] | The path attribute with value [/SASDeploymentBackup] in deployment descriptor [config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASDeploymentBackup.xml] has been ignored

and also , I am getting below timing out issue when I try to logon to SASStudio

org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://sasmid.com/SASLogon/v1/tickets": Connection timed out (Connection timed out); nested exception is java.net.ConnectException: Connection timed out (Connection timed out)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:534)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:482)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:430)
at com.sas.svcs.security.authentication.client.AuthenticationClient.doLogon(AuthenticationClient.java:162)
at com.sas.svcs.security.authentication.client.AuthenticationClient.logon(AuthenticationClient.java:150)
at com.sas.svcs.security.authentication.client.AuthenticationClient.logon(AuthenticationClient.java:230)
at com.sas.svcs.security.authentication.client.AuthenticationClient.logon(AuthenticationClient.java:122)
at com.sas.svcs.security.authentication.web.providers.UsernamePasswordCasAuthenticationProvider.getAuthenticationClient(UsernamePasswordCasAuthenticationProvider.java:22)
at com.sas.svcs.security.authentication.web.providers.AbstractAuthenticationClientProvider.authenticate(AbstractAuthenticationClientProvider.java:247)
at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
at com.sas.svcs.authentication.helper.SpringSecurityContextFactory.newAuthenticatedSecurityContext(SpringSecurityContextFactory.java:363)
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContextWithAuthManager(LazySpringSecurityContext.java:181)
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContext(LazySpringSecurityContext.java:234)
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getAuthentication(LazySpringSecurityContext.java:245)
at com.sas.svcs.security.aop.RunAsInterceptor.invoke(RunAsInterceptor.java:84)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy1870.folderExists(Unknown Source)
at com.sas.themedesigner.WIPThemeUIPComponent$UIPRunnable.isFlexThemeUpgradeInPlaceNeeded(WIPThemeUIPComponent.java:152)
at com.sas.themedesigner.WIPThemeUIPComponent$UIPRunnable.run(WIPThemeUIPComponent.java:122)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:681)
at sun.security.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:484)
at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:153)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:82)
at com.sas.svcs.remoting.client.SSLSocketFactory.createSocket(SSLSocketFactory.java:43)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:127)
at com.sas.svcs.remoting.client.SSLSocketFactory.createSocket(SSLSocketFactory.java:57)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.sas.svcs.remoting.client.CommonsClientHttpRequestFactory$CommonsClientHttpRequest.executeInternal(CommonsClientHttpRequestFactory.java:191)
at com.sas.svcs.remoting.client.CommonsClientHttpRequestFactory$CommonsClientHttpRequest.executeInternal(CommonsClientHttpRequestFactory.java:133)
at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:50)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:519)
... 27 more

[SASKiwi]

This type of problem is best progressed with SAS Tech Support if you haven't done so already. It looks like you have a software configuration problem.

[sathya66]

Thanks,
Yes, we are configuring our system for mid HA
https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/n14182gcigmyicn1huwlyl49s5fr.htm

Webserver:
https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/n0axzi2o0wubxan1cgaovjqqjfho.htm

step :

Install Additional Web Server Instances

2. Based on the network topology or protocol change, perform the tasks that apply from Manual Configuration Tasks.
https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/n1uh9f02c7lsnzn1cu57z20h95m8.htm

Configure the SAS Content Server to Use an Existing Customer Reverse Proxy

1. Changed the following JVM options to point to our proxy.

   -Dsas.scs.cas.scheme=https 
   -Dsas.scs.cas.host=sas.mid.com
   -Dsas.scs.cas.port=443
   -Dsas.scs.svc.scheme=https
   -Dsas.scs.svc.host=sas.mid.com
   -Dsas.scs.svc.port=443
   

2. Change the -Dsas.scs.svc.internal.url=http://host:port_number JVM option to point to the internal URI of the SAS Web Server. If the option does not exist, add it.

in the above second point  which hostname and port_number should I use? is it mid- server host and  what is the port_number?
we are planning  to cluster 3 mid-tiers .

I am working on 1st mid-tier  so in the host ,should I use 1st mid-tier host? and what is port_number? is it 443 or 8343?

do we need to change anything from our network side  or any other configs? 

we just setup load balancing proxy (sas.mid.com ) with listing port to 443 and talking with mid1, mid2 and mid3  to target port 8343 

[SASKiwi]

Sorry, I'm not familiar with your SAS architecture. You will get quicker answers from SAS Tech Support.