Unable to Access soa-infra and the Composites from Enterprise Manager during Specific Time Intervals "oracle.sysman.emSDK.app.exception.EMSystemException"

(Doc ID 1357692.1)

Last updated on DECEMBER 01, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 14-Feb-2013***

Symptoms

While trying to access the SOA in production environment, the composites and the soa-infra are not accessible.
The issue occurs between 00:00 - 04:00 server time.
During this time the instances created by the application are executed as expected.

In the admin server diagnostic log and enterprise manager log files the following error message is thrown:

[AdminServer] [NOTIFICATION:32] [] [oracle.sysman.emSDK.view.errPopup.ErrorPopupUtil] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000J7zHRR_DGfX5Hv5Eif1ELA4c0000mR,0] [APP: em] [dcid: aa00922f213f915d:5af525e1:131fa972163:-7fe8-0000000000001020] An error happened while connecting to soa-infra runtime at t3://hostname:8001/soa-infra. Please view the log files for details.[[
oracle.sysman.emSDK.app.exception.EMSystemException
at oracle.sysman.emai.model.sca.WLSObjectHelper._createLocator(WLSObjectHelper.java:81)
at oracle.sysman.emai.model.sca.WLSObjectHelper.getLocator(WLSObjectHelper.java:43)
at oracle.sysman.emai.model.sca.SCAObject.getLocator(SCAObject.java:72)
at oracle.sysman.emai.model.sca.share.SCASharedModel.getLocator(SCASharedModel.java:21)
at oracle.sysman.emai.model.sca.share.composite.CompositeInstances.initialize(CompositeInstances.java:104)
at oracle.sysman.emai.model.sca.EMModel.initializeSCAData(EMModel.java:25)
at oracle.sysman.emai.model.sca.SCAObject.initializeData(SCAObject.java:59)
...
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
...
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticated.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:119)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
...
]]


Enterprise Manager logs:

./FMW_HOME/user_projects/domains/<DOMAIN_NAME>/servers/AdminServer/sysman/log/emoms.log
./FMW_HOME/user_projects/domains/<DOMAIN_NAME>/servers/AdminServer/sysman/log/emoms.trc


Admin server logs:

./FMW_HOME/user_projects/domains/<DOMAIN_NAME>/servers/AdminServer/logs/AdminServer-diagnostic.log

Cause

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