OAM_ADMIN status is in failed status
Locked
12
12
 
|
Hi Erman
My OAM admin server is getting started with running status and the console is also opening. But oam_admin deployment is showing the status as "failed"due to which oamconsole is not opening. Below is the snippet from the admin server logs <Mar 2, 2017 7:55:47 AM EST> <Warning> <HTTP> <BEA-101162> <User defined listener oracle.security.am.lifecycle.ApplicationLifecycle failed: oracle.security.am.common.utilities.exception.AmRuntimeException: Component Bootstrap Failed. oracle.security.am.common.utilities.exception.AmRuntimeException: Component Bootstrap Failed at oracle.security.am.lifecycle.ApplicationLifecycle.contextInitialized(ApplicationLifecycle.java:117) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181) Truncated. see log file for complete stacktrace Caused By: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at oracle.security.am.lifecycle.util.ComponentBootstrapHelper.invokeMethod(ComponentBootstrapHelper.java:136) Truncated. see log file for complete stacktrace Caused By: oracle.security.am.install.AMInstallException: DB Policy not configured in mixed mode at oracle.security.am.install.startup.AMBootstrapListener.checkDBPolicyStoreConfigured(AMBootstrapListener.java:161) at oracle.security.am.install.startup.AMBootstrapListener.initialize(AMBootstrapListener.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Truncated. see log file for complete stacktrace > <Mar 2, 2017 7:55:47 AM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'oam_admin [Version=11.1.2.0.0]'. weblogic.application.ModuleException: at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) Truncated. see log file for complete stacktrace Caused By: oracle.security.am.install.AMInstallException: DB Policy not configured in mixed mode at oracle.security.am.install.startup.AMBootstrapListener.checkDBPolicyStoreConfigured(AMBootstrapListener.java:161) at oracle.security.am.install.startup.AMBootstrapListener.initialize(AMBootstrapListener.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Truncated. see log file for complete stacktrace > <Mar 2, 2017 7:55:48 AM EST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.> <Mar 2, 2017 7:55:48 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN> <Mar 2, 2017 7:55:48 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING> <Mar 2, 2017 7:55:48 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.56.3:7003 for protocols iiop, t3, ldap, snmp, http.> <Mar 2, 2017 7:55:48 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7003 for protocols iiop, t3, ldap, snmp, http.> <Mar 2, 2017 7:55:48 AM EST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "oam_domain" running in Production Mode> <Mar 2, 2017 7:55:48 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> <Mar 2, 2017 7:55:48 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> |
Re: OAM_ADMIN status is in failed status
Administrator
|
Take a look at this note ->
OAM 11g Server Error "Component Bootstrap Failed" caused by DB Policy Not Configured in Mixed Mode (Doc ID 2008417.1) Send me the steps that you have taken (in detail, with screenshots) and make me understand what you mean by "oam_admin deployment" for further diagnostics. |
|
|
Hi Erman
I have followed this particular note and getting a different error which is mentioned below. Mar 02, 2017 9:05:13 AM oracle.security.jps.internal.policystore.PolicyStoreHelper getPolicyStoreInstance SEVERE: The policy store property oracle.security.jps.farm.name is invalid or not defined. java.util.logging.ErrorManager: 5 java.util.MissingResourceException: Can't find resource for bundle oracle.security.jps.internal.common.resources.common.CommonResources, key JPS-04090 at java.util.ResourceBundle.getObject(ResourceBundle.java:395) at java.util.ResourceBundle.getString(ResourceBundle.java:355) at oracle.security.jps.util.JpsBundle.getString(JpsBundle.java:178) at oracle.security.jps.util.JpsBundle.getString(JpsBundle.java:207) at oracle.security.jps.JpsLocalizableException.getLocalizedMessage(JpsLocalizableException.java:145) at oracle.security.jps.JpsLocalizableException.getLocalizedMessage(JpsLocalizableException.java:131) at java.lang.Throwable.toString(Throwable.java:480) at java.lang.String.valueOf(String.java:2849) at java.lang.StringBuilder.append(StringBuilder.java:128) at java.lang.Throwable.printEnclosedStackTrace(Throwable.java:695) at java.lang.Throwable.printEnclosedStackTrace(Throwable.java:709) at java.lang.Throwable.printStackTrace(Throwable.java:667) at java.lang.Throwable.printStackTrace(Throwable.java:721) at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:157) at java.util.logging.StreamHandler.publish(StreamHandler.java:196) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:105) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.logp(Logger.java:841) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.init(PDPServiceImpl.java:482) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.<init>(PDPServiceImpl.java:455) at oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider.getInstance(PDPServiceProvider.java:100) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:159) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:165) at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:3152) at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:3149) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:3149) at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3480) at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3466) at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:188) at oracle.security.jps.internal.policystore.TenantJavaPolicyProvider.<init>(TenantJavaPolicyProvider.java:161) at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:306) at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:279) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:383) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022) at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873) at weblogic.security.SecurityService.start(SecurityService.java:141) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) <Mar 2, 2017 9:05:13 AM EST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-04001: Cannot read the default policy store.> <Mar 2, 2017 9:05:13 AM EST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Can't find resource for bundle oracle.security.jps.internal.common.resources.common.CommonResources, key JPS-04090> *************************************************************************** The WebLogic Server encountered a critical failure java.util.MissingResourceException: Can't find resource for bundle oracle.security.jps.internal.common.resources.common.CommonResources, key JPS-04090 at java.util.ResourceBundle.getObject(ResourceBundle.java:395) at java.util.ResourceBundle.getString(ResourceBundle.java:355) at oracle.security.jps.util.JpsBundle.getString(JpsBundle.java:178) at oracle.security.jps.util.JpsBundle.getString(JpsBundle.java:207) at oracle.security.jps.JpsLocalizableException.getLocalizedMessage(JpsLocalizableException.java:145) at oracle.security.jps.JpsLocalizableException.getLocalizedMessage(JpsLocalizableException.java:131) at java.lang.Throwable.toString(Throwable.java:480) at com.bea.logging.ThrowableWrapper.<init>(ThrowableWrapper.java:26) at com.bea.logging.ThrowableWrapper.<init>(ThrowableWrapper.java:29) at com.bea.logging.ThrowableWrapper.<init>(ThrowableWrapper.java:29) at com.bea.logging.ThrowableWrapper.<init>(ThrowableWrapper.java:29) at com.bea.logging.ThrowableWrapper.<init>(ThrowableWrapper.java:29) at com.bea.logging.BaseLogRecord.setThrown(BaseLogRecord.java:172) at com.bea.logging.BaseLogRecord.<init>(BaseLogRecord.java:100) at weblogic.logging.WLLogRecord.<init>(WLLogRecord.java:63) at weblogic.logging.JDKLoggerFactory.createBaseLogRecord(JDKLoggerFactory.java:85) at com.bea.logging.LoggingService.log(LoggingService.java:234) at weblogic.kernel.T3SrvrLogger.logServerSubsystemFailedWithTrace(T3SrvrLogger.java:2359) at weblogic.t3.srvr.T3Srvr.setFailedState(T3Srvr.java:323) at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:895) at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469) at weblogic.Server.main(Server.java:71) Reason: Can't find resource for bundle oracle.security.jps.internal.common.resources.common.CommonResources, key JPS-04090 *************************************************************************** <Mar 2, 2017 9:05:13 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> =========================== Can you share your email id so that i can send you the admin server logs and screenshot. |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
you can attach the logs here. Upload them as files . 11 Tem 2017 06:58 tarihinde "Raja [via Erman Arslan's Oracle Forum]" <[hidden email]> yazdı: Hi Erman |
|
|
Hi Erman
I can't find anything via which i can upload the files. |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
You should first create an account .
With your account logged in, click reply. While you are replying you should click on "More>Upload a file" to upload a file. |
|
|
|
|
|
|
Hi Erman
I have uploaded the admin server logs(1.without doing any changes in jps.xml 2.after doing the changes in jps.xml as per metalink note) and the respective screenshots for OAM Note: I am using same database for oid and oam. |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
Is oam_admin deployed to the admin server?
Or is it deployed to the oam_server1 or oam_policy_mgr1 or omsm_server1? |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
Send me the oam_server1 logs as well.
|
|
|
Hi Erman
I think oam_admin is deployed under admin server. How to i verify that? Thanks |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
Click on the application name and then open the targets tab. You will see it there.
|
|
|
|
|
Hi Erman
Have uploaded the oam_server1 logs. And oam_admin is deployed under admin server. Thanks |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
You have :
oracle.security.am.install.AMInstallException: DB Policy not configured in mixed mode Implement the actions documented in this note -> OAM 11g Server Error "Component Bootstrap Failed" caused by DB Policy Not Configured in Mixed Mode (Doc ID 2008417.1) |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
This error message should not be in the logs.
I already sent you this document previosly. Are you sure that you took the actions documented there? |
|
|
Yes Erman. I have also uploaded the admin server logs after doing the changes. The log attached is
Adminoamafterjpschanges.out |
|
|
From the log, i can see a section:-JPS-04001: Cannot read the default policy store
And from metalink, i found one note:-Unable To Start Weblogic Admin Server Due To JPS-04001 Post Upgrade From OAM 11.1.2.2 To OAM 11..2.3 (Doc ID 2232659.1), which states that i should apply a patch 13964737-YVDZ (JSSE patch. Required for WLS 10.3.6 with JDK 7) Please let me know your thoughts. Thanks |
Re: OAM_ADMIN status is in failed status
|
Administrator
|
in managed server log, you have:
oracle.security.am.install.AMInstallException: DB Policy not configured in mixed mode I can't see your admin server log. I think you deleted it from this forum. anyways, if you JPS-04001 , take the actions documented in 2232659.1. |
«
Return to Middleware / Weblogic
|
1 view|%1 views
| Free forum by Nabble | Edit this page |