DMS Application Fails to Initialize When Starting Weblogic Managed Server

(Doc ID 1373145.1)

Last updated on JANUARY 17, 2017

Applies to:

Oracle Fusion Middleware - Version to [Release Oracle11g]
Information in this document applies to any platform.


DMS application fails to properly initialize when starting a Weblogic Managed Server.

The managed server itself starts and functions properly.

When trying to gather metrics for the managed server from the Fusion Middleware Control
(/em), metrics and status are not displayed properly, or not displayed at all.

In this case it is the WLS_ODS managed server, but it can happen with any managed server.


In the managed server log, in this case it is wls_ods1.log


The error stack found is:

Aug 25, 2011 11:43:32 AM init
INFO: initialization error
oracle.jrf.PortabilityLayerException: Access not allowed for subject: principals=[], on ResourceType: Log Action: execute, Target: computeLogFilePath
at oracle.jrf.wls.WlsServerPlatformSupport.getServerLogPath(
at weblogic.servlet.internal.StubSecurityHelper$


Aug 25, 2011 11:43:33 AM
INFO: DMS startup class is not started. DMS runs with reduced functionality.
java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@2dd063b3 logDir=null agency=oracle.dms.reporter.SpyAgency@4c419444 dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@656d2378
at oracle.dms.impl.producer.Dumper.<init>(


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