A PASOE instance fails to start due to the following exception:
java.lang.RuntimeException: Error creating bean with name 'org.springframework.security.authentication.ProviderManager#2': Cannot resolve reference to bean 'oerealm' while setting constructor argument;Error creating bean with name 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0' in WEBAPP: MyWebApp

A PASOE instance which is configured with the OEREALM authentication fails to start in OpenEdge Explorer / Management with the following error:

Start operation has timed out for PAS instance : oepas1, Does not get response from pas server in specified timeout 180 secs.

An exception similar to the following is written to the "localhost.<date>.log" file:

ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.listenerStart - Exception sending context initialized event to listener instance of class [com.progress.appserv.services.security.OESpringContextLoaderListener]
java.lang.RuntimeException: Error creating bean with name 'org.springframework.security.authentication.ProviderManager#2': Cannot resolve reference to bean 'oerealm' while setting constructor argument;Error creating bean with name 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0' in WEBAPP: MyWebApp
	at com.progress.appserv.services.security.OESpringContextLoaderListener.handleException(OESpringContextLoaderListener.java:31)
	at com.progress.appserv.services.security.OESpringContextLoaderListener.contextInitialized(OESpringContextLoaderListener.java:19)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4462)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4914)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:683)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:658)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:661)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1025)
	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1919)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
	at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
	at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:826)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:476)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1619)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:318)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:114)
	at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
	at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:345)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:893)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:794)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1332)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1322)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.base/java.lang.Thread.run(Thread.java:834)

An exception similar to the following may also be written to the "<webapp name>.<date>.log" file:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.filterChains': Cannot resolve reference to bean 'org.springframework.security.web.DefaultSecurityFilterChain#2' while setting bean property 'sourceList' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.DefaultSecurityFilterChain#2': Cannot resolve reference to bean 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0' while setting constructor argument with key [8]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0': Cannot resolve reference to bean 'org.springframework.security.authentication.ProviderManager#2' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.authentication.ProviderManager#2': Cannot resolve reference to bean 'oerealm' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oerealm': Cannot resolve reference to bean 'OERealmAuthProvider' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OERealmAuthProvider' defined in ServletContext resource [/WEB-INF/spring/authManagers.xml]: Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Missing registry file (OERealmAuthProvider): ABLDomainRegistry.keystore 

An exception similar to the following may be written to the "<webapp name>.agent.<date>.log" file:

-- Connection failure for host <hostname> port 52680 transport TCP. (9407)
MSAS csMtSendABLSessionInfo : error sending session info to broker : num_user_sessions= 1  err= -4004

"ABLDomainRegistry.keystore" is the value defined for the "OERealm.AuthProvider.registryFile" property in the webapp's "oeablSecurity.properties" file. For example:

OERealm.AuthProvider.registryFile=ABLDomainRegistry.keystore

The PASOE instance seems to start fine through the 'tcman start' command, but the same exceptions occur in the log files.

They keystore defined for the "OERealm.AuthProvider.registryFile" property in the webapp's "oeablSecurity.properties" file is missing.

Place the missing keystore in the <PASOE Instance>\conf directory.

Progress Article(s):
PASOE instance fails to start in OEM due to java.lang.RuntimeException