23 OHS-03506 to OHS-04533
- OHS-03572
- MaxRequestWorkers exceeds range, raise ServerLimit.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03573
- MaxRequestWorkers exceeds range, raise ServerLimit or ThreadPerChild.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03575
- The value of ThreadLimit cannot be less than the value of ThreadsPerChild.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03576
- The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03577
- The value of ServerLimit cannot be less than the value of MaxRequestWorkers.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03578
- The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxRequestWorkers.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03582
- The specified module "{0}" is not installed. Module has to be installed before configuring it.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03604
- Unable to find Server Name, Setting it to default AdminServer
- Category:
- Configuration
- Cause:
- Action:
- OHS-03607
- Port {0} for {1} is already in use on machine "{2}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03608
- No ports for {0} were available for auto-assignment on machine "{1}" in the range {2}-{3}.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03611
- Instance "{0}" is in state "{1}" and cannot be deleted.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03612
- The port value, {0}, has already been used and cannot be configured for {1}.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03614
- The umask "{0}" is not valid, please provide an octal number less than or equal to 0777.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03703
- P12 Wallet is null; Possibly because the wallet is absent/not configured.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03708
- WLCluster not configured; Not allowed to call listWLCluster
- Category:
- Configuration
- Cause:
- Action:
- OHS-03709
- DynamicServerList is not configured ; Illegal Usage
- Category:
- Configuration
- Cause:
- Action:
- OHS-03711
- SSLCRLCheck or SSLCARevocationFile is not configured properly
- Category:
- Configuration
- Cause:
- Action:
- OHS-03718
- The file requested, "{0}", is not part of the current OHS configuration. Please enable the file first.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03720
- No virtual host name specified. Invalid virtual host name.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03721
- Default Virtual Host name must be a port number or * or an empty string.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03722
- Virtual Host-Server Name "{0}"-"{1}" already exists.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03723
- Syntax Error in Log configuration: operation failed.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03724
- Could not parse configuration file template value "{0}" on createInstance() invocation.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03725
- Key "{0}" is not a valid configuration file template value on createInstance() invocation.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03726
- Configuration file template value "{0}" does not contain a valid port number on createInstance() invocation.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03728
- Instance name invalid. "{0}" is longer than 30 characters.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03729
- Instance name invalid. "{0}" does not start with a letter.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03730
- Instance name invalid. "{0}" contains an invalid character.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03731
- Instance name invalid :"{0}". The following reserved names (ignoring letter case) are not allowed as instance names : "{1}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03734
- Invalid port number "{0}" is specified. Port number must be between 1 and 65535 inclusive.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03735
- Invalid log level :"{0}". Valid log levels are : "{1}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03737
- Property file {0} could not be loaded; using defaults
- Category:
- Configuration
- Cause:
- Action:
- OHS-03740
- KeepAliveTimeout "{0}" is not valid. Use KeepAliveTimeout num[ms|s|mi|h].
- Category:
- Configuration
- Cause:
- Action:
- OHS-03742
- Invalid module "{0}". Only module identifiers specified in LoadModule directives with the trailing _module omitted and statically compiled modules are supported
- Category:
- Configuration
- Cause:
- Action:
- OHS-03745
- LogLevel syntax is not valid. Use LogLevel [module:]level [module:level] ...
- Category:
- Configuration
- Cause:
- Action:
- OHS-03748
- OraLogLevel syntax is not valid. Use OraLogLevel [module_name] <msg_type>[:msg_level] ...
- Category:
- Configuration
- Cause:
- Action:
- OHS-03755
- VirtualHost copntainer with value "{0}" was not found in the file "{1}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03756
- There was no "{0}" directive with value "{1}" in the file "{2}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03802
- Load Operation finished in VH SSLResource for instance {0}
- Category:
- Configuration
- Cause:
- Action:
- OHS-03806
- Unregistered all configuration MBeans for instance {0}
- Category:
- Configuration
- Cause:
- Action:
- OHS-03814
- An error occured while setting the file contents for the config file "{0}". Make sure that the specified configuration file content is of valid format.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03816
- The specified configuration file "{0}" is not part of the configuration.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03817
- An error occurred setting the contents of config file "{0}": {1}
- Category:
- Configuration
- Cause:
- Action:
- OHS-03820
- Directory "{0}" is missing from the Oracle HTTP Server installation. The instance cannot be created.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03821
- The ohs.product.home property is not set. The instance cannot be created.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03822
- The fully qualified domain name for host "{0}" could not be resolved. ServerName will be set to "{1}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03840
- Listen directive corresponding to the address({0}) exists in configuartion file of another instance
- Category:
- Configuration
- Cause:
- Action:
- OHS-03845
- Exporting an empty KeyStore is not allowed, please add certificate(s) before exporting.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03848
- The value "{0}" is not valid for the directive "{1}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03849
- MinSpareThreads cannot be greater than MaxSpareThreads.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03850
- MaxSpareThreads cannot be less than MinSpareThreads.
- Category:
- Configuration
- Cause:
- Action:
- OHS-03852
- Error while importing the contents of a wallet for the instance "{0}".
- Category:
- Configuration
- Cause:
- Action:
- OHS-03853
- The certificates in the wallet "{0}" are not being imported.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04001
- Error while starting the server {0}: server start/stop is already in progress
- Category:
- Process
- Cause:
- Action:
- OHS-04002
- Error while stopping the server {0}: server start/stop is already in progress
- Category:
- Process
- Cause:
- Action:
- OHS-04004
- Error while restarting the server {0}: server start/stop is already in progress
- Category:
- Process
- Cause:
- Action:
- OHS-04006
- Error while restarting the server {0}: server is not currently running
- Category:
- Process
- Cause:
- Action:
- OHS-04007
- Failed to start the server {0} successfully: attempting to cleanup the process
- Category:
- Process
- Cause:
- Action:
- OHS-04008
- Failed to stop the server {0} gracefully: attempting to kill
- Category:
- Process
- Cause:
- Action:
- OHS-04009
- Failed to re-start the server {0} completely: attempting to cleanup the process
- Category:
- Process
- Cause:
- Action:
- OHS-04010
- Server {0} is in an inconsistent state -- the process could not be stopped or killed. This issue must be manually resolved
- Category:
- Process
- Cause:
- Action:
- OHS-04014
- Property {0} was configured with invalid value {1} in file {2}
- Category:
- Process
- Cause:
- Action:
- OHS-04032
- Invalid property environment variable name {0} configured in {1}: {2}. Property environment name syntax is {3}, where {4} is the optional append flag, {5} is the optional numeric order value, and {6} is the name of the environment variable
- Category:
- Process
- Cause:
- Action:
- OHS-04034
- SSL is not enabled for the admin port of {0}. Thus, the connection between NodeManager and the admin port of {1} is not secure. SSL must be enabled for this connection. For more information on how to enable SSL for this connection, refer to OHS documentation
- Category:
- Process
- Cause:
- Action:
- OHS-04035
- nm-wallet is not configured for {0} in ohs.plugins.nodemanager.properties. Hence {1} failed to start
- Category:
- Process
- Cause:
- Action:
- OHS-04036
- ServerName directive is not configured in admin.conf of {0}
- Category:
- Process
- Cause:
- Action:
- OHS-04037
- HostName/IP address is not configured for Listen directive in admin.conf of {0}
- Category:
- Process
- Cause:
- Action:
- OHS-04102
- InstanceDirectory {0} does not contain a valid OHS instance
- Category:
- Process
- Cause:
- Action:
- OHS-04109
- Errors occured while commiting changes for the following instances: {0}. Check {1} for details
- Category:
- Process
- Cause:
- Action:
- OHS-04251
- Failed to reach the OHS instance: {0} Make sure that instance is up and running
- Category:
- Process
- Cause:
- Action:
- OHS-04401
- Unable to find template directory {0} within OHS installation at {1}. Make sure that {1} contains a valid OHS installation.
- Category:
- Process
- Cause:
- Action:
- OHS-04402
- Unable to copy template directory {0} to directory {1} within new instance
- Category:
- Process
- Cause:
- Action:
- OHS-04501
- Connect to a WebLogic server before using this command.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04507
- Instance "{0}" is in state "{1}" and cannot be deleted.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04513
- The following required arguments are missing :{0} .
- Category:
- Configuration
- Cause:
- Action:
- OHS-04514
- Port {0} was specified more than once for the new instance.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04515
- The new instance uses a privileged port. Refer to the privileged port configuration information in the product documentation.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04517
- Instance names are limited to thirty characters, must begin with a letter, may contain letters, numbers, -, or _, and must not be one of the following reserved names(ignoring letter case): {0}
- Category:
- Configuration
- Cause:
- Action:
- OHS-04525
- Privileged ports are not supported with this command.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04526
- NodeManager is unreachable. "{0}" might be in undeletable state because the NodeManager is unreachable.
- Category:
- Configuration
- Cause:
- Action:
- OHS-04528
- Disconnect from WebLogic server before using this command.
- Category:
- Configuration
- Cause:
- Action: