EM12c: Auto Refresh Weblogic Domain jobs are failing with 'Null'
(Doc ID 2011890.1)
Last updated on SEPTEMBER 17, 2021
Applies to:
Enterprise Manager for Fusion Middleware - Version 12.1.0.5.0 to 12.1.0.7.0Information in this document applies to any platform.
Symptoms
In Oracle Enterprise Manager (EM) there is an Auto Refresh Feature. This feature Add/Updates targets in EM, if new targets has been deployed on the Oracle WebLogic Server side.
Jobs are working with the
(EM-FMW-BP (Agent Monitoring) 12.1.0.6.6) and failing with the same patch level.
When we check the output of the job from UI it shows only 'null' as output.
Auto Refresh WebLogic Jobs are failing with the following exception in the logs.
---------------
2014-12-30 13:53:06,843 [RJob Step 414831] ERROR commands.WebLogicDomainRefreshCommand logp.251 - Error in executeCommand()
java.lang.NullPointerException
at oracle.sysman.emas.model.discovery.jobs.commands.WebLogicDomainRefreshCommand.executeCommand(WebLogicDomainRefreshCommand.java:132)
at oracle.sysman.emdrep.jobs.CommandStepExecutor.execute(CommandStepExecutor.java:160)
at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.execute(ConsoleJobStepExecutor.java:337)
at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.executeStep(ConsoleJobStepExecutor.java:218)
at sun.reflect.GeneratedMethodAccessor4582.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:370)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:202)
at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:477)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1131)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1129)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:74)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:83)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:458)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1149)
In the EM Console it shows only Null and no other error messages.
At the same time if we run the job manually by right clicking the FARM it works fine.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |