After Applying Weblogic Patch or any CPU Patch, Discoverer Fails To Start From Enterprise Manager (EM) (Doc ID 1335764.1)

Last updated on APRIL 06, 2016

Applies to:

Oracle Discoverer - Version 11.1.1.2.0 to 11.1.1.6.0 [Release 11g]
Information in this document applies to any platform.
*** Checked for relevance 4-6-16 ***

Symptoms

After applying Weblogic patch, in exampe:

attempting to start Discoverer from EM Fusion Middleware Control fails to start.

WLS_DISCO.log shows the following warning and error messages:

 

<WLS_DISCO> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
<0000IwfJ00VBh45DrR3FCY1Db7rf000001> <1302101501376> <BEA-101162> <User
defined listener oracle.discoverer.applications.framework.ApplicationListener
failed: java.security.AccessControlException: access denied
(java.lang.RuntimePermission oracle.discoverer.connections).
java.security.AccessControlException: access denied
(java.lang.RuntimePermission oracle.discoverer.connections)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
at java.security.AccessController.checkPermission(AccessController.java:546)
at oracle.disco.remote.corba.SessionPooler._checkPermission(Unknown Source)

 

The very same can happen after applying ANY CPU patch when trying to start Discoverer:

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

 

Changes

Problem started occuring after applying Weblogic patch.

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