WebSphere Process Server messages     Operating Systems: All supported

CWUDG/CWUDM/CWUDN/CWUDQ/CWUDS/CWUDT

CWUDG0001I: {0} starting initialization.
Problem The user console control servlet is starting.
User response None.
CWUDG0002I: {0} finished initialization.
Problem The user console control servlet has completed startup successfully.
User response None.
CWUDG0003I: Reading init parameters.
Problem The user console control servlet has started reading external parameters in its init method.
User response None.
CWUDG0004I: Finished reading init parameters.
Problem The user console control servlet has finished reading external parameters in its init method. This message indicates the user console is ready to accept client requests.
User response None.
CWUDG0005E: A serious error has occurred. error message: <{0}> error: {1} More information: {2}
Problem This error message indicates an unexpected error has occurred. The <Message> describes the error that occurred and the <Throwable> is the type of error that was caught. <Additional information> may provide further information, if available.
User response A trace of the gui component is recommended. Contact IBM support with this information.
CWUDG0006E: A persistence error has occurred. error message: <{0}> error: {1} More information: {2}
Problem An error occurred while performing a database operation. The <Message> describes the error that occurred and the <Throwable> is the type of error that was caught. <Additional information> may provide further information, if available.
User response Check database connections and state. Provide IBM support with a trace, including the gui and persistence components.
CWUDG0007E: A User mismatch error has occurred. error message: <{0}> error: {1} More information: {2}
Problem The user id provided does not match the user id required or expected whilst performing an operation that requires authentication. The <Message> describes the error that occurred and the <Throwable> is the type of error that was caught. <Additional information> may provide further information, if available.
User response Check the user has authority for the operation being requested. If necessary, contact IBM support detailing the actions taken to recreate the problem.
CWUDG0008E: An invalid key was passed. error message: <{0}> error: {1} More information: {2}
Problem The requested operation is trying to retrieve information about an entity with a key that is invalid. This may occur if the entity has been deleted by another session. The <Message> describes the error that occurred and the <Throwable> is the type of error that was caught. <Additional information> may provide further information, if available.
User response Ask the client to close existing sessions and attempt the operation in a new browser session. If the problem persists, contact IBM support with a trace of the gui and api components.
CWUDG0009E: An invalid value was supplied. error message: <{0}> error: {1} More information: {2}
Problem An invalid value was passed to an API call. The <Message> describes the error that occurred and the <Throwable> is the type of error that was caught. <Additional information> may provide further information, if available.
User response Contact IBM support with a trace of the gui and api components.
CWUDG0010E: Failed to introspect ActionForm fields. Exception: {0}
Problem String properties of a form object could not be introspected which means that the form contents cannot be checked for invalid characters.
User response Contact IBM support with details of the Exception and a trace of the gui component.
CWUDG0011E: Failed to invoke reflected methods in ActionForm. Exception: {0}
Problem A form object's declared public method for setting or getting a String value could not be invoked. This method is required to check for invalid characters.
User response Contact IBM support with details of the Exception and a trace of the gui component.
CWUDG0012E: User console initialisation failed to connect to UDDI database. Exception: {0}
Problem During user console initialization, connection to the database failed, and threw the exception specified.
User response Check the connection to the UDDI database. The included exception message may yield some clues to help you resolve the problem. If unresolved, contact IBM support with a trace of the gui component during startup.
CWUDG0013E: User console initialisation failed to initialize tModels. Exception: {0}
Problem Indicates that an error has occurred during initialization of ActionServlet, specifically when reading tModels (invoking init method in class TModelNames).
User response Check the state of the UDDI database. Visually inspect the TMODEL table and confirm it is populated with valid data. The included exception message may yield some clues to help resolve the problem. If unresolved, contact IBM support with a trace of the gui component during startup.
CWUDG0014E: User console initialization failed to initialize taxonomies. Exception: {0}
Problem Indicates that an error has occurred during initialization of ActionServlet, specifically when reading taxonomy data (invoking init method of CategoryTaxonomyTree).
User response Check the state of the UDDI database. The included exception message may yield some clues to help resolve the problem. If unresolved, contact IBM support with a trace of the gui component during startup.
CWUDM0001E: An unexpected error occurred performing the administrative operation: {0}. Exception: {1}.
Problem An internal error occurred processing the specified UddiNode MBean operation.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0002E: MBean transaction failed. Commit flag was: {0}
Problem Failed to commit or rollback the current transaction
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0003E: MBean transaction did not begin.
Problem Failed to invoke begin method on the UserTransaction.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0004E: MBean transaction connection failed to release.
Problem Failed to release connection after transaction committed or rolled back.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0005E: MBean could not establish control with persistence manager.
Problem Message is self-explanatory.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0006E: MBean could not acquire connection for UDDI datasource.
Problem Message is self-explanatory.
User response Check datasource configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0007E: UddiNode MBean with ObjectName {0} could not be unregistered.
Problem The UddiNode MBean for the UDDI application could not be unregistered from the MBeanServer.
User response Restart the UDDI application or the application server. If the problem cannot be resolved, contact your IBM Customer Service Center, supplying the ObjectName value reported in the message (if present).
CWUDM0008W: MBean notfication for event {0} failed.
Problem Message is self-explanatory.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0009W: A UddiNode MBean is already registered.
Problem There is a UddiNode MBean registered in the same cell, node and server.
User response Ensure there is only one UDDI application deployed in the server. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0020E: Unable to retrieve UDDI node ID.
Problem A database error occurred.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0021E: Unable to retrieve UDDI node state.
Problem A database error occurred.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0022E: Unable to retrieve UDDI node application name.
Problem A database error occurred.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0023E: Unable to retrieve UDDI node description.
Problem A database error occurred.
User response Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0024E: Unable to activate UDDI node.
Problem An error occurred trying to activate the UDDI node.
User response Check the running state of the UDDI application. Restart the application if necessary. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0025I: Unable to activate a UDDI node that is not initialized.
Problem The UDDI node must be initialized (and in deactivated state) before it can be activated.
User response If the UDDI node is ready to be initialized, invoke the initialization operation.
CWUDM0026E: Unable to deactivate UDDI node.
Problem An error occurred trying to deactivate the UDDI node.
User response Check the running state of the UDDI application. Restart the application if necessary. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0027I: Unable to deactivate UDDI node that is not initialized.
Problem The UDDI node must be initialized (and activated) before it can be deactivated.
User response If the UDDI node is ready to be initialized, invoke the initialization operation.
CWUDM0028E: Unable to initialize UDDI node.
Problem An error occurred during UDDI node initialization.
User response Check the UDDI application installation and datasource settings. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0029I: Unable to initialize UDDI node because a required property is missing or invalid: {0}.
Problem A configuration property that is required for UDDI node initialization has not been populated.
User response Supply a value for the required property.
CWUDM0030I: Initialize operation did not occur because the UDDI node is already initialized.
Problem A UDDI node can only be initialized once.
User response None.
CWUDM0031I: Initialize operation did not occur because the UDDI node is in default configuration and is already initialized.
Problem A UDDI node can only be initialized once.
User response None.
CWUDM0051E: Unable to create UDDI publisher with user name {0}.
Problem An error occurred trying to register the UDDI publisher.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0053E: Unable to delete UDDI publisher with user name {0}.
Problem An error occurred trying to register the UDDI publisher.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0056E: Unable to update UDDI publisher with user name {0}.
Problem An error occurred trying to update the UDDI publisher.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0059E: Unable to retrieve information for UDDI publisher with user name {0}.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0060E: Unable to retrieve collection of UDDI publishers.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0061E: Unable to get tier assigned to UDDI publisher with user name {0}.
Problem This may because the UDDI publisher with the specified user name does not exist, or because a database error occurred performing the operation.
User response Check the UDDI publisher exists. If it does, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0062E: Unable to create UDDI publishers with user names: {0}.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0070E: Unable to create tier with ID: {0}.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0071E: Unable to delete tier with ID: {0}.
Problem This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation.
User response Check the tier ID. If it does exist, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0072E: Unable to retrieve information for tier with ID: {0}.
Problem This may be because the supplied tier ID is not an integer, or the tier with the ID does not exist, or because of a database error performing the operation.
User response Check the tier ID is an integer and the tier exists. If it does exist, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0073E: Unable to retrieve collection of tiers.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0074E: Unable to set default tier to tier ID: {0}.
Problem This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation.
User response Check the tier ID. If it does exist, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0075E: Unable to update tier with ID: {0}.
Problem This is most likely because the tier with the specified ID does not exist, or because a database error occurred performing the operation.
User response Check the tier ID. If it does exist, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0076E: Unable to get count of UDDI publishers for tier ID: {0}.
Problem This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation.
User response Check the tier ID. If it does exist, check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0077E: Unable to retrieve collection of entitlements.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0078E: Unable to retrieve collection of limits.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0079I: The default tier cannot be deleted.
Problem A tier must always exist that is designated as the tier assigned to UDDI publishers when auto-registration of UDDI publishers is enabled.
User response None.
CWUDM0100E: Unable to get configuration property information for property with ID: {0}.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0102E: Unable to retrieve collection of configuration properties.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0103E: Unable to update configuration properties.
Problem This may occur if any of the updated property objects fails validation. Check any cause exceptions for possible additional information. Alternatively database error may have occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0104E: Unable to update configuration property with ID: {0}.
Problem This may occur if the updated property object fails validation. Check any cause exceptions for possible additional information. Alternatively a database error may have occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0107E: Failed to retrieve required properties from database.
Problem This indicates a database error occurred when trying to initialize a UDDI node.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0120E: Unable to get policy information for policy with ID: {0}.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0122E: Unable to get policy group with group ID: {0}
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0123E: Unable to retrieve collection of policy groups.
Problem A database error occurred performing the operation.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0124E: Unable to update policies.
Problem This may occur if any of the updated policy objects fails validation. Check any cause exceptions for possible additional information. Alternatively a database error may have occurred performing the operation.
User response Ensure all policy IDs and values are valid. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0125E: Unable to update policy with ID: {0}.
Problem This may occur if the updated policy object fails validation or the ID isn't recognized. Check any cause exceptions for possible additional information. Alternatively a database error may have occurred performing the operation.
User response Check the policy ID and value are valid. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0140E: Unable to change value set tModelKey from {0} to {1}.
Problem The policy with the specified ID does not exist.
User response Use a valid policy ID. These can be found in PolicyConstants.
CWUDM0141E: Unable to retrieve value set details for tModel key: {0}.
Problem A database error occurred getting the value set details.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0142E: Unable to get value set property: {1} for value set with tModel key: {0}.
Problem The value set property ID or tModel key supplied was not recognized.
User response Supply a valid value set property ID and tModel key. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0143E: Unable to retrieve value sets collection.
Problem A database error may have occurred.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0144E: Unable to determine if value set with tModel key: {0} exists.
Problem The tModel key supplied is not valid or a database error may have occurred.
User response Ensure the tModel exists. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0145E: Unable to load value set data for value set with tModel key: {0} and file name: {1}.
Problem The tModel key is not recognized, the file doesn't contain valid value set data, or a database error occurred.
User response Ensure the tModel exists and the value set data object is populated. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0146E: Unable to load value set data for value set with tModel key: {0}.
Problem The tModel key is not recognized or a database error occurred.
User response Ensure the tModel exists and the value set data object is populated. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0147E: Could not update value set status with tModel key: {0}.
Problem The value set status object supplied is null or the tModel key is not known.
User response Supply a valid value set status object with tModel key for a value set tModel that exists. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0148E: Could not update value set status with tModel key: {0}, property: {1}.
Problem A database error occurred updating the supported status of the value set status.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0149E: Could not update value set status with tModel key: {0}.
Problem One of the supplied value set status objects contained a tModel key which was not recognized.
User response Supply tModel keys for value set tModels that exist. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0150E: Could not update value set status with tModel key: {0}, property: {1}.
Problem A database error occurred updating the supported status of one of the value set status objects.
User response Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0151E: Unable to unload value set data with tModel key: {0}.
Problem The tModel key is not recognized or a database error occurred.
User response Ensure the tModel exists. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0170W: Loading of configuration file {0} failed.
Problem The Digester configuration file could not be loaded.
User response Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0171W: Parsing of configuration file {0} failed.
Problem The Digester configuration file is not in the correct format.
User response Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0172W: An unexpected date format was found while parsing configuration file.
Problem An incorrect date format is contained in the configuration file.
User response Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDM0180I: UDDI node was activated.
Problem The UDDI node is ready to accept UDDI API requests.
User response None.
CWUDM0181I: UDDI node was deactivated.
Problem The UDDI node is set to not accept UDDI API requests. This typically occurs when configuration settings are being updated by administrative tasks.
User response None.
CWUDM0182I: UDDI node initialized successfully.
Problem The UDDI node is ready to accept UDDI API requests.
User response None.
CWUDM0183I: UDDI publisher {0} was created.
Problem A new UDDI Publisher has been created.
User response None.
CWUDM0184I: UDDI publisher {0} was updated.
Problem A UDDI Publisher has been updated.
User response None.
CWUDM0185I: UDDI publisher {0} was deleted.
Problem A UDDI Publisher has been deleted.
User response None.
CWUDM0186I: Tier {0} was created.
Problem A new UDDI Tier has been created.
User response None.
CWUDM0187I: Tier {0} was updated.
Problem A UDDI Tier has been updated.
User response None.
CWUDM0188I: Tier {0} was deleted.
Problem A UDDI Tier has been deleted.
User response None.
CWUDM0189I: Configuration property {0} was updated to value {1}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0190I: Policy {0} was updated to value {1}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0191I: Default tier was set to {0}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0192I: Loaded value set for tModel key {0} from file {1}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0193I: Loaded value set for tModel key {0}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0194I: Unloaded value set for tModel key {0}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0195I: Updated value set supported status for tModel key {0} to {1}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDM0196I: Changed tModel key for value set from {0} to {1}.
Problem This message indicates the administrative operation completed successfully.
User response None.
CWUDN0001I: UDDI Node State change, new state: {0}
Problem The UDDI Registry Node has changed to a the new state indicated.
User response None.
CWUDN0002E: Error, invalid Node State requested: {0}
Problem The UDDI Registry Node was requested to change to an invalid state.
User response None.
CWUDN0003I: {0}
Problem The UDDI Registry Node configuration is persisted successfully.
User response None.
CWUDN0004E: Error, NodeManager initialization failed getting PersisterControl.
Problem The UDDI Node Manager was unable to access the UDDI Database.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0005E: Error, NodeManager initialization UDDIFatalErrorException.
Problem An exception occurred during UDDI Node Manager initialization.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0006E: Error, NodeManager initialization UDDIException.
Problem An exception occurred during UDDI Node Manager initialization.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0007E: Error, NodeManager initialization Exception.
Problem An exception occurred during UDDI Node Manager initialization.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0008E: Error, NodeManager initialization Throwable.
Problem An exception occurred during UDDI Node Manager initialization.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0009E: Error, NodeManager initialization rollback Exception.
Problem An exception occurred during UDDI Node Manager initialization.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0010E: Error, NodeManager initialization Throwable releasing connection.
Problem An exception occurred during UDDI Node Manager initialization when releasing the database connection.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDN0011E: Error, NodeManager destroy failed getting PersisterControl.
Problem An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts.
User response None.
CWUDN0012E: Error, NodeManager destroy UDDIException during destroy.
Problem An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts.
User response None.
CWUDN0013E: Error, NodeManager destroy rollback Exception.
Problem An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts.
User response None.
CWUDN0014E: Error, NodeManager destroy Exception releasing connection.
Problem An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts.
User response None.
CWUDQ0001I: UDDI registry migration datasource is present
Problem The UDDI migration datasource is defined when UDDI is started.
User response None.
CWUDQ0002I: UDDI registry migration has started {0} {1}
Problem The UDDI database migration process has started. This may take sometime to complete dependant on the size of your database.
User response None.
CWUDQ0003I: UDDI registry migration has completed
Problem The UDDI database migration process has finished.
User response None.
CWUDQ0004W: UDDI registry not started due to migration errors
Problem The UDDI Registry has not been activated because migration errors were encountered.
User response Examine the messages produced during the migration process. Detemine if the problem is user fixable, that is, the Version 2 database is quiesced and so on. If the problem is fixable re-create the Version 3 UDDI database and restart the UDDI application. If the problem can not be rectified contact your IBM Customer Service Center.
CWUDQ0005I: {0} rows have been inserted into table {1}
Problem An informational message showing the number of database rows converted for each UDDI table.
User response None.
CWUDQ1001E: Row not inserted into {0}
Problem A row was unable to be inserted into a database table.
User response See CWUDQ1003E for details of the SQL Exception details.
CWUDQ1002E: Table {0} values are: {1}
Problem Contains the table in error and the significant key values of the row being migrated.
User response None.
CWUDQ1003E: SQL Exception during migration: {0}
Problem An SQL Exception has occurred during the migration process. The SQL Exception details are displayed in the message.
User response Examine the SQL Exception information on its cause. Message CWUDQ1002E contains table details and significant key values. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDQ1004E: {0} rows not inserted into table {1} due to errors
Problem A message showing the number of database rows not converted for a particular UDDI table.
User response None.
CWUDQ1005E: SQL Exception during key value extraction: {0}
Problem An SQL Exception occurred during the production of the CWUDQ1002E message.
User response None.
CWUDQ1006E: Exception during migration: {0}
Problem An Exception has occurred during the migration process. The Exception details are displayed in the message.
User response Examine the Exception information on its cause. Message CWUDQ1002E contains table details and significant key values. If the problem cannot be resolved, contact your IBM Customer Service Center.
CWUDS0001E: ParserPool found empty while attempting to process request. Request unsatisfied.
Problem A SOAP request was received, but was unable to be dealt with, as there were no free Parsers within the ParserPool.
User response Consider increasing the number of Parsers within the ParserPool by modifying the Init Parameter on the SOAP servlets.
CWUDS0002E: Error locating schemas required for UDDI processing. SOAP servlets unworkable.
Problem The SOAP servlet was unable to locate the schemas it requires in order to process SOAP requests. Without these, the servlet cannot process SOAP requests.
User response Check installation of UDDI was performed correctly. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDS0003W: Servlet unable to locate init parameter 'defaultPoolSize'. Using internal defaults.
Problem The SOAP servlet was unable to locate the init parameter which sets the default size of the ParserPool. It will fall back to an internal default.
User response If this message occurred after attempting to make changes to the defaultPoolSize init parameter, ensure the changes were correct. If this message has appeared after installed, ensure installation was performed correctly.
CWUDS0004W: Servlet unable to understand init parameter 'defaultPoolSize'. Using internal defaults.
Problem The SOAP servlet was unable to parse the init parameter which sets the default size of the ParserPool. It will fall back to an internal default.
User response If this message occurred after attempting to make changes to the defaultPoolSize init parameter, ensure the changes were correct. If this message has appeared after installed, ensure installation was performed correctly.
CWUDS0005E: Error occurred during parser creation.
Problem An unspecified error occurred during the creation of a SOAP parser.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDS0006E: Internal configuration error.
Problem This error may occur if there was a failure creating a Parser, with accompanying message CWUDS0005. It may also occur if there was a problem acquiring the Persistence layer.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDS0007E: Error during servlet acquisition of persistence layer.
Problem The SOAP servlet was unable to acquire the persistence layer required for it to communicate with the UDDI datasource.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDS0008E: Error during servlet release of persistence layer.
Problem The persistence layer reported a problem when the SOAP servlet attempted to release it.
User response Restart the UDDI registry. If the error persists, examine the WebSphere logs for information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDS0009E: Error during sending of response to client.
Problem An error occurred when sending a SOAP response message back to a client. The client may not have receieved the response.
User response This error is recorded to enable logging of failed responses to clients. The error may be the fault of the client disconnecting before the reply could be sent, or may indicate a network problem. Examine the WebSphere logs for more information on its cause.
CWUDS0010E: Serious error while servlet attempting to process doPost Request.
Problem A serious error occurred processing a UDDI Version 1 or Version 2 SOAP request.
User response Check the validity of the UDDI Version 1 or Version 2 SOAP request.
CWUDS0011E: incomplete URL receieved processing doGet Request.
Problem An incomplete or incorrect UDDI Version 3 GET request was received.
User response Check the validity of the UDDI Version 3 GET request URL.
CWUDS0012E: non-UDDI exception received processing doGet Request.
Problem A serious error occurred while processing a UDDI Version 3 GET request.
User response Check the validity of the UDDI Version 3 GET request URL.
CWUDT0001E: UDDIFatalErrorException processing request.
Problem A serious internal error occurred while processing a UDDI Version 3 SOAP request.
User response Check the configuration of the UDDI Enterprise Application. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDT0002E: UDDIFatalErrorException processing request.
Problem A serious UDDI error occurred while processing a UDDI Version 3 SOAP request.
User response Check the validity of the UDDI request.
CWUDT0003E: UDDIFatalErrorException processing request.
Problem A serious non UDDI error occurred while processing a UDDI Version 3 SOAP request.
User response Check the validity of the UDDI request.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.uddi.ras.UDDIMessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)