38 JRF-10001 to JRF-20011

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-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-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.

Cause: The WLST applyJRF command is out-of-sync with the template that is used to extend the domain, or domain has not been installed with JRF.

Action: Use the wlst.sh/cmd from the same Oracle Home that contains the JRF template, which was used to extend the domain; or extend the domain with JRF template if JRF is not installed

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