mid-tier application not coming up

[woo]

Hello, we are running

Version - sas 9.3 m3

OS - Linux VM

where we really don't have much memory available (zero physical memory with 15 gb cached memory available). when we start web application, can login fine but nothing is coming up.

how do i overcome these errors?

server.log has this error 

ERROR (tomcat-http--2) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASModelRisk].[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at org.apache.jsp.layout.CompanyLogo_jsp._jspService(CompanyLogo_jsp.java:123)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:443)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:728)

and catalina.out has this error, 

[tomcat-http--2] ERROR com.sas.oprisk.monitor.web.ErrorServlet - An error occurred while handling another error.
org.apache.jasper.JasperException: javax.servlet.ServletException: javax.servlet.jsp.JspException: org.apache.jasper.JasperException: org.apache.jasper.JasperException: org.apache.jasper.JasperException: org.apache.jasper.JasperException: java.lang.NullPointerException
at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:565)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:466)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:728)

[JuanS_OCS]

Hello @woo,

Unfortunately this is not enough to get good conclussions, you would need to take additional actions or retrieve further information.

Anything  from the list below would help.

Personally, I would:

• Drop any non-required web applications from deploying (carefull with the WIP ones)
• Align with SAS Technical Support to fine tune the memory settings of your SAS and SAS/Web Java JVMs
• Monitor, if possible, those JVMs memory counters with JMX connection (jconsole, e.g) which will give you the scientifical reasoning to what is going on.
• Check other logs: RemoteServices, Web Applications (under SAS Config folder), your /etc/messages on Linux, etc
• Increase that physical RAM, where possible

Hope it helps. Please share any further information you manage to retrieve.

Best regards,

Juan

[SimonDawson]

SAS 9.3 is quite old. This likely means it was working for a long time. When did this stop working? When was it last working? What was changed in that period since the two startups?