topic Re: SAS application loading issue in Administration and Deployment

SAS application loading issue

Paul30 — Thu, 06 Feb 2020 12:03:30 GMT

Hi,
When we login into application page is keep on in loading state for more time in IE11. We are using Linux 7.7, java 1.7 and tomcat application server. After clearing cache and closing browser, sometimes application is getting logged in. Sometimes it is in loading state and sometimes it even does not load and stuck in white screen. Sometimes at the time of loading page, we get recover page option to select. After doing recover page, it works sometime or it may not. Could any one please provide solution.

Re: SAS application loading issue

AnandVyas — Fri, 07 Feb 2020 03:59:09 GMT

Hi Paul,

Have you tried any other browser to open the application? This could also due to network issue. Have you tried to connect to LAN and hitting the same issue?

Re: SAS application loading issue

Paul30 — Fri, 07 Feb 2020 13:22:33 GMT

Hi Anand,

Thank you for your response...

We have tried with Google Chrome also the same issue persist. Other applications are running fine in same LAN. We are hitting the URL connecting to LAN.

Re: SAS application loading issue

AnandVyas — Fri, 07 Feb 2020 14:29:24 GMT

You should enable trace logging for the web application and also object spawner and then try to replicate the issue. Since you have mentioned in the initial post that sometimes you are able to login, I believe it could be something due to network or firewall causing intermittent issues. Trace logs would help to gather more detailed messages to debug.

Re: SAS application loading issue

Paul30 — Wed, 12 Feb 2020 10:24:33 GMT

We have enabled trace log. In almost all logs a WARN message is getting printed " com.sas.services.session.SessionContext - Forced destruction of the session context by the session service. Session Context=fbbd73*******:*****:******:-3eb9. Request to please guide.

Re: SAS application loading issue

AnandVyas — Mon, 17 Feb 2020 13:31:52 GMT

Hi Paul,

I believe this issue requires analyzing various SAS logs and may also involve some troubleshooting with network team.

I would suggest you to raise a SAS Support track by emailing the error and trace enabled logs to support@sas.com for faster resolution.