Explanation | The user console control servlet is starting. |
Action | No action is required. |
Explanation | The user console control servlet has completed startup successfully. |
Action | No action is required. |
Explanation | The user console control servlet has started reading external parameters during initialization. |
Action | No action is required. |
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. |
Explanation | An unexpected error has occurred. Examine the error message, error type, and additional information to help to resolve the problem. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |
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. |
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. |
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 | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The contents of a form object cannot be checked for characters that are not valid. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The contents of a form object cannot be checked for characters that are not valid. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The UDDI administrative function cannot connect to the UDDI registry database. |
Action | Check the configuration of the data source. |
Explanation | The UddiNode MBean for the UDDI application could not be unregistered from the MBeanServer. |
Action | Restart the UDDI application or the application server. |
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. |
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. |
Explanation | A database error occurred. |
Action | Check the connection to the UDDI database and the installation configuration of the UDDI application. |
Explanation | A database error occurred. |
Action | Check the connection to the UDDI database and the installation configuration of the UDDI application. |
Explanation | A database error occurred. |
Action | Check the connection to the UDDI database and the installation configuration of the UDDI application. |
Explanation | A database error occurred. |
Action | Check the connection to the UDDI database and the installation configuration of the UDDI application. |
Explanation | An error occurred trying to activate the UDDI node. |
Action | Check the running state of the UDDI application. Restart the application if necessary. |
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. |
Explanation | An error occurred trying to deactivate the UDDI node. |
Action | Check the running state of the UDDI application. Restart the application if necessary. |
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. |
Explanation | An error occurred during initialization of the UDDI node. |
Action | Check the installation and data source settings of the UDDI application. |
Explanation | A configuration property that is required for UDDI node initialization has not been supplied. |
Action | Supply a value for the required property. |
Explanation | A UDDI node can be initialized only once. |
Action | No action is required. |
Explanation | A UDDI node can be initialized only once. |
Action | No action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The policy with the specified ID does not exist. |
Action | Use a valid policy ID. You can find these in the PolicyConstants interface information. |
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. |
Explanation | The value set property ID or tModel key supplied was not recognized. |
Action | Supply a valid value set property ID and tModel key. |
Explanation | A database error might have occurred. |
Action | Check the configuration of the UDDI application and the connection to the UDDI database. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The Digester configuration file could not be loaded. |
Action | Check the configuration of the UDDI application. |
Explanation | The Digester configuration file is not in the correct format. |
Action | Check the configuration of the UDDI application. |
Explanation | A date format in the configuration file is not correct. |
Action | Check the configuration of the UDDI application. |
Explanation | The UDDI node is ready to accept UDDI Application Programming Interface requests. |
Action | No action is required. |
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. |
Explanation | The UDDI node is ready to accept UDDI Application Programming Interface requests. |
Action | No action is required. |
Explanation | A new UDDI publisher has been created. |
Action | No action is required. |
Explanation | A UDDI publisher has been updated. |
Action | No action is required. |
Explanation | A UDDI publisher has been deleted. |
Action | No action is required. |
Explanation | A new UDDI tier has been created. |
Action | No action is required. |
Explanation | A UDDI tier has been updated. |
Action | No action is required. |
Explanation | A UDDI tier has been deleted. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The administrative operation described in the message completed successfully. |
Action | No action is required. |
Explanation | The UDDI registry node has changed to the new state shown in the message. |
Action | No action is required. |
Explanation | The UDDI registry node was requested to change to a state that is not valid. |
Action | No action is required. |
Explanation | The UDDI registry node configuration is successfully made persistent. |
Action | No action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. |
Action | No action is required. |
Explanation | An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. |
Action | No action is required. |
Explanation | An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. |
Action | No action is required. |
Explanation | An exception occurred when the UDDI application was stopping. This problem will not affect any subsequent UDDI restarts. |
Action | No action is required. |
Explanation | The UDDI migration data source is defined when UDDI is started. |
Action | No action is required. |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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 Version 2 database is shut down.If you can, resolve the problem, then re-create the Version 3 UDDI database and restart the UDDI application. |
Explanation | This message shows the number of database rows converted for each UDDI table. |
Action | No action is required. |
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. |
Explanation | This message shows the significant key values of the row being migrated into the specified database table. |
Action | No action is required. |
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. |
Explanation | This message shows the number of database rows that were not converted for the specified UDDI table. |
Action | No action is required. |
Explanation | An SQL exception occurred during the production of the CWUDQ1002E message. |
Action | No action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An error occurred processing a UDDI Version 1 or Version 2 SOAP request. |
Action | Check that the UDDI Version 1 or Version 2 SOAP request is valid. |
Explanation | An incomplete or incorrect UDDI Version 3 GET request was received. |
Action | Check that the UDDI Version 3 GET request URL is valid. |
Explanation | An error occurred while processing a UDDI Version 3 GET request. |
Action | Check that the UDDI Version 3 GET request URL is valid. |
Explanation | An internal error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the configuration of the UDDI enterprise application. |
Explanation | A UDDI error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the validity of the UDDI request. |
Explanation | An error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the validity of the UDDI request. |