Explanation | None |
Action | None |
Explanation | The wsadmin launcher has been invoked with the "-c" option. This option requires that a string be supplied to be interpreted as a wsadmin command. |
Action | Reissue the wsadmin command with a command string following the -c option. |
Explanation | The wsadmin launcher has been invoked with an option that requires the name of a file, but no such argument was found. These options are -f, -p, and -profile. |
Action | Reissue the wsadmin command with a file name following the option. |
Explanation | The wsadmin launcher has been invoked with the -host option, but no host name argument was found. |
Action | Reissue the wsadmin command with a host name following the -host option. |
Explanation | The wsadmin launcher has been invoked with the -port option, but no port number argument was found. |
Action | Reissue the wsadmin command with a port number following the -port option. |
Explanation | The wsadmin launcher has been invoked with the -lang option, but no language argument was found. |
Action | Reissue the wsadmin command with a scripting language name following the -lang option. |
Explanation | The wsadmin launcher has been invoked with the -conntype option, but no connection type argument was found. |
Action | Reissue the wsadmin command with a connection type (e.g. SOAP, RMI) following the -conntype option. |
Explanation | The wsadmin launcher has been invoked with the -port option, but the string following -port is not an integer. |
Action | Reissue the wsadmin command with an integer port argument for the -port option. |
Explanation | The wsadmin launcher cannot determine what port number should be used when a connector is created. |
Action | Supply a -port option on the wsadmin command line or a com.ws.scripting.port property in the wsadmin.properties file. |
Explanation | An invalid connection type was supplied on the command line -conntype option or in the com.ws.scripting.connectionType property in the wsadmin.properties file. |
Action | Correct the connection type on the command line or properties file: use "SOAP," "RMI," or "NONE." |
Explanation | The wsadmin launcher has been invoked with an option that requires the name of a file, but the file can not be found. |
Action | Correct the name of the file specified by -p, -f, or -profile, or in a wsadmin.properties file. |
Explanation | During wsadmin initialization, a properties file could not be loaded. |
Action | Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems. |
Explanation | wsadmin cannot determine which scripting language to use for the specified file. |
Action | Specify a -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | wsadmin cannot determine which scripting language to use for an interactive session. |
Action | Specify a -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | An error occurred during the interactive execution of the specified command. |
Action | Examine the accompanying exception information to determine the appropriate action. |
Explanation | An IO exception occurred while reading a script or profile. |
Action | Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems. |
Explanation | An exception occurred while running a script or profile. |
Action | Examine the wsadmin.traceout log file to determine the problem. |
Explanation | An unsupported scripting language was specified. |
Action | Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option. |
Explanation | Connection type information is required for wsadmin -- it can be specified either by the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties. |
Action | Specify a valid connection type; this can be done either by the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties. |
Explanation | The specified connection type requires that a host be specified. |
Action | Specify a valid host; this can be done either by the -host command line option or the com.ibm.ws.scripting.host property in wsadmin.properties. |
Explanation | wsadmin cannot determine which scripting language to use with the -c option. |
Action | Specify a -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | An error occurred during the execution of the specified command. |
Action | Examine the exception information provided in the message to determine the appropriate course of action. |
Explanation | An error was reported from the connector when trying to establish a connection to the host. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. |
Explanation | wsadmin attempted to create an ObjectName object from a string that was incorrectly formatted. |
Action | Insure that the string included in the failing command is correctly formatted for an ObjectName string. In particular, this can occur if the string is empty. |
Explanation | An AdminControl getConfigId or completeObjectName command was invoked; these commands only return a single result, but the ObjectName template passed in as an argument matches two or more running MBeans. This informational message is issued to indicate that the first matching MBean will be used. |
Action | None, if the first matching MBean is sufficient. Otherwise, re-issue the command, specifying the desired MBean more completely. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An error was reported from the connector when trying to establish a connection to the server. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server may not be running. |
Explanation | An error occured in setting the cache directory permission. |
Action | Enusre that cache directory exists and the user attempting to set the file permissions is authorized to change it. |
Explanation | None |
Action | None |
Explanation | This message is displayed when a wsadmin AdminConfig command is attempted and the wsadmin process is not connected to a server with a running config service. |
Action | Reissue the wsadmin command, specifying a server with a running config service. |
Explanation | This message is logged when wsadmin is initialized and the wsadmin process cannot cconnect to a server. |
Action | Reissue the wsadmin command so that a server connection is made. |
Explanation | An AdminControl reconnect command failed to reconnect to the server. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server may not be running. |
Explanation | This informational message is displayed when an AdminControl reconnect command sucessfully completes. |
Action | None |
Explanation | An incorrect config id was specified for an AdminConfig command. |
Action | Specify a valid config id -- such an id must have one of two forms: name(uri) or (uri). In this case, no closing parenthesis was found. |
Explanation | An incorrect config id was specified for an AdminConfig command. |
Action | Specify a valid config id -- such an id must have one of two forms: name(uri) or (uri). In this case, no opening parenthesis was found. |
Explanation | An attribute was specified on an AdminConfig command that wsadmin is unable to process. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | An invalid attribute name was specified for the given type. |
Action | Correct the attribute name; use the AdminConfig attributes command for a list of valid attribute names. |
Explanation | An enum attribute could not be initialized by AdminConfig. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | When an object is created with AdminConfig, wsadmin needs to determine what attribute name to use for the new object in the parent. In certain cases it is not possible to determine this information -- this is true if the parent object contains more than one attribute of the type being created. |
Action | Use the AdminConfig create command that uses four parameters. As a fourth parameter, supply one of the attribute names supplied in this message. |
Explanation | wsadmin cannot find the config object specified by an AdminConfig command. |
Action | Check to be sure that a valid config object is specified. |
Explanation | A help <argument> command has been invoked for some wsadmin object, but no help is available for the specified argument. |
Action | Verify that <argument> is a valid argument for help. Issue the "help" command again without the argument for a list of valid possibilities. |
Explanation | None |
Action | None |
Explanation | An AdminConfig parents command has failed with an unknown problem. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | An AdminConfig create or modify command has specified an attribute of some ENUM type, but the value given to the attribute is not one of the allowed values. |
Action | Specify one of the allowed values for this ENUM attribute -- the WASX7087E error message enumerates the possible values. |
Explanation | An AdminConfig create or modify command has specified an attribute of some numeric type, but the value given to the attribute is not a number. |
Action | Specify a numeric value for the attribute. |
Explanation | This is an informational message logging that this command was invoked. |
Action | None |
Explanation | This is an informational message logging that this script was invoked. |
Action | None |
Explanation | This informational message is logged instead of WASX7090I if the command appears to contain a password. |
Action | None |
Explanation | This informational message is logged when the subject message is displayed to the user. |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | This informational message is displayed in response to an AdminApp options command. The install options valid for any ear file are displayed with it. |
Action | None |
Explanation | An AdminApp command is invoked in the local mode, but wsadmin cannot determine the installation root for WebSphere. |
Action | The server.root property should be set by the wsadmin.bat or wsadmin.sh launcher. If you have modified this launcher, correct the changes. If not, contact IBM Support. |
Explanation | One or more invalid options were specified for an AdminApp or AdminConfig command. |
Action | Check the spelling of the options; correct or remove any incorrect options and reissue the command. |
Explanation | Invalid data has been specified in an AdminApp install command for the specified task. |
Action | Examine the errors reported for this task and correct the install command. |
Explanation | Incomplete data has been specified in an AdminApp install command for the specified task. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | Invalid data has been specified in an AdminApp install command for the specified task. The task consists of some number of items, but a different number has been supplied. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | =Invalid data has been specified in an AdminApp install command for the specified task. The task consists of some number of items, some of which cannot be changed. The unchangeable items consitute a key for the data, and this key must be matched exactly by the information included in an install command for this task. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | This informational message is displayed in response to an AdminApp options command. All the valid options are displayed with it. |
Action | None |
Explanation | An AdminApp taskInfo command was invoked, but the supplied task name is not valid. |
Action | Please supply a valid task name; the valid names are included in the WAS7113E message output. |
Explanation | wsadmin failed to copy an ear file to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem; perhaps there may not be enough space in the file system, or there may be file permission problems. |
Explanation | wsadmin failed to read an ear file when preparing to copy it to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem; this problem can result from an incorrect file path or a file permission problem. |
Explanation | wsadmin failed to copy an ear file to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems. |
Explanation | The user has requested that an interactive scripting session be terminated, but configuration changes have been made during the session and have not been saved. The user is being given the opportunity to commit the unsaved changes. |
Action | If you wish to exit the scripting session without saving changes, respond with "quit" or "exit." Any other response will keep the session active. You can use the AdminConfig save command to commit the unsaved changes. |
Explanation | An AdminConfig setSaveMode command was issued with an invalid mode. |
Action | Please specify a valid save mode: valid options are "overwriteOnConflict," and "rollbackOnConflict." |
Explanation | This message is written into the log file when an exception is encountered. It is followed by information extracted from the exception. |
Action | Examine the exception information in the log to try to determine the source of the problem. |
Explanation | The specified string was found when '{' was expected in the input stream. |
Action | Correct and re-issue the command. |
Explanation | The specified string was not found in the expected location in the input stream. |
Action | Correct and re-issue the command. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An AdminConfig create command was attempted, but the specified parent was of an invalid type. |
Action | Reissue the command, specifying a valid parent object for the object to be created. |
Explanation | An AdminApp install command failed. |
Action | See previous messages for details. |
Explanation | An AdminApp uninstall command failed. |
Action | See previous messages for details. |
Explanation | An AdminApp install command was invoked for a war file, but the "-contextroot" option was not supplied. |
Action | Specify a "-contextroot" option. |
Explanation | An AdminControl invoke command was issued for an MBean operation, but there is no operation defined for that MBean that accepts the same number of parameters specified in the AdminControl invoke command. |
Action | Reissue the invoke command using the correct number of parameters. The "operations" command on the Help object can be used to learn more about the signatures available for this operation. |
Explanation | An AdminControl invoke command was issued, in which a different number of parameters and signature elements were specified. There must be exactly one signature element for every parameter. |
Action | Reissue the invoke command using the correct number of signature and parameter elements, or reissue the command with no signature elements at all. |
Explanation | An AdminControl trace command was specified, but the supplied trace string is not valid. |
Action | Ensure that the trace string is spelled correctly. |
Explanation | During the processing of an AdminConfig command, a config id was found that does not correspond to an existing configuration object. |
Action | Ensure that the id is spelled correctly. |
Explanation | None |
Action | None |
Explanation | This informational message is displayed in response to the AdminConfig queryChanges command. Each file listed has been updated by the scripting client since the last save or reset command. |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An invalid value was specified for an AdminConfig command. |
Action | sSpply a valid value as indicated in the error message. |
Explanation | An informational message issued in response to invoking the AdminConfig setCrossDocumentValidationEnabled. |
Action | None |
Explanation | An informational message issued in response to invoking the AdminConfig setValidationLevel. |
Action | None |
Explanation | This informational message is written to the validation output file every time validation is requested. |
Action | None |
Explanation | This message is displayed when validation is complete. |
Action | If desired, examine the messages logged in the specified file to see if corrective action is needed. |
Explanation | This message is a summary of messages generated during configuration validation. |
Action | None |
Explanation | This message is logged to a file when validation is requested. By default, the name of the file is wsadmin.valout, located in the logs directory. |
Action | If the message indicates a configuration problem, the configuration should be fixed. |
Explanation | During wsadmin initialization, an attempt is made to open an output file for validation results. This file exists, but wsadmin cannot write to it. |
Action | Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems. |
Explanation | During wsadmin initialization, an attempt is made to open an output file for validation results. This file could not be created. |
Action | Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems. |
Explanation | This message is displayed if no connection can be obtained to the config service. |
Action | Restart wsadin so that a server connection is obtained. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | This message is displayed if no connection can be obtained to the application management service. |
Action | Restart wsadmin so that a server connection is obtained or use "-conntype NONE" option to run the local mode. |
Explanation | This is an informational message displayed when wsadmin initializes or when validation settings are changed. |
Action | None |
Explanation | This is an informational message displayed when wsadmin connects to a server during initialization. |
Action | None |
Explanation | During wsadmin initialization, an attempt is made to determine the type of server to which it is connected. This determination has failed. |
Action | Examine the wsadmin.traceout file to determine the cause of the failure. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | The wsadmin scripting client could not connect to a server using the options supplied on the command line and contained in wsadmin.properties files. |
Action | If a connection is not needed, no action is necessary -- in this case, the "-conntype NONE" option could be specified on the wsadmin command line to indicate the no connection is desired; this will suppress WASX7213I. If a connection is needed, then wsadmin must be re-started with connection information that will allow it to connect to a running server. Perhaps the host or port information is incorrect. |
Explanation | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The DataSourceCfgHelper MBean is needed to perform the testConnection function. It should be running in a server. |
Action | If the wsadmin process is not connected to a server, invoke wsadmin so that a connection is established. If wsadmin is connected, access the IBM WebSphere Application Server Support webpage for futher problem determination. |
Explanation | An AdminControl "testConnection" command was successfully executed. The database adapter code reported no errors or warnings. |
Action | None |
Explanation | There is a constraint on the specified attribute. |
Action | Specify the missing attribute. |
Explanation | The "-local" option is not permitted for AdminApp functions when the scripting client is connected to a server. |
Action | Remove the "-local" option, or invoke wsadmin using the "-conntype NONE" option to avoid being connected to a server. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | A profile has been specified for wsadmin operation. This profile is not in the same scripting language as the scripting session, so it will not be executed. |
Action | Correct the wsadmin.properties file or the wsadmin command line options so that the profile is not specified. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An AdminControl setAttribute command has been invoked for an MBean, but the attribute is not of a type supported by wsadmin's setAttribute command. |
Action | Use the setAttribute_jmx command to set this attribute. |
Explanation | An expected error has occurred during AdminConfig modify or create. |
Action | Examine the wsadmin.traceout log for more information about the failure. |
Explanation | If a scripting session begins with unsaved changes in the workspace, the workspace is reset and the unsaved changes are lost. This message is informational only. |
Action | None |
Explanation | This message issued in response to a "queryChanges" command for the AdminConfig object. It means that no changes have been made to the WebSphere configuration by this scripting process since the last "save" or "reset" AdminConfig command. |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | wsadmin initialization failed to connect to a server process because of a problem authenticating to the server. |
Action | Ensure that user and password are correct on the command line or in a properties file. |
Explanation | None |
Action | None |
Explanation | The wsadmin launcher has been invoked with the -user option, but no user name argument was found. |
Action | Reissue the wsadmin command with a user name following the -user option. |
Explanation | The wsadmin launcher has been invoked with the -password option, but no password argument was found. |
Action | Reissue the wsadmin command with a password following the -password option. |
Explanation | An AdminControl stopServer command has been issued, but a running server of the specified name cannot be found. |
Action | Ensure that the server name is spelled correctly. |
Explanation | Scripting client is connected to the wrong type of process. |
Action | Ensure that the scripting client is connected to the correct process. |
Explanation | An AdminControl startServer command has been issued, but there is no server of the specified name in the configuration. |
Action | Ensure that the server is spelled correctly. |
Explanation | During AdminControl startServer invocation, an attempt is made to locate the NodeSync object on the node where the server is to be started. This message reports that the NodeSync object cannot be located. An attempt is made to start the server. |
Action | The NodeSync object should be running; examine the logs on the node to determine why it is not. |
Explanation | An AdminControl startServer command has been issued, but there is no running NodeAgent on the server's node. |
Action | Start the NodeAgent on the appropriate machine. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | In response to an AdminControl startServer command, the specified server has been started on the specificed node. |
Action | None |
Explanation | A request has been made to start the specified server process. The scripting process will wait until the start is complete or the action times out. If it does time out, this message is issued. |
Action | Check to see that the server has indeed started before continuing. |
Explanation | In response to an AdminControl stopServer command, the specified server has been stopped on the specificed node. |
Action | None |
Explanation | A request has been made to stop the specified server process. The scripting process will wait until the stop is complete or the action times out. If it does time out, this message is issued. |
Action | Check to see that the server has indeed stopped before continuing. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | This message is generated by the installInteractive and editInteractive AdminApp commands. It is accompanied by a string that can be modified (if needed) and copied into a script for use with the install or edit commands. |
Action | None, unless the command string is needed for use in a script. |
Explanation | An AdminApp install command has been invoked for the specified application name, but this name is already being used. |
Action | Specify a different application name using the "-appname" option. |
Explanation | An AdminApp command has been invoked for the specified application, but it does not exist. |
Action | Ensure that the application name is spelled correctly. |
Explanation | An AdminApp command has been invoked for the specified file, but it cannot be used. |
Action | Ensure that this file exists and is readable. |
Explanation | An AdminApp edit or editInteractive command was invoked for the given application, but that application has no valid tasks to edit. |
Action | None; there is nothing to edit for this application. |
Explanation | An AdminConfig command has been invoked that requires an argument to be an object of a specific type, but the object is not of that type. |
Action | Invoke the command again, supplying an object of the correct type. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An AdminConfig extract command was invoked, but the specified filename describes an existing file system entity that is not a file. |
Action | The specified name is probably a directory name; reissue the extract command with a valid file name. |
Explanation | An AdminConfig extract command was invoked, but the document data cannot be written to the specified file. |
Action | Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems. |
Explanation | An AdminConfig command was invoked that requires connection to a Network Deployment Manager server, but the scripting client is not connected to such a server. |
Action | Either connect to a Network Deployment Manager server or refrain from invoking this AdminConfig command. |
Explanation | The wsadmin launcher has been invoked with the -wsadmin_classpath option, but no classpath argument was found. |
Action | Reissue the wsadmin command with a classpath following the -wsadmin_classpath option. |
Explanation | None |
Action | None |
Explanation | An AdminApp taskInfo command was invoked, but no task information can be obtained for this task from the specified ear file. |
Action | Ensure that this file exists and is readable, and that the task name is spelled correctly. |
Explanation | An AdminApp options command was invoked, but no task options can be obtained from the specified ear file. |
Action | Ensure that this file exists and is readable. |
Explanation | Options that are included on the wsadmin command line that are not recognized as valid wsadmin options are assumed to be arguments for the wsadmin scripts or commands to use. These options are available to the script in the argv variable and a count of these arguments is available in the argc variable. |
Action | If the unrecognized options were intended as arguments that are used by scripts or commands, no user action is required. If not, correct or delete the unrecognized options. |
Explanation | None |
Action | None |
Explanation | A node agent process is being started; no configuration synchronization before startup is possible since the node agent is the entity responsible for the synchronization. |
Action | None |
Explanation | An AdminControl testConnection command was invoked, but the node for the specified DataSource cannot be determined. |
Action | Ensure that the DataSource is correctly configured. |
Explanation | An invalid AdminConfig create command was invoked; this type of object can not be created. |
Action | Change the create command as appropriate. |
Explanation | A script concluded without saving configuration changes. This informational message logs the fact that the changes are lost. |
Action | Insure that AdminConfig "save" commands are executed at appropriate times. |
Explanation | None |
Action | None |
Explanation | This message signals that the scripting process is beginning to initialize the dynamic scripting objects. |
Action | None |
Explanation | This message signals that the dynamic scripting objects initialized when a scripting process begins are initialized. |
Action | None |
Explanation | A dynamic scripting object failed to initialize. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | An error occurred during the initialization of dynamic scripting objects. |
Action | Use AdminControl invoke and get/setAttribute(s) commands to interact with MBeans instead of dynamic scripting support. |
Explanation | An error has occurred during the initialization of the objects used by wsadmin. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | A server is being started by the wsadmin "startServer" command. Because no automatic configuration synchronization is performed, this message is emitted to inform the user that the configuration used by the starting server may not be the most recent configuration. |
Action | If the configuration is known to be incorrect, stop the server and invoke a configuration synchronization for this node. |
Explanation | A wsadmin AdminControl startServer command has been issued for a server that is already started. |
Action | Check to see that you have specified the correct server name. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | wsadmin failed to create a temporary directory for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems. |
Explanation | wsadmin failed to copy an expanded ear directory to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems. |
Explanation | During the initialization of a scripting process, several properties files may be loaded. This is an informational message logged so the user or service representative can tell what properties files are in use. |
Action | None |
Explanation | A listing of the was.policy security policy file associated with this application is displayed with this message. This is for informational purposes only. |
Action | None |
Explanation | The AdminConfig showAttribute command will only display the value of a single attribute, but multiple attribute names were supplied. |
Action | Correct the command so that only a single attribute name is supplied. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An interactive scripting session is ending, and the scripting process is attempting to determine if configuration changes have been made during the session. An unexpected exception has occurred during the process of making this determination. The connection to the server process may have been broken prior to stopping the scripting session. |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | In an AdminApp install command, a required option is missing. |
Action | Invoke the command again, supplying the missing option. |
Explanation | A request has been made to stop the specified server process. The scripting process will wait until the stop is complete or the action times out. In the first case, WASX7264I should be issued; in the second case, WASX7265W should be issued. |
Action | None |
Explanation | An exception occurred during the processing of an AdminControl stopServer command. |
Action | Examine the wsadmin.traceout file and the server log files to determine the source of the problem. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An interactive scripting session concluded without saving configuration changes. This informational message logs the fact that the changes are lost. |
Action | Insure that AdminConfig "save" commands are executed at appropriate times. |
Explanation | None |
Action | None |
Explanation | An AdminControl startServer command has been issued, but the node name specified is not the same as that currently connected to by the NodeAgent. |
Action | Please insure that the node name is spelled correctly. |
Explanation | An AdminControl startServer command has been issued, but the node name is not specified. |
Action | Please specify the node name to locate the server in the startServer command. |
Explanation | An AdminControl startServer command has been issued, but there is no node of the specified name in the configuration. |
Action | Ensure that the node is spelled correctly. |
Explanation | An AdminControl stopServer command has been issued, but the NodeAgent for the specified server is not located in the configuration. |
Action | Ensure that the client is connected to the appropriate process type. |
Explanation | The specified option requires an accompanying argument. For example, if you specify "-node" you need to follow "-node" with the name of a node: "-node mynode." |
Action | Supply an argument for the indicated option, or remove the option from the command line. |
Explanation | This message is the output in response to a "taskInfo" command for the AdminApp object. It details the task information requested. |
Action | None |
Explanation | None |
Action | None |
Explanation | This message is disaplyed during interactive application install when an incorrect value is entered for the resource authorization field. |
Action | Enter container or per connection factory as the value of resource authorization. |
Explanation | A "parents" command has been issued for an object type, but that type is not supported by the parents command. |
Action | None |
Explanation | The number of arguments supplied for the given command is not correct. An exception is thrown containing the help information for this command. |
Action | Please review help information and reissue the command with the correct number of arguments. |
Explanation | The convention for supplying attribute values that are collections of objects is that each object is a list of name-value pairs, and the collection of objects is a list of these objects. An example of a collection consisting of two objects would be: {{{attr1 val1a} {attr2 val2a}} {attr1 val1b} {attr2 val2b}}}. |
Action | Correct the syntax of the command so that the attribute is notated as a collection. |
Explanation | The convention for supplying attribute values that are embedded objects is that the object is a list of name-value pairs. An example of an embedded object consisting of three attributes would be: {{attr1 val1a} {attr2 val2a}}. |
Action | Correct the syntax of the command so that the embedded object is notated as a list of name-value pairs. |
Explanation | The value supplied for the attribute is not valid. |
Action | Correct the syntax of the command so that attribute is notated correctly. |
Explanation | The argument to the startServer command is not valid. |
Action | Reissue the command with the correct value for the argument. |
Explanation | A request has been made with "-conntype NONE" option in the command line or specified in com.ws.scripting.connectionType property with NONE as the value in wsadmin.properties to not to connect to a running server. This is just informational purpose only. |
Action | None |
Explanation | One or more invalid options were specified for an AdminApp command. |
Action | Check the spelling of the options; correct or remove any incorrect options and reissue the command. |
Explanation | AdminApp install/installInteractive has been invoked with the -reloadInterval option, but the value following this option is not an integer. |
Action | Reissue the AdminApp command with an integer argument for the -reloadInterval option. |
Explanation | None |
Action | None |
Explanation | AdminConfig required command returns no required attribute for the specified type. |
Action | None |
Explanation | None |
Action | None |
Explanation | Help message command can not locate any message information for the specified message id. |
Action | If the specified message id is incorrect, then invoke the Help message command with the correct message id. |
Explanation | The directory containing the help information does not exist. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | The bean provider specified in the extension xml cannot be registered with BSF. |
Action | Understand what the exception is included in the trace log and correct the problem accordingly. If the problem persists, contact IBM support. |
Explanation | The implementation class provided in the extension xml is not found. |
Action | Correct the implementation class in the extension xml if there is a typo in the class or make sure the class is in the classpath. |
Explanation | The implementation class provided in the extension xml can not be instantiated. |
Action | Understand what the exception is included in the trace log and correct the problem accordingly. Make sure the class provided a constructor with no argument. |
Explanation | The same implementation class is included in the extension xml more than once. |
Action | Remove the duplicate implementation class in the extension xml. |
Explanation | The extension xml contains element type reported in the warning message with required element type missing. |
Action | Add the missing element type reported in the message to the extension xml. |
Explanation | The same element type is used more than once in the extension xml. |
Action | Remove the extra element type in the extension xml. |
Explanation | The reported element tag in the extension xml is not supported. |
Action | Remove the unsupported element tag in the extension xml. |
Explanation | A type handler registerd to handle the same type class is included in the extension xml more than once. |
Action | Remove the duplicate type handler in the extension xml. |
Explanation | none |
Action | none |
Explanation | An unsupported scripting language was specified. |
Action | Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | none |
Action | none |
Explanation | testConnection command is supported in server with version 5.1 and up. |
Action | use testConnectionToDataSource method in DataSourceCfgHelper MBean to test connection of DataSource resided in 5.0 server. |
Explanation | See previous messages for details. |
Action | See previous messages for details. |
Explanation | This command is not supported. |
Action | Do not use this command. |
Explanation | This command is not supported. |
Action | Do not use this command. |
Explanation | WebSphere Application Server attempts to prevent applications from performing security-sensitive operations, like calling the System.exit() method, replacing the Java 2 Security manager, and replacing the Java 2 Security policy. If the application is granted the all permission ( java.security.AllPermission), the Java 2 Security permission checks are effectively disabled, which can compromise the integrity of the system. |
Action | Review the application policy, which is located in the EAR/META-INF/was.policy file, remove the security-sensitive permissions and grant the application only the permissions that are required. |
Explanation | WebSphere Application Server attempts to prevent applications from performing security-sensitive operations, like calling the System.exit() method, replacing the Java 2 Security manager, and replacing the Java 2 Security policy. If the application is granted the all permission ( java.security.AllPermission), the Java 2 Security permission checks are effectively disabled, which can compromise the integrity of the system. |
Action | Review the application policy, which is located in the EAR/META-INF/was.policy file, remove the security-sensitive permissions and grant the application only the permissions that are required. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | Both -lang and -internalLang options are specified. However, their values are not the same. |
Action | Specify either -lang or -internalLang option. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | There are still applications using the resource adapter specified in the uninstallResourceAdapter command. |
Action | Uninstall the applications listed in the error message before uninstall the resource adapter. If you want to force this uninstall action without uninstalling applications first, specify the -force option with uninstallResourceAdapter command. |
Explanation | There are still other J2CResourceAdapter objects using the resource adapter specified in the uninstallResourceAdapter command. |
Action | Uninstall the resource adapters listed in the error message before attempting to uninstall the specified resource adapter. If you want to force this uninstall action without uninstalling the other resource adapters first, use the -force option with uninstallResourceAdapter command. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | An AdminApp view command was invoked for the given application, but that application has no valid tasks to view. |
Action | None; there is nothing to edit for this application. |
Explanation | An AdminApp view command was invoked for the given application, but that application has invalid tasks to view. |
Action | None; Please give the correct task with the correct spelling. To find out the list of valid task names, use the -tasknames option. |
Explanation | Removing Node from the configuration will corrupt your configuration. |
Action | If you have not commit the change, you can still perform "AdminConfig reset" command to restore the configuration to its initial state. |
Explanation | Removing Node from configuration require some manual steps. It is not recommended operation, it is better to use removeNode utility script instead. |
Action | If you have not commit the change, you can still perform "AdminConfig reset" command to restore the configuration to its initial state. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | There are unrecognized options specified in the AdminApp command. |
Action | Check the options provided in the message. Rerun the AdminApp command if the options contain typo. Otherwise, no further action is required. |
Explanation | The value for the content type parameter is incorrect. Valid values for this parameter are add, addupdate, delete, and update. |
Action | Rerun update command with the correct content type value. |
Explanation | The value for the operation option is incorrect. Valid values for this parameter are app, file, modulefile, and partialapp. |
Action | Rerun update command with the correct operation value. |
Explanation | The option mentioned in the message does not have to be provided if the specified content type is provided in the update command. |
Action | None |
Explanation | The option mentioned in the message does not have to be provided if the specified operation is provided in the update command. |
Action | None |
Explanation | The missing option is a required option when the specified content type is provided in the update command. |
Action | Rerun the update command providing the missing option. |
Explanation | The missing option is a required option if the specified content type and operation are provided in the update command. |
Action | Rerun the update command providing the missing option. |
Explanation | An AdminApp update command failed. |
Action | See previous messages for details. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | contextroot option is specified with the update command using modulefile content type and update or addupdate operation. |
Action | For update operation with modulefile as the content type, contextroot option will be ignored. For addupdate operation with modulefile as the content type, contextroot option will be ignored if module exists. No further action is required. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | There are deprecated options specified in the AdminApp command. |
Action | The options listed in the warning message are deprecated. The support for these options will be removed eventually. If there is replacement option for the deprecated option, you should start using the replacement option. If there is no replacement option, then your command should work fine without the deprecated option. |
Explanation | A string value representing a boolean is not entered as true or false. |
Action | If there is typo in the string value representing a boolean, then rerun the command with the correct string value. Otherwise, no further action is required. |
Explanation | To use any default binding option, you must also specify the usedefaultbindings option. |
Action | Provide the usedefaultbindings option in the option string with the AdminApp install, installInteractive, update, or updateInteractive command. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | None |
Action | None |
Explanation | Scripting client is connected to local mode. |
Action | Ensure that the scripting client is connected to a server and ensure that the server is running. |
Explanation | The terminate flag can only be used to stop servers of type Managed Process |
Action | Ensure that the server being stopped is a Managed Process. |
Explanation | Node name should be provided as one of the arguments. |
Action | Ensure that arguments include the node name the server is on. |
Explanation | A request has been made to stop the specified server process. The scripting process will not wait till the request succeeds. |
Action | Check to see that the server has indeed stopped before continuing. |
Explanation | None |
Action | None |
Explanation | Command name is not registered as one of the available admin commands. |
Action | Correct the command name |
Explanation | Wrong number of arguments, invalid command, or invalid command group name is entered with AdminTask help command |
Action | Use AdminTask help command to contain a list of valid commands to perform help operation on. |
Explanation | none |
Action | none |
Explanation | none |
Action | none |
Explanation | none |
Action | none |
Explanation | none |
Action | none |
Explanation | none |
Action | none |
Explanation | Admin command does not contain the specified parameter. |
Action | Check that there is no typo in the parameter name or use help command to get detailed help for the command. |
Explanation | The specified language is not supported. Supported scripting languages are Jacl and Jython. |
Action | Provide either Jacl and Jython as the scripting language. |
Explanation | This message is logged when wsadmin is initialized and the wsadmin process cannot cconnect to a server. |
Action | Reissue the wsadmin command so that a server connection is made. |
Explanation | You have specified to modify the data in the specified step which is not enabled for the task. |
Action | Reissue the AdminTask command without the step option indicated in the error message. |
Explanation | none |
Action | none |
Explanation | You have specified more than one set of data value to the specified step which is not a table. |
Action | Reissue the AdminTask command providing only one set of data value to the step indicated in the error message. |
Explanation | Option value provided to the specified step is not valid. |
Action | Reissue the AdminTask command with the correct option value for step. |
Explanation | Admin command contains an internal error. |
Action | Contact the command provider to resolve this problem. |
Explanation | Admin command contains an internal error. |
Action | Contact the command provider to resolve this problem. |
Explanation | Option values provided to the specified step does not matching the existing data. |
Action | Reissue the AdminTask command with the correct option values for step. |
Explanation | Option values provided to the specified step does not have enough fields. |
Action | Reissue the AdminTask command with the correct option values for step. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | The specified character was found in an unexpected location in the input stream. |
Action | Correct and re-issue the command. |
Explanation | This message is issued when an UnsupportedOperationException is received from an MBean, probably as the result of an AdminControl invoke command. |
Action | Check the spelling of the operation attempted. |
Explanation | This message is issued when a RuntimeMBeanException is received from an MBean. |
Action | Examine the exception information and modify the the failing command, as appropriate. |