Express (Distributed operating systems), v8.0 > Reference > Messages
CWUDD
CWUDD0001I: Attempting to deploy UDDI Registry application.
Explanation The UDDI deployment process is starting. Action No action is required.
CWUDD0002W: Failed to discard unsaved changes caught exception Exc. Value is:
Explanation This message warns that changes made in the wsadmin session before the uddiDeploy.jacl script was run cannot be discarded, and shows the error that occurred. Action No action is required.
CWUDD0003I: Application Manager found.
Explanation An active Application Manager can be used to stop and start UDDI on the deployment server. Action No action is required.
CWUDD0004I: Application Manager unavailable, application will not be started/stopped.
Explanation No active Application Manager can be found, so there is no need to stop and start UDDI on the deployment server. Action No action is required.
CWUDD0005I: ApplicationManager not running, application will not be started/stopped.
Explanation An Application Manager has been found, but it is not running, so there is no need to stop and start UDDI on the deployment server. Action No action is required.
CWUDD0006I: Checking for installed UDDI Registry application of name appname. Value is:
Explanation The deployment script is checking for deployed UDDI applications. Action No action is required.
CWUDD0007I: Stopping application of name appname. Value is:
Explanation There is an attempt to stop a deployed UDDI application. Action No action is required.
CWUDD0008W: Stopping application appname caught exception Exc. Application might not have been running on this server. Values are:
Explanation The UDDI application stop request failed. Action Attempt to stop the UDDI application using the Administrative Console and rerun the uddiDeploy.jacl script.
CWUDD0009I: Application appname stopped successfully. Value is:
Explanation The UDDI application has stopped running. Action No action is required.
CWUDD0010I: Removing application appname. Value is:
Explanation The deployment script is attempting to remove an existing UDDI application. Action No action is required.
CWUDD0011I: Application appname removed successfully. Value is:
Explanation The UDDI application has been removed from the configuration. Action No action is required.
CWUDD0012I: Attempting to create default UDDI datasource.
Explanation A default UDDI deployment has been requested and therefore a Derby data source will be created. Action No action is required.
CWUDD0013I: Multiple Derby JDBC Providers found. Using first in list.
Explanation The deployment script has detected a number of suitable Derby JDBC providers and will use the first one. Action No action is required.
CWUDD0014I: UDDI Datasource name successfully created. Value is:
Explanation A Derby data source has been created for the default UDDI deployment. Action No action is required.
CWUDD0015I: Setting application classloader mode.
Explanation The UDDI application requires the class loading mode to be PARENT_LAST. Action No action is required.
CWUDD0016I: Altered classloader mode of application appname from oldmode to newmode. Values are:
Explanation The UDDI application class loader mode has been successfully changed. Action No action is required.
CWUDD0017I: Setting classloader mode for application modules.
Explanation The UDDI application web modules require PARENT_LAST class loading. Action No action is required.
CWUDD0018I: Altered classloader mode of module modname in application appname from oldmode to newmode. Values are:
Explanation The UDDI Web modules class loader mode has been successfully changed. Action No action is required.
CWUDD0019I: UDDI successfully deployed.
Explanation This message is for informational purposes only. Action No action is required.
CWUDD0020I: Attempting to save new configuration.
Explanation There is an attempt to save the configuration after removing any existing UDDI application. Action No action is required.
CWUDD0021I: Changes saved successfully.
Explanation There is an attempt to save the configuration after removing any existing UDDI application. Action No action is required.
CWUDD0022I: Attempting to save new configuration.
Explanation There is an attempt to save the configuration after installing the UDDI application ear. Action No action is required.
CWUDD0023I: Changes saved successfully.
Explanation The configuration changes have been successfully saved. Action No action is required.
CWUDD0024I: Attempting to save new configuration.
Explanation There is an attempt to save the configuration after changing the class loader modes. Action No action is required.
CWUDD0025I: Changes saved successfully.
Explanation The configuration changes have been successfully saved. Action No action is required.
CWUDD1001W: Failed to discard unsaved changes caught exception Exc. Value is:
Explanation This message warns that changes made in the wsadmin session before the uddiDeploy.jacl script was run cannot be discarded, and shows the error that occurred. Action No action is required.
CWUDD1002I: Application Manager found.
Explanation An active Application Manager can be used to stop and start UDDI on the deployment server. Action No action is required.
CWUDD1003I: Application Manager unavailable, application will not be started/stopped.
Explanation No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server. Action No action is required.
CWUDD1004I: ApplicationManager not running, application will not be started/stopped.
Explanation An Application Manager has been found, but it is not running, so there is no need to stop and start UDDI on the deployment server. Action No action is required.
CWUDD1005I: Stopping application of name appname. Value is:
Explanation There is an attempt to stop a deployed UDDI application. Action No action is required.
CWUDD1006W: Stopping application appname caught exception Exc. Application might not have been running on this server. Values are:
Explanation The request to stop the UDDI application failed. Action Attempt to stop the UDDI application using the Administrative Console and rerun the uddiDeploy.jacl script.
CWUDD1007I: Application appname stopped successfully. Value is:
Explanation The UDDI application has stopped running. Action No action is required.
CWUDD1008I: Removing application appname. Value is:
Explanation The removal script is attempting to remove the UDDI application. Action No action is required.
CWUDD1009I: Attempting to remove UDDI Registry application.
Explanation The UDDI removal process is starting. Action No action is required.
CWUDD1010I: Application appname removed successfully. Value is:
Explanation The UDDI application has been removed from the configuration. Action No action is required.
CWUDD1011I: Attempting to remove the default UDDI datasource.
Explanation A default UDDI removal has been requested and therefore the Derby data source used for UDDI will be removed. Action No action is required.
CWUDD1012I: UDDI Datasource name successfully removed. Value is:
Explanation The UDDI Derby data source has been removed from the configuration. Action No action is required.
CWUDD1013I: UDDI Datasource name does not exist. No action required. Value is:
Explanation The default UDDI Derby data source does not exist in this configuration and therefore does not need to be removed. Action No action is required.
CWUDD1014I: UDDI Registry application and default UDDI datasource removed successfully.
Explanation UDDI has been successfully removed from the configuration. Action No action is required.
CWUDD1015I: Attempting to save new configuration.
Explanation There is an attempt to save the configuration after removing the UDDI application. Action No action is required.
CWUDD1016I: Changes saved successfully.
Explanation The configuration changes have been successfully saved. Action No action is required.
CWUDD1017I: UDDI Registry application removed successfully.
Explanation UDDI has been successfully removed from the configuration. Action No action is required.
CWUDD1018W: Application appname is not installed. Value is:
Explanation The UDDI application has not been deployed and therefore the application cannot be removed. Action No action is required.
CWUDD6001E: Incorrect number of arguments passed to script.
Explanation The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. Action Retry the script with the correct arguments.
CWUDD6002E: Usage is:
Explanation The deployment script has not been called with the correct arguments. Action Retry the script with the correct arguments
CWUDD6003E: Failed to determine server ID caught exception Exc. Value is:
Explanation An exception occurred while trying to determine the Server ID. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6004E: Failed to determine server ID, possibly due to invalid nodename or servername (check case).
Explanation The server ID could not be located for the given node name and server name. Action Check that the node name and server name are correct and are in the correct case.
CWUDD6005E: Failed to determine the list of JDBC providers caught exception Exc. Value is:
Explanation The deployment script was unable to determine the list of JDBC providers. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6006E: Failed to get JDBC provider name from id caught exception Exc. Value is:
Explanation An exception occurred while trying to determine the list of JDBC providers for the server. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6007E: Attempt to create a Derby JDBC provider caught exception Exc. Value is:
Explanation A Derby JDBC provider is required for the default deployment of UDDI and an exception occurred while trying to create this JDBC provider. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6008E: Failed to create datasource caught exception Exc. Value is:
Explanation An exception occurred while trying to create the UDDI Derby data source. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6009E: Failed to create resource property set caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property set. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6010E: Failed to create 'databaseName' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'databaseName'. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6011E: Failed to create 'shutdownDatabase' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'shutdownDatabase'. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6012E: Failed to create 'dataSourceName' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'dataSourceName'. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6013E: Failed to create 'description' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'description'. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6014E: Failed to create 'connectionAttributes' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'connectionAttributes' Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6015E: Failed to create 'createDatabase' resource property caught exception Exc. Value is:
Explanation An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'createDatabase' Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6016E: Attempt to locate the WebSphere Installation Directory failed.
Explanation The installation directory of Application Server could not be determined. Action Verify that the Application Server has been correctly installed and that the WAS_INSTALL_ROOT environment variable exists in the configuration.
CWUDD6017E: Uninstall of application appname caught exception Exc. Values are:
Explanation An exception occurred while trying to uninstall an existing UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6018E: Install of UDDI application caught exception Exc. Value is:
Explanation An exception occurred while trying to install the UDDI application, probably during the installation of the UDDI application into the application server, but possibly at another stage during the deployment of UDDI. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6019E: Attempt to find application classloader failed with exception Exc. Value is:
Explanation An exception occurred while trying to locate the classloader for the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6020E: Attempt to read current classloader mode failed with exception Exc. Value is:
Explanation An exception occurred while trying to determine the classloader mode of the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6021E: Attempt to modify classloader mode to newmode failed with exception Exc. Values are:
Explanation An exception occurred while trying to change the classloader mode of the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6022E: Attempt to read new classloader mode failed with exception Exc. Value is:
Explanation An exception occurred while trying to verify the new classloader mode of the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6023E: Attempt to read module list from application failed with exception Exc. Value is:
Explanation An exception occurred while trying to determine the list of modules held in the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6024E: Attempt to locate URI attribute on module failed with exception Exc. Value is:
Explanation An exception occurred while trying to determine the URI attribute of the application module. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6025E: Attempt to read current classloader mode from module failed with exception Exc. Value is:
Explanation An exception occurred while trying to determine the classloader mode of a UDDI module. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6026E: Attempt to modify module classloader mode to newmode failed with exception Exc. Values are:
Explanation An exception occurred while trying to change the classloader mode of a UDDI module. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6027E: Attempt to read new module classloader mode failed with exception Exc. Value is:
Explanation An exception occurred while trying to verify the new classloader mode of a UDDI module. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6028E: Attempt to create the default UDDI Registry Derby database failed with exception Exc. Value is:
Explanation An exception occurred while trying to create the default Derby database. Action Refer to the accompanying messages to determine the cause.
CWUDD6029E: Attempt to locate the Nodes Variable Map failed with exception Exc. Value is:
Explanation An exception occurred while trying to locate the configurations Variable Map for the given node. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6030E: Error saving configuration, changes not saved due to exception Exc. Value is:
Explanation An exception occurred while trying to save the configuration after creating a default data source and removing an existing UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6031E: Error saving configuration, changes not saved due to exception Exc. Value is:
Explanation An exception occurred while trying to save the configuration after installing the UDDI application. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6032E: Error saving configuration, changes not saved due to exception Exc. Value is:
Explanation An exception occurred while trying to save the final configuration. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6033E: Incorrect argument passed to script.
Explanation The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. Action Retry the script with the correct arguments.
CWUDD6034E: 'default' keyword is not allowed in a WAS Network Deployment configuration.
Explanation A default Derby UDDI registry is not permitted in a WAS Network Deployment configuration. Follow the UDDI installation instructions about how to create a non-default UDDI registry database. Action Retry the script with the correct arguments.
CWUDD6035E: Cluster names are only allowed in a WAS Network Deployment configuration.
Explanation UDDI can be deployed to a cluster only in a Network Deployment configuration. Action Deploy UDDI using the arguments node name and server name.
CWUDD6036E: Failed to determine cluster ID caught exception Exc. Value is:
Explanation An exception occurred while trying to determine the cluster ID. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD6037E: Failed to determine cluster ID, possibly due to invalid clusterName (check case).
Explanation The cluster ID could not be located for the given cluster name. Action Check the cluster name is correct and is in the correct case.
CWUDD7001E: Incorrect number of arguments passed to script.
Explanation The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. Action Retry the script with the correct arguments.
CWUDD7002E: Usage is:
Explanation The removal script has not been called with the correct arguments. Action Retry the script with the correct arguments
CWUDD7003E: Failed to determine server ID caught exception Exc. Value is:
Explanation An exception occurred while trying to determine the Server ID. Action Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD7004E: Failed to determine server ID, possibly due to invalid nodename or servername (check case).
Explanation The Server ID could not be located for the given node name or server name. Action Check that the node name or server name are correct and are in the correct case.
CWUDD7005E: Uninstall of application appname caught exception Exc. Values are:
Explanation An exception occurred while trying to uninstall the UDDI application. Action Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD7006E: Failed to remove default UDDI datasource caught exception Exc. Value is:
Explanation An exception occurred while trying to remove the UDDI Derby data source. Action Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD7007E: Error saving configuration, changes not saved due to exception Exc. Value is:
Explanation An exception occurred while trying to save the final configuration. Action Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD7008E: Incorrect argument passed to script.
Explanation The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. Action Retry the script with the correct arguments.
CWUDD7009E: 'default' keyword is not allowed in a WAS Network Deployment configuration.
Explanation A default Derby UDDI Registry is not permitted in a WAS Network Deployment configuration. Therefore there is no default Derby UDDI data source to remove. Action Retry the script with the correct arguments.
CWUDD7010E: Cluster names are only allowed in a WAS Network Deployment configuration.
Explanation UDDI can only be removed from a cluster in a Network Deployment configuration. Action Remove UDDI using the arguments node name and server name.
CWUDD7011E: Failed to determine cluster ID caught exception Exc. Value is:
Explanation An exception occurred while trying to determine the cluster ID. Action Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause.
CWUDD7012E: Failed to determine cluster ID, possibly due to invalid clusterName (check case).
Explanation The cluster ID could not be located for the given cluster name. Action Check the cluster name is correct and is in the correct case.