Home / Middleware

17 JRF-10001 to JRF-20036

JRF-10001: Fail to retrieve the application identifier. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application name.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10002: Fail to retrieve the WebLogic domain adminser server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the admin server name.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10003: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server name based on the current thread.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10004: Fail to check if the current server is admin server. The internal exception is: {0}.

Cause: The MBean server could not be accessed to verify that the server in the current thread is the admin server.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10005: Fail to retrieve the server log path. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server log path.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10006: Fail to copy the config file from {0} to the server directory {1}. The internal exception is: {2}.

Cause: The server config directory could not be accessed.

Action: Use the applyJRF() wlst command to ensure that the server has been properly configured.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10007: Fail to retrieve the system property domain.home.

Cause: The system property domain.home was not specified during WebLogic server startup.

Action: Specify the system property domain.home when starting the WebLogic server.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10008: I/O exception occurs when aceessing to the JRF template at {0}.

Cause: The specified JRF template was not accessaible.

Action: Verify that the template jar from the template location is present and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10009: I/O exception occurs when parsing config/config.xml from the JRF template at {0}.

Cause: The config.xml might be missing from the JRF template or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10010: The file config.xml under domain {0} does not exist.

Cause: The config.xml under domain config was missing or corrupted.

Action: Verify that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10011: Fail to parse the config.xml file from JRF template.

Cause: The domain config.xml might be missing or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home and that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10012: Fail to retrieve the property for the Common Components Home.

Cause: The Common Components Home property was not set.

Action: Set the Oracle Home property using the system property common.components.home or the environment variable COMMON_COMPONENTS_HOME.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10013: The specified Oracle Home directory {0} does not exist.

Cause: The Common Components Home directory did not exist.

Action: Verify that Common ComponentsHome, specified through the system property common.components.home or environment variable COMMON_COMPONENTS_HOME, is a valid directory.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10014: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application server platform information.

Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10015: The specified application server platform {0} is not supported by JRF.

Cause: JRF does not support the specified platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10016: The initialization of the server config directory from the Oracle Home {0} with domain directory {1} for copying fails. The internal exception is: {2}.

Cause: Could not retrieve the servers from the domain config.xml file.

Action: Verify that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10017: Unable to invoke {0} because the domain {1} has not been extended with JRF template.

Cause: Domain has not been extended with JRF template.

Action: Apply JRF template to the domain.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10018: Server or cluster "{0}" is not found.

Cause: The server or cluster is not found.

Action: Create the server or cluster.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10019: Could not obtain edit lock on the domain

Cause: Domain is being edited by someone else

Action: Wait until the edit lock on the domain is released and retry.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10020: Could not load/instantiate a WebLogic server platform support instance.

Cause: Could not load/instantiate a WebLogic server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10021: Could not load/instantiate a WebSphere server platform support instance.

Cause: Could not load/instantiate a WebSphere server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10022: Could not load system property 'oracle.domain.config.dir'.

Cause: Could not load system property 'oracle.domain.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.domain.config.dir' is set.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10023: Could not load system property 'oracle.server.config.dir'.

Cause: Could not load system property 'oracle.server.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.server.config.dir' is set.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10024: JRF is unable to determine the current application server platform.

Cause: JRF is unable to determine the current platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10025: Could not load/instantiate a JBoss server platform support instance.

Cause: Could not load/instantiate a JBoss server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10026: Failed to get application server edition

Cause: JRF Failed to retrieve application server edition

Action: Verify that the application server is installed and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10027: Operation is not supported on this application server edition

Cause: Operation is not supported on this platform edition.

