AdminUI fails to start up with error net.sf.ehcache.CacheException: Could not create cache directory
Article ID: 376223
Updated On:
Products
Issue/Introduction
2024-08-30 16:41:38,897 ERROR [io.undertow.servlet] (ServerService Thread Pool -- 55) Failed to start the SiteMinder Admin Directory: net.sf.ehcache.CacheException: Could not create cache directory "/apps/CA/siteminder/adminui/standalone/data/apacheds/siteminder/cache/e09a2205-e0b8-4996-bcaf-1001c06bdf31".
at net.sf.ehcache.store.disk.DiskStorageFactory.getDataFile(DiskStorageFactory.java:888)
at net.sf.ehcache.store.disk.DiskStorageFactory.<init>(DiskStorageFactory.java:126)
at net.sf.ehcache.store.disk.DiskStore.create(DiskStore.java:162)
at net.sf.ehcache.store.DiskBackedMemoryStore.createDiskStore(DiskBackedMemoryStore.java:60)
at net.sf.ehcache.store.DiskBackedMemoryStore.create(DiskBackedMemoryStore.java:48)
at net.sf.ehcache.Cache.initialise(Cache.java:1102)
at net.sf.ehcache.CacheManager.initializeEhcache(CacheManager.java:1258)
at net.sf.ehcache.CacheManager.addCacheNoCheck(CacheManager.java:1289)
at net.sf.ehcache.CacheManager.addConfiguredCaches(CacheManager.java:706)
at net.sf.ehcache.CacheManager.doInit(CacheManager.java:424)
at net.sf.ehcache.CacheManager.init(CacheManager.java:358)
at net.sf.ehcache.CacheManager.<init>(CacheManager.java:243)
at org.apache.directory.server.core.api.CacheService.initialize(CacheService.java:164)
at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.build(DefaultDirectoryServiceFactory.java:251)
at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.init(DefaultDirectoryServiceFactory.java:125)
at com.ca.siteminder.directory.servlet.DirectoryServiceContextListener.contextInitialized(DirectoryServiceContextListener.java:109)
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:219)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:187)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:255)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:87)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:750)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Cause
It's file permission issue.
For example, try to use another specific user to start up adminUI
Resolution
It's recommend to continue using the same user to install the adminUI to run it.
If need to change user, then change the owner for the entire directory tree of the adminUI.
For example, assume that the new user is smuser, the admin install folder is /apps/CA/siteminder/adminui, then the command will be,
chown -R smuser:smuser /apps/CA/siteminder/adminui
Additional Information
Feedback
