| 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. |