Explanation | The user console control servlet is starting. |
Action | None. |
Explanation | The user console control servlet has completed startup successfully. |
Action | None. |
Explanation | The user console control servlet has started reading external parameters in its init method. |
Action | None. |
Explanation | 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. |
Action | None. |
Explanation | 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. |
Action | A trace of the gui component is recommended. Contact IBM support with this information. |
Explanation | 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. |
Action | Check database connections and state. Provide IBM support with a trace, including the gui and persistence components. |
Explanation | 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. |
Action | Check the user has authority for the operation being requested. If necessary, contact IBM support detailing the actions taken to recreate the problem. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | Contact IBM support with a trace of the gui and api components. |
Explanation | String properties of a form object could not be introspected which means that the form contents cannot be checked for invalid characters. |
Action | Contact IBM support with details of the Exception and a trace of the gui component. |
Explanation | 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. |
Action | Contact IBM support with details of the Exception and a trace of the gui component. |
Explanation | During user console initialization, connection to the database failed, and threw the exception specified. |
Action | 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. |
Explanation | Indicates that an error has occurred during initialization of ActionServlet, specifically when reading tModels (invoking init method in class TModelNames). |
Action | 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. |
Explanation | Indicates that an error has occurred during initialization of ActionServlet, specifically when reading taxonomy data (invoking init method of CategoryTaxonomyTree). |
Action | 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. |
Explanation | An internal error occurred processing the specified UddiNode MBean operation. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | Failed to commit or rollback the current transaction |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | Failed to invoke begin method on the UserTransaction. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | Failed to release connection after transaction committed or rolled back. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | Message is self-explanatory. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | Message is self-explanatory. |
Action | Check datasource configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The UddiNode MBean for the UDDI application could not be unregistered from the MBeanServer. |
Action | 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). |
Explanation | Message is self-explanatory. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | There is a UddiNode MBean registered in the same cell, node and server. |
Action | Ensure there is only one UDDI application deployed in the server. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred. |
Action | Check database connectivity and UDDI application installation configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | An error occurred trying to activate the UDDI node. |
Action | 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. |
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, invoke 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. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The UDDI node must be initialized (and activated) before it can be deactivated. |
Action | If the UDDI node is ready to be initialized, invoke the initialization operation. |
Explanation | An error occurred during UDDI node initialization. |
Action | Check the UDDI application installation and datasource settings. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A configuration property that is required for UDDI node initialization has not been populated. |
Action | Supply a value for the required property. |
Explanation | A UDDI node can only be initialized once. |
Action | None. |
Explanation | A UDDI node can only be initialized once. |
Action | None. |
Explanation | An error occurred trying to register the UDDI publisher. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | An error occurred trying to register the UDDI publisher. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | An error occurred trying to update the UDDI publisher. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | This may because the UDDI publisher with the specified user name does not exist, or because a database error occurred performing the operation. |
Action | 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. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation. |
Action | 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. |
Explanation | This is most likely because the tier with the specified ID does not exist, or because a database error occurred performing the operation. |
Action | 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. |
Explanation | This may because the tier with the specified ID does not exist, or because a database error occurred performing the operation. |
Action | 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. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A tier must always exist that is designated as the tier assigned to UDDI publishers when auto-registration of UDDI publishers is enabled. |
Action | None. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | 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. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | 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. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | This indicates a database error occurred when trying to initialize a UDDI node. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred performing the operation. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | The policy with the specified ID does not exist. |
Action | Use a valid policy ID. These can be found in PolicyConstants. |
Explanation | A database error occurred getting the value set details. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The value set property ID or tModel key supplied was not recognized. |
Action | Supply a valid value set property ID and tModel key. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error may have occurred. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The tModel key supplied is not valid or a database error may have occurred. |
Action | Ensure the tModel exists. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The tModel key is not recognized, the file doesn't contain valid value set data, or a database error occurred. |
Action | 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. |
Explanation | The tModel key is not recognized or a database error occurred. |
Action | 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. |
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 UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | A database error occurred updating the supported status of the value set status. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | One of the supplied value set status objects contained a tModel key which was not recognized. |
Action | 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. |
Explanation | A database error occurred updating the supported status of one of the value set status objects. |
Action | Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The tModel key is not recognized or a database error occurred. |
Action | Ensure the tModel exists. Check UDDI application configuration and database connectivity. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The Digester configuration file could not be loaded. |
Action | Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The Digester configuration file is not in the correct format. |
Action | Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | An incorrect date format is contained in the configuration file. |
Action | Check UDDI application configuration. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Explanation | The UDDI node is ready to accept UDDI API requests. |
Action | None. |
Explanation | The UDDI node is set to not accept UDDI API requests. This typically occurs when configuration settings are being updated by administrative tasks. |
Action | None. |
Explanation | The UDDI node is ready to accept UDDI API requests. |
Action | None. |
Explanation | A new UDDI Publisher has been created. |
Action | None. |
Explanation | A UDDI Publisher has been updated. |
Action | None. |
Explanation | A UDDI Publisher has been deleted. |
Action | None. |
Explanation | A new UDDI Tier has been created. |
Action | None. |
Explanation | A UDDI Tier has been updated. |
Action | None. |
Explanation | A UDDI Tier has been deleted. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | This message indicates the administrative operation completed successfully. |
Action | None. |
Explanation | The UDDI Registry Node has changed to a the new state indicated. |
Action | None. |
Explanation | The UDDI Registry Node was requested to change to an invalid state. |
Action | None. |
Explanation | The UDDI Registry Node configuration is persisted successfully. |
Action | None. |
Explanation | The UDDI Node Manager was unable to access the UDDI Database. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager initialization when releasing the database connection. |
Action | 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. |
Explanation | An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts. |
Action | None. |
Explanation | An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts. |
Action | None. |
Explanation | An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts. |
Action | None. |
Explanation | An exception occurred during UDDI Node Manager destroy, this problem will not affect any subsequent UDDI restarts. |
Action | None. |
Explanation | The UDDI migration datasource is defined when UDDI is started. |
Action | None. |
Explanation | The UDDI database migration process has started. This may take sometime to complete dependant on the size of your database. |
Action | None. |
Explanation | The UDDI database migration process has finished. |
Action | None. |
Explanation | The UDDI Registry has not been activated because migration errors were encountered. |
Action | 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. |
Explanation | An informational message showing the number of database rows converted for each UDDI table. |
Action | None. |
Explanation | A row was unable to be inserted into a database table. |
Action | See CWUDQ1003E for details of the SQL Exception details. |
Explanation | Contains the table in error and the significant key values of the row being migrated. |
Action | None. |
Explanation | An SQL Exception has occurred during the migration process. The SQL Exception details are displayed in the message. |
Action | 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. |
Explanation | A message showing the number of database rows not converted for a particular UDDI table. |
Action | None. |
Explanation | An SQL Exception occurred during the production of the CWUDQ1002E message. |
Action | None. |
Explanation | An Exception has occurred during the migration process. The Exception details are displayed in the message. |
Action | 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. |
Explanation | A SOAP request was received, but was unable to be dealt with, as there were no free Parsers within the ParserPool. |
Action | Consider increasing the number of Parsers within the ParserPool by modifying the Init Parameter on the SOAP servlets. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | An unspecified error occurred during the creation of a SOAP parser. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | The SOAP servlet was unable to acquire the persistence layer required for it to communicate with the UDDI datasource. |
Action | 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. |
Explanation | The persistence layer reported a problem when the SOAP servlet attempted to release it. |
Action | 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. |
Explanation | An error occurred when sending a SOAP response message back to a client. The client may not have receieved the response. |
Action | 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. |
Explanation | A serious error occurred processing a UDDI Version 1 or Version 2 SOAP request. |
Action | Check the validity of the UDDI Version 1 or Version 2 SOAP request. |
Explanation | An incomplete or incorrect UDDI Version 3 GET request was received. |
Action | Check the validity of the UDDI Version 3 GET request URL. |
Explanation | A serious error occurred while processing a UDDI Version 3 GET request. |
Action | Check the validity of the UDDI Version 3 GET request URL. |
Explanation | A serious internal error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the configuration of the UDDI Enterprise Application. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | A serious UDDI error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the validity of the UDDI request. |
Explanation | A serious non UDDI error occurred while processing a UDDI Version 3 SOAP request. |
Action | Check the validity of the UDDI request. |