Express (Distributed operating systems), v8.0 > Reference > Messages
CWUDS / CWUDG / CWUDQ/ CWUDN / CWUDT / CWUDM
CWUDG0001I: {0} starting initialization.
Explanation The user console control servlet is starting. Action No action is required.
CWUDG0002I: {0} finished initialization.
Explanation The user console control servlet has completed startup successfully. Action No action is required.
CWUDG0003I: Reading init parameters.
Explanation The user console control servlet has started reading external parameters during initialization. Action No action is required.
CWUDG0004I: Finished reading init parameters.
Explanation The user console control servlet has finished reading external parameters during initialization. The user console is ready to accept client requests. Action No action is required.
CWUDG0005E: A serious error has occurred. error message: <{0}> error: {1} More information: {2}
Explanation An unexpected error has occurred. Examine the error message, error type, and additional information to help to resolve the problem. Action More info at:
CWUDG0006E: A persistence error has occurred. error message: <{0}> error: {1} More information: {2}
Explanation An error occurred while performing a database operation. Examine the error message, error type, and additional information to help to resolve the problem. Action Check the database connections.
CWUDG0007E: A User mismatch error has occurred. error message: <{0}> error: {1} More information: {2}
Explanation The user id provided does not match the user id required or expected while performing an operation that requires authentication. Examine the error message, error type, and additional information to help to resolve the problem. Action Check that the user has authority for the operation that was requested.
CWUDG0008E: An invalid key was passed. error message: <{0}> error: {1} More information: {2}
Explanation The requested operation is trying to retrieve information about an entity with a key that is not valid. This might occur if the entity has been deleted by another session. Examine the error message, error type, and additional information to help to resolve the problem. Action Ask the client to close existing sessions and attempt the operation in a new browser session.
CWUDG0009E: An invalid value was supplied. error message: <{0}> error: {1} More information: {2}
Explanation A value that was passed to an API call was not valid. Examine the error message, error type, and additional information to help to resolve the problem. Action More info at:
CWUDG0010E: Failed to introspect ActionForm fields. Exception: {0}
Explanation The contents of a form object cannot be checked for characters that are not valid. Action More info at:
CWUDG0011E: Failed to invoke reflected methods in ActionForm. Exception: {0}
Explanation The contents of a form object cannot be checked for characters that are not valid. Action More info at:
CWUDG0012E: User console initialisation failed to connect to UDDI database. Exception: {0}
Explanation During user console initialization, connection to the database failed, and threw the exception specified. Action Check the connection to the UDDI database. Examine the exception message to help to resolve the problem.
CWUDG0013E: User console initialisation failed to initialize tModels. Exception: {0}
Explanation An error has occurred during initialization of ActionServlet, specifically when reading tModels (invoking the init method in class TModelNames). Action Check the state of the UDDI database. Check that the TMODEL table is populated with valid data. Examine the exception message to help resolve the problem.
CWUDG0014E: User console initialization failed to initialize taxonomies. Exception: {0}
Explanation An error has occurred during initialization of ActionServlet, specifically when reading taxonomy data (invoking the init method of CategoryTaxonomyTree). Action Check the state of the UDDI database. Examine the exception message to help to resolve the problem.
CWUDM0001E: An unexpected error occurred performing the administrative operation: {0}. Exception: {1}.
Explanation An internal error occurred during the specified administrative operation. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0002E: MBean transaction failed. Commit flag was: {0}
Explanation The current transaction did not commit or roll back. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0003E: MBean transaction did not begin.
Explanation An error occurred trying to start a transaction. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0004E: MBean transaction connection failed to release.
Explanation A connection was not released after a transaction was committed or rolled back. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0005E: MBean could not establish control with persistence manager.
Explanation The UDDI administrative function cannot connect to the UDDI registry database. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0006E: MBean could not acquire connection for UDDI datasource.
Explanation The UDDI administrative function cannot connect to the UDDI registry database. Action Check the configuration of the data source.
CWUDM0007E: UddiNode MBean with ObjectName {0} could not be unregistered.
Explanation The UddiNode MBean for the UDDI application could not be unregistered from the MBeanServer. Action Restart the UDDI application or the application server.
CWUDM0008W: MBean notfication for event {0} failed.
Explanation The UDDI administrative function did not complete successfully. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0009W: A UddiNode MBean is already registered.
Explanation There is a UddiNode MBean registered in the same cell, node, and server. Action Ensure that there is only one UDDI application deployed in the server.
CWUDM0020E: Unable to retrieve UDDI node ID.
Explanation A database error occurred. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0021E: Unable to retrieve UDDI node state.
Explanation A database error occurred. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0022E: Unable to retrieve UDDI node application name.
Explanation A database error occurred. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0023E: Unable to retrieve UDDI node description.
Explanation A database error occurred. Action Check the connection to the UDDI database and the installation configuration of the UDDI application.
CWUDM0024E: Unable to activate UDDI node.
Explanation An error occurred trying to activate the UDDI node. Action Check the running state of the UDDI application. Restart the application if necessary.
CWUDM0025I: Unable to activate a UDDI node that is not initialized.
Explanation The UDDI node must be initialized, and in deactivated state, before it can be activated. Action If the UDDI node is ready to be initialized, start the initialization operation.
CWUDM0026E: Unable to deactivate UDDI node.
Explanation An error occurred trying to deactivate the UDDI node. Action Check the running state of the UDDI application. Restart the application if necessary.
CWUDM0027I: Unable to deactivate UDDI node that is not initialized.
Explanation The UDDI node must be initialized, and activated, before it can be deactivated. Action If the UDDI node is ready to be initialized, start the initialization operation.
CWUDM0028E: Unable to initialize UDDI node.
Explanation An error occurred during initialization of the UDDI node. Action Check the installation and data source settings of the UDDI application.
CWUDM0029I: Unable to initialize UDDI node because a required property is missing or invalid: {0}.
Explanation A configuration property that is required for UDDI node initialization has not been supplied. Action Supply a value for the required property.
CWUDM0030I: Initialize operation did not occur because the UDDI node is already initialized.
Explanation A UDDI node can be initialized only once. Action No action is required.
CWUDM0031I: Initialize operation did not occur because the UDDI node is in default configuration and is already initialized.
Explanation A UDDI node can be initialized only once. Action No action is required.
CWUDM0051E: Unable to create UDDI publisher with user name {0}.
Explanation An error occurred trying to register the UDDI publisher. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0053E: Unable to delete UDDI publisher with user name {0}.
Explanation An error occurred trying to register the UDDI publisher. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0056E: Unable to update UDDI publisher with user name {0}.
Explanation An error occurred trying to update the UDDI publisher. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0059E: Unable to retrieve information for UDDI publisher with user name {0}.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0060E: Unable to retrieve collection of UDDI publishers.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0061E: Unable to get tier assigned to UDDI publisher with user name {0}.
Explanation The UDDI publisher with the specified user name might not exist, or a database error might have occurred when performing the operation described in the message. Action Check that the UDDI publisher exists. If it does, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0062E: Unable to create UDDI publishers with user names: {0}.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0070E: Unable to create tier with ID: {0}.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0071E: Unable to delete tier with ID: {0}.
Explanation The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message. Action Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0072E: Unable to retrieve information for tier with ID: {0}.
Explanation The supplied tier ID might not be an integer, the tier with the ID might not exist, or of a database error might have occurred performing the operation described in the message. Action Check the tier ID is an integer and the tier exists. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0073E: Unable to retrieve collection of tiers.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0074E: Unable to set default tier to tier ID: {0}.
Explanation The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message. Action Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0075E: Unable to update tier with ID: {0}.
Explanation The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message. Action Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0076E: Unable to get count of UDDI publishers for tier ID: {0}.
Explanation The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message. Action Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0077E: Unable to retrieve collection of entitlements.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0078E: Unable to retrieve collection of limits.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0079I: The default tier cannot be deleted.
Explanation When auto-registration of UDDI publishers is enabled, a tier that is designated as the tier assigned to UDDI publishers must always exist. Action No action is required.
CWUDM0100E: Unable to get configuration property information for property with ID: {0}.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0102E: Unable to retrieve collection of configuration properties.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0103E: Unable to update configuration properties.
Explanation This might occur if an updated property object cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0104E: Unable to update configuration property with ID: {0}.
Explanation This might occur if the updated property object shown in the message cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0107E: Failed to retrieve required properties from database.
Explanation A database error occurred when trying to initialize a UDDI node. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0120E: Unable to get policy information for policy with ID: {0}.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0122E: Unable to get policy group with group ID: {0}
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0123E: Unable to retrieve collection of policy groups.
Explanation A database error occurred performing the operation described in the message. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0124E: Unable to update policies.
Explanation This might occur if an updated policy object cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message. Action Ensure all policy IDs and values are valid. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0125E: Unable to update policy with ID: {0}.
Explanation This might occur if the updated policy object shown in the message cannot be validated, or its ID is not recognized. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message. Action Check the policy ID and value are valid. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0140E: Unable to change value set tModelKey from {0} to {1}.
Explanation The policy with the specified ID does not exist. Action Use a valid policy ID. We can find these in the PolicyConstants interface information.
CWUDM0141E: Unable to retrieve value set details for tModel key: {0}.
Explanation A database error occurred getting the value set details. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0142E: Unable to get value set property: {1} for value set with tModel key: {0}.
Explanation The value set property ID or tModel key supplied was not recognized. Action Supply a valid value set property ID and tModel key.
CWUDM0143E: Unable to retrieve value sets collection.
Explanation A database error might have occurred. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0144E: Unable to determine if value set with tModel key: {0} exists.
Explanation The tModel key supplied is not valid or a database error might have occurred. Action Ensure that the tModel exists. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0145E: Unable to load value set data for value set with tModel key: {0} and file name: {1}.
Explanation The tModel key is not recognized, the file doesn't contain valid value set data, or a database error occurred. Action Ensure that the tModel exists and the value set data object is populated. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0146E: Unable to load value set data for value set with tModel key: {0}.
Explanation The tModel key is not recognized or a database error occurred. Action Ensure that the tModel exists and the value set data object is populated. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0147E: Could not update value set status with tModel key: {0}.
Explanation The value set status object supplied is null or the tModel key is not known. Action Supply a valid value set status object with tModel key for a value set tModel that exists. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0148E: Could not update value set status with tModel key: {0}, property: {1}.
Explanation A database error occurred when updating the supported status of the value set status. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0149E: Could not update value set status with tModel key: {0}.
Explanation One of the supplied value set status objects contained a tModel key that was not recognized. Action Supply tModel keys for value set tModels that exist. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0150E: Could not update value set status with tModel key: {0}, property: {1}.
Explanation A database error occurred when updating the supported status of one of the value set status objects. Action Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0151E: Unable to unload value set data with tModel key: {0}.
Explanation The tModel key is not recognized or a database error occurred. Action Ensure that the tModel exists. Check the configuration of the UDDI application and the connection to the UDDI database.
CWUDM0170W: Loading of configuration file {0} failed.
Explanation The Digester configuration file could not be loaded. Action Check the configuration of the UDDI application.
CWUDM0171W: Parsing of configuration file {0} failed.
Explanation The Digester configuration file is not in the correct format. Action Check the configuration of the UDDI application.
CWUDM0172W: An unexpected date format was found while parsing configuration file.
Explanation A date format in the configuration file is not correct. Action Check the configuration of the UDDI application.
CWUDM0180I: UDDI node was activated.
Explanation The UDDI node is ready to accept UDDI Application Programming Interface requests. Action No action is required.
CWUDM0181I: UDDI node was deactivated.
Explanation The UDDI node is not ready to accept UDDI Application Programming Interface requests. This might occur when administrative tasks are updating configuration settings. Action No action is required.
CWUDM0182I: UDDI node initialized successfully.
Explanation The UDDI node is ready to accept UDDI Application Programming Interface requests. Action No action is required.
CWUDM0183I: UDDI publisher {0} was created.
Explanation A new UDDI publisher has been created. Action No action is required.
CWUDM0184I: UDDI publisher {0} was updated.
Explanation A UDDI publisher has been updated. Action No action is required.
CWUDM0185I: UDDI publisher {0} was deleted.
Explanation A UDDI publisher has been deleted. Action No action is required.
CWUDM0186I: Tier {0} was created.
Explanation A new UDDI tier has been created. Action No action is required.
CWUDM0187I: Tier {0} was updated.
Explanation A UDDI tier has been updated. Action No action is required.
CWUDM0188I: Tier {0} was deleted.
Explanation A UDDI tier has been deleted. Action No action is required.
CWUDM0189I: Configuration property {0} was updated to value {1}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0190I: Policy {0} was updated to value {1}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0191I: Default tier was set to {0}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0192I: Loaded value set for tModel key {0} from file {1}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0193I: Loaded value set for tModel key {0}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0194I: Unloaded value set for tModel key {0}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0195I: Updated value set supported status for tModel key {0} to {1}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDM0196I: Changed tModel key for value set from {0} to {1}.
Explanation The administrative operation described in the message completed successfully. Action No action is required.
CWUDN0001I: UDDI Node State change, new state: {0}
Explanation The UDDI registry node has changed to the new state shown in the message. Action No action is required.
CWUDN0002E: Error, invalid Node State requested: {0}
Explanation The UDDI registry node was requested to change to a state that is not valid. Action No action is required.
CWUDN0003I: {0}
Explanation The UDDI registry node configuration is successfully made persistent. Action No action is required.
CWUDN0004E: Error, NodeManager initialization failed getting PersisterControl.
Explanation The UDDI node manager could not access the UDDI database. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0005E: Error, NodeManager initialization UDDIFatalErrorException.
Explanation An exception occurred during initialization of the UDDI node manager. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0006E: Error, NodeManager initialization UDDIException.
Explanation An exception occurred during initialization of the UDDI node manager. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0007E: Error, NodeManager initialization Exception.
Explanation An exception occurred during initialization of the UDDI node manager. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0008E: Error, NodeManager initialization Throwable.
Explanation An exception occurred during initialization of the UDDI node manager. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0009E: Error, NodeManager initialization rollback Exception.
Explanation An exception occurred during initialization of the UDDI node manager. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0010E: Error, NodeManager initialization Throwable releasing connection.
Explanation An exception occurred during initialization of the UDDI node manager when releasing the database connection. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDN0011E: Error, NodeManager destroy failed getting PersisterControl.
Explanation An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. Action No action is required.
CWUDN0012E: Error, NodeManager destroy UDDIException during destroy.
Explanation An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. Action No action is required.
CWUDN0013E: Error, NodeManager destroy rollback Exception.
Explanation An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. Action No action is required.
CWUDN0014E: Error, NodeManager destroy Exception releasing connection.
Explanation An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. Action No action is required.
CWUDQ0001I: UDDI registry migration datasource is present
Explanation The UDDI migration data source is defined when UDDI is started. Action No action is required.
CWUDQ0002I: UDDI registry migration has started {0} {1}
Explanation The UDDI database migration process has started. This can take some time to complete, depending on the size of the database. Action No action is required.
CWUDQ0003I: UDDI registry migration has completed
Explanation This message is for informational purposes only. Action No action is required.
CWUDQ0004W: UDDI registry not started due to migration errors
Explanation The UDDI registry has not been activated because there were migration errors. Action Examine the messages produced during the migration process and determine whether the problem is one that you can resolve, for example, the v2 database is shut down.If you can, resolve the problem, then re-create the v3 UDDI database and restart the UDDI application.
CWUDQ0005I: {0} rows have been inserted into table {1}
Explanation This message shows the number of database rows converted for each UDDI table. Action No action is required.
CWUDQ1001E: Row not inserted into {0}
Explanation A row could not be inserted into the database table shown in the message. Action See the accompanying error messages for more information. CWUDQ1003E shows details of the SQL exception.
CWUDQ1002E: Table {0} values are: {1}
Explanation This message shows the significant key values of the row being migrated into the specified database table. Action No action is required.
CWUDQ1003E: SQL Exception during migration: {0}
Explanation The SQL exception shown in the message has occurred during the migration process. Action Examine the SQL exception message and the accompanying error messages to help to resolve the problem. Message CWUDQ1002E contains table details and significant key values.
CWUDQ1004E: {0} rows not inserted into table {1} due to errors
Explanation This message shows the number of database rows that were not converted for the specified UDDI table. Action No action is required.
CWUDQ1005E: SQL Exception during key value extraction: {0}
Explanation An SQL exception occurred during the production of the CWUDQ1002E message. Action No action is required.
CWUDQ1006E: Exception during migration: {0}
Explanation The exception shown in the message has occurred during the migration process. Action Examine the exception message and the accompanying error messages to help to resolve the problem. Message CWUDQ1002E contains table details and significant key values.
CWUDS0001E: ParserPool found empty while attempting to process request. Request unsatisfied.
Explanation A SOAP request was received, but could not be dealt with, because there were no free Parsers in the ParserPool. Action Consider increasing the number of Parsers in the ParserPool by modifying the init parameter on the SOAP servlets.
CWUDS0002E: Error locating schemas required for UDDI processing. SOAP servlets unworkable.
Explanation The SOAP servlet could not locate the schemas it requires to process SOAP requests. Without these, the servlet cannot process SOAP requests. Action Check that the installation of UDDI was performed correctly. If the error continues, examine the Application Server logs for information about its cause.
CWUDS0003W: Servlet unable to locate init parameter 'defaultPoolSize'. Using internal defaults.
Explanation The SOAP servlet could not locate the init parameter, which sets the default size of the ParserPool. It will use an internal default setting. Action If this message occurred after attempting to change the defaultPoolSize init parameter, ensure that the changes were correct. If this message occurred after installation, ensure that installation was performed correctly.
CWUDS0004W: Servlet unable to understand init parameter 'defaultPoolSize'. Using internal defaults.
Explanation The SOAP servlet could not parse the init parameter which sets the default size of the ParserPool. It will use an internal default setting. Action If this message occurred after attempting to change the defaultPoolSize init parameter, ensure that the changes were correct. If this message occurred after installation, ensure that installation was performed correctly.
CWUDS0005E: Error occurred during parser creation.
Explanation An unspecified error occurred during the creation of a SOAP parser. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDS0006E: Internal configuration error.
Explanation This error might occur if there was a failure creating a parser, with accompanying message CWUDS0005. It might also occur if there was a problem acquiring the persistence layer. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDS0007E: Error during servlet acquisition of persistence layer.
Explanation The SOAP servlet could not acquire the persistence layer required for it to communicate with the UDDI data source. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDS0008E: Error during servlet release of persistence layer.
Explanation The persistence layer reported a problem when the SOAP servlet attempted to release it. Action Restart the UDDI registry. If the error continues, examine the Application Server logs for information about its cause.
CWUDS0009E: Error during sending of response to client.
Explanation An error occurred when sending a SOAP response message back to a client. The client might not have received the response. Action This error is recorded so that failed responses to clients are logged. The client might have disconnected before the reply could be sent, or there might be a network problem. Examine the Application Server logs for more information about its cause.
CWUDS0010E: Serious error while servlet attempting to process doPost Request.
Explanation An error occurred processing a UDDI v1 or v2 SOAP request. Action Check that the UDDI v1 or v2 SOAP request is valid.
CWUDS0011E: incomplete URL receieved processing doGet Request.
Explanation An incomplete or incorrect UDDI v3 GET request was received. Action Check that the UDDI v3 GET request URL is valid.
CWUDS0012E: non-UDDI exception received processing doGet Request.
Explanation An error occurred while processing a UDDI v3 GET request. Action Check that the UDDI v3 GET request URL is valid.
CWUDT0001E: UDDIFatalErrorException processing request.
Explanation An internal error occurred while processing a UDDI v3 SOAP request. Action Check the configuration of the UDDI enterprise application.
CWUDT0002E: UDDIFatalErrorException processing request.
Explanation A UDDI error occurred while processing a UDDI v3 SOAP request. Action Check the validity of the UDDI request.
CWUDT0003E: UDDIFatalErrorException processing request.
Explanation An error occurred while processing a UDDI v3 SOAP request. Action Check the validity of the UDDI request.