Action: Verify it is the right application server edition.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10028: Invoke startup and shutdown class {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-10029: String {0} is in invalid format . Example of correct string format is {1}

Cause: String format is invalid.

Action: Correct the string format, see example of a correct string format in the exception message

Level: 1

Type: ERROR

Impact: Configuration

JRF-20001: Read domain {0} to applyJRF

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20002: Update JRF changes to domain {0} in {1} mode

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20003: Target JRF components to "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20004: Cannot copy {0} to {1}: "{2}"

Cause:

Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20005: Environment variables {0} not set

Cause:

Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20006: Copying JRF configuration files from {0} to {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20007: Unable to add help for JRF commands: "{0}"

Cause:

Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20008: No domain has been read

Cause: JRF detects that domain has not been read.

Action: Read the domain offline or connect online before invoke JRF WLST command.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20009: JRF component or service with type "{0}" and name "{1}" is not found on server "{2}".

Cause: Domain has not been extended with JRF or upgraded with new JRF version, or the applyJRF command is out-of-sync with JRF in the domain

Action: Extend domain with JRF template, or invoke upgradeJRF() to upgrade the domain if the install is upgraded.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20010: {0} is not found.

Cause: file not found

Action: Verify oraclehomeproperties.xml exist

Level: 1

Type: ERROR

Impact: Configuration

JRF-20011: Node GUID does not exist or node is empty in {0}.

Cause: node not found or no value

Action: Verify oraclehomeproperties.xml exist

Level: 1

Type: ERROR

Impact: Configuration

JRF-20012: System properties {0} not set

Cause:

Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20013: Target does not exist or not valid : {0}.

Cause: target not found or not valid

Action: Verify target exists and valid

Level: 1

Type: ERROR

Impact: Configuration

JRF-20014: Failed to create library at : {0}.

Cause: Creating shared library failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20015: Failed to create custom service : {0}.

Cause: Creating custom service failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20016: JRF_FAILED_CREATE_URLPROVIDER : {0}.

Cause: Creating URL Provider failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20017: Failed to config jvm args for : {0}.

Cause: Config JVM memory arguments failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20018: Failed to add jvm system property for : {0}.

Cause: Adding system property failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20019: Failed to parse template: {0}.

Cause: Template has error

Action: Verify template

Level: 1

Type: ERROR

Impact: Configuration

JRF-20020: Failed to get variable {0} from {1}.

Cause: Get variable failed

Action: Verify variable.xml

Level: 1

Type: ERROR

Impact: Configuration

JRF-20021: Failed to update targets of application {0}.

Cause: Failed to update application target

Action: Verify application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20022: Failed to update {0}.

Cause: Failed to update oracle jdbc driver path

Action: Verify server

Level: 1

Type: ERROR

Impact: Configuration

JRF-20023: Failed to install application {0}.

Cause: Failed to install application

Action: Verify application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20024: Failed to create variable {0} for {1}.

Cause: Failed to create variable

Action: Verify server

Level: 1

Type: ERROR

Impact: Configuration

JRF-20025: Need to apply jrf template to cell.

Cause: Cell is not jrf enabled

Action: Apply jrf template to the cell since this cell is not jrf enabled

Level: 1

Type: ERROR

Impact: Configuration

JRF-20026: Could not load/instantiate {0} JRFService instance.

Cause: Could not load/instantiate a JRFService implementation class instance.

Action: Check if JRFService implementation class in the error message can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20028: JRFService not supported

Cause: JRFService is not supported.

Action: Check if the server has related JRFService available.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20029: MapModulesToServers is disabled, cannot modify target of application {0}.

Cause: MapModulesToServers is disabled, cannot modify target of application.

Action: Enable MapModulesToServers task for this application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20030: Enable StartupBeansService failed on server {0}.

Cause: Enable StartupBeansService failed

Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20031: Initializing sun.awt.AppContext to avoid a redeployment leak. Please see bug 7711331

Cause: Avoid a redeployment leak

Action: Initializing sun.awt.AppContext

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20032: sun.awt.AppContext not found

Cause: sun.awt.AppContext not found

Action: Verify jdk

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20033: JRF startups - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual startup stacktrace are included in the error log.

Cause: JRF is not configured properly

Action: Resolve these issues

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20034: JRF shutdowns - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual shutdown stacktrace are included in the error log.

Cause: JRF is not configured properly

Action: Resolve these issues

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20035: invalid format.

Cause: invalid url format

Action: fix url format

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20036: checkIfJRFApplied api failed on target {0} with exception {1}

Cause: The operation that checks if JRF applied to a target server or cluster failed

Action: See message and exception stack trace in admin server log to debug

Level: 1

Type: NOTIFICATION

Impact: Configuration