BookmarkSubscribeRSS Feed
VatKS
Calcite | Level 5

A similar issue I see at but didn't find any solution, https://communities.sas.com/t5/Administration-and-Deployment/Web-server-don-t-start/td-p/807390
We are using SAS 9.4 M6

Webserver Catalina has these:

05:14:20,598 | WARN | [JmxSocketListener] | Detected LDAP configuration '/opt/sas/web/sasconfig/Lev1/Web/WebAppServer/SASServ
er2_1/conf/jaas.config', but there is no ldap configuration entry specified.
05:14:20,653 | INFO | [Catalina] | Initialization processed in 833 ms
05:14:21,457 | INFO | [StandardService] | Starting service [Catalina]
05:14:21,457 | INFO | [StandardEngine] | Starting Servlet Engine: Pivotal tc Runtime 3.2.11.RELEASE/8.5.32.A.RELEASE
05:14:21,464 | INFO | [HostConfig] | Deploying configuration descriptor [/sas_application/sasconfig/web/config/Lev1/Web/WebAp
pServer/SASServer2_1/conf/Catalina/localhost/SASEnvironmentMgrMidTier.xml]
05:14:21,464 | INFO | [HostConfig] | Deploying configuration descriptor [/sas_application/sasconfig/web/config/Lev1/Web/WebAp
pServer/SASServer2_1/conf/Catalina/localhost/SASStudio.xml]
05:14:21,464 | INFO | [HostConfig] | Deploying configuration descriptor [/sas_application/sasconfig/web/config/Lev1/Web/WebAp
pServer/SASServer2_1/conf/Catalina/localhost/SASWebDoc.xml]
05:14:29,884 | INFO | [[/SASWebDoc]] | No Spring WebApplicationInitializer types detected on classpath
05:14:29,902 | INFO | [[/SASWebDoc]] | Config path: file:////opt/sas/web/sasconfig/Lev1/Web/Common/LogConfig/
05:14:29,903 | INFO | [[/SASWebDoc]] | Context path: SASWebDoc
05:14:29,904 | INFO | [[/SASWebDoc]] | Configuring Log4j from URL at path: /file:////opt/sas/web/sasconfig/Lev1/Web/Common/Lo
gConfig/SASWebDoc-log4j.xml
05:14:29,904 | INFO | [[/SASWebDoc]] | isXMLConfigFile: true
05:14:29,987 | INFO | [[/SASWebDoc]] | Initializing Spring root WebApplicationContext

2025-04-13 05:14:40,423 [localhost-startStop-2] ERROR [unknown] com.sas.services.deployment.ServiceLoader - Unable to obtain s
ervice deployment from the SAS Metadata Repository metadata source.
2025-04-13 05:14:40,423 [localhost-startStop-2] ERROR [unknown] com.sas.services.deployment.PlatformServices - Exception encou
ntered starting services defined in metadata source
Server {
software component: "Platform Local Services"
host: "scemeta1.abcd.net"
port: "xxxx"
repository: "Foundation"
}
.
com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceE
xception: Unable to obtain service from factory class com.sas.services.session.SessionServiceFactory. [ com.sas.services.Servi
ceException: Unable to initialize the Logging Service. ] ]
05:14:40,428 | ERROR | [[/SASWebDoc]] | Exception sending context initialized event to listener instance of class [com.sas.svc
s.webapp.servlet.FrameworkContextListener]
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sas.svcs.discoveryService' defined in
class path resource [META-INF/local-jps.xml]: Invocation of init method failed; nested exception is com.sas.services.deploymen
t.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: Unable to obtain
service from factory class com.sas.services.session.SessionServiceFactory. [ com.sas.services.ServiceException: Unable to ini
tialize the Logging Service. ] ]
05:14:40,441 | WARN | [WebappClassLoaderBase] | The web application [SASWebDoc] appears to have started a thread named [Timer
-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:552)
java.util.TimerThread.run(Timer.java:505)


and Server Log:
2025-04-13 05:14:55,407 ERROR (localhost-startStop-1) [org.apache.catalina.loader.WebappClassLoaderBase] Found RMI Target with stub class class [com.sas.metadata.remote.MdObjectListImpl_Stub] and value [MdObjectListImpl_Stub[UnicastRef [liveRef: [endpoint:[127.0.0.1:39466](local),objID:[122b7ddb:1962d91edf9:-7403, -1146460060386749809]]]]]. This RMI Target has been forcibly removed to prevent a memory leak.
2025-04-13 05:14:55,415 INFO (localhost-startStop-1) [org.apache.catalina.startup.HostConfig] Deployment of configuration descriptor [/sas_application/sasconfig/web/config/Lev1/Web/WebAppServer/SASServer2_1/conf/Catalina/localhost/SASEnvironmentMgrMidTier.xml] has finished in [33,951] ms
2025-04-13 05:14:40,427 ERROR (localhost-startStop-2) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASWebDoc]] Exception sending context initialized event to listener instance of class [com.sas.svcs.webapp.servlet.springframework.DefaultContextLoaderListener]
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sas.svcs.discoveryService' defined in class path resource [META-INF/local-jps.xml]: Invocation of init method failed; nested exception is com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: Unable to obtain service from factory class com.sas.services.session.SessionServiceFactory. [ com.sas.services.ServiceException: Unable to initialize the Logging Service. ] ]

 

 

2 REPLIES 2
gwootton
SAS Super FREQ
An HTTP 404 response when accessing /SASStudio suggests the SAS Studio Web Application didn't start, so this is likely a failure happening in SASServer2_1 where SAS Studio runs. Are the other web applications and servers functional? For example, can you access /SASLogon and be prompted for authentication credentials, and/or authenticate successfully? Does restarting the middle tier have any impact on the issue?

From the messages provided it looks like the server may have had an issue connecting to the Metadata Server when it was starting, so this may have been the result of the middle tier being started before the Metadata tier.
--
Greg Wootton | Principal Systems Technical Support Engineer
VatKS
Calcite | Level 5

@gwootton , There is only SASStudio is being used. SAS logon is also not accessible, However, web server is deployed successfully. Restarting also didn't help. Everything Stopped and started as per defined procedure and best practices.

Raised it with SAS INstitute they suggested to run a Repair on Metadata server as they found an ID in log of Mwtadata which does not exists and server is trying to connect with it.

So once I try then will see if it works. probably planning for first May weekend.

 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 826 views
  • 1 like
  • 2 in conversation