Last updated on AUGUST 05, 2016
Applies to:Oracle Access Manager - Version 22.214.171.124.1 and later
Information in this document applies to any platform.
Admin server and OAM Managed Server both start successfully, however the OAM server is not listening on the proxy port and the oam_server deployment listed in the WLS console deployments is in a failed state. A review of the $DOMAIN_HOME/servers/oam_server1/logs/oam_server1-diagnostic.log shows an error similar to:
####<Oct 2, 2013 10:33:56 AM EDT> <Error> <HTTP> <ucolhp1o.csd.disa.mil> <WLS_OAM1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000K5t_aTU5i^2xfoJ7C_1IJ2uZ000004> <1380724436923> <BEA-101216> <Servlet: "spmanager" failed to preload on startup in Web application: "/oamfed".
java.lang.RuntimeException: oracle.security.fed.jvt.discovery.exceptions.DiscoveryFinderException: OAM property is not of type String: /DeployedComponent/Server/NGAMServer/Profile/OAMServerProfile/OAMSERVER/serverhost
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms