Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | This is a Web Container exception which can be caused by one of three things: 1. An error occured while preinvoking the security collaborator. 2. An error occured while processing the server connection. 3. An error occured while processing the servlet request. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is a transport error which occurs when bad data has been encountered. |
User response | If this problem persists check the transport configuration associated with the transport which caused the error. |
Problem | This is an internal error which occurs when the plugin forces the application server dispatchers to handle more than one request at a time. |
User response | Check the logs for an IllegalStateException which should occur just before this error, and contact IBM support if the problem persists. |
Problem | This is a Web Container exception which can be caused by one of three things: 1. An error occured while preinvoking the security collaborator. 2. An error occured while processing the server connection. 3. An error occured while processing the servlet request. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Pooled resources don't contain any SQEvents |
User response | None. |
Problem | Problems occured when closing the server queue. |
User response | Examine server logs for exceptions. |
Problem | The virtual host containing requested application is not found. |
User response | Check the virtual host on which application is installed. Make sure virtual host configuration has alias with host and port defined as invoked by clients. |
Problem | This error occured because of a bad or missing X.509 certificate. |
User response | Check the logs for the exception to see the exact trace. Regenerate or obtain a new certificate if the error persists. |
Problem | An error occured while processing a queued service event. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This error occured because two installed applications were found to have the same context root (path). This may lead to indeterminate behaviour. |
User response | One of the applications will need to be uninstalled, and then reinstalled using a different context root. If for some reason itis not possible to uninstall and reinstall, contact IBM support. |
Problem | This is an internal system error and is probably caused by an earlier failure.. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | The specified transport name is not valid. |
User response | Define a transport conforming to the transport definition rules. |
Problem | Failed to add the web group specified in the message to the web container. |
User response | Check the definitions for the web group (web module) in web.xml. |
Problem | Error in the JNDI service. |
User response | Be sure that you have defined a JNDI service and that its port is not in use by another application. |
Problem | Connection queue has overflowed. |
User response | Increase the size of the connection queue. |
Problem | iiopredirector XML contains invalid XML syntax |
User response | Examine the iiopredirector xml for syntax conformance. |
Problem | None. |
User response | None. |
Problem | Attempting to output a buffer of size less than 0. |
User response | Only write buffers of size of 0 or greater. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Initialization parameter name not found. |
User response | Specify a parameter name in the web.xml file. |
Problem | Uncaught exception thrown in servlet service method. |
User response | Varies by root cause. |
Problem | Could not initialize the web application specified in the message. |
User response | Check all definitions for this web application (web module) in the application.xml and web.xml files. |
Problem | Invalid format found for a request header. |
User response | Check client header creation. |
Problem | Could not find the specified web group (web module). |
User response | Be sure the web group is defined and deployed. Also check to be sure that a host and port have been defined for your virtual hosts and that there are no host/port conflicts across your virtual hosts. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | An error was encountered in the specified servlet. |
User response | Varies by reported cause. |
Problem | None. |
User response | None. |
Problem | Could not find a definition for the specified virtual host. |
User response | Make sure the virtual host is defined in the virtualhosts.xml file. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not set an attribute. |
User response | Make sure the attribute conforms to attribute guidelines. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | An error was encountered in the specified servlet. |
User response | Varies by reported cause. |
Problem | Class specified to object pool is not accessible. |
User response | Be sure the class is on the object pool's classpath. |
Problem | Error encountered reading plug-in configuration. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not shutdown server. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | The specified path is not a directory. |
User response | Make sure the directory exists or that you are requesting the right directory. |
Problem | None. |
User response | None. |
Problem | Error encountered stopping a transport. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | WebAppSecurityCollaborator. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | A remote object is not serializable. |
User response | Be sure your remote objects implement the Serializable interface. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem invoking the specified servlet. |
User response | Be sure the servlet is defined and accessible. |
Problem | Total read equals zero. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal error encountered. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not find the specified resource for a servlet. |
User response | Be sure the resource exists and has been defined. |
Problem | JarFileClassProvider is invalid. File has been updated. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | An error occurred during a servlet destroy. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | The specified servlet is being loaded for service. |
User response | None. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal engine error. |
User response | Gather server logs and contact IBM service. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Invalid date format. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Servlet is being destroyed after wait has timed out. |
User response | None. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Input class is not poolable. |
User response | Implement the IPoolable interface in the input class. |
Problem | Could not destroy specified servlet. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not bind the specified host name to the specified serlvet host. |
User response | Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml. |
Problem | The specified directory is invalid. |
User response | Check directory specification for errors. |
Problem | Using first server specification found. |
User response | None. |
Problem | Internal web container error. |
User response | Gather server logs and contact IBM service. |
Problem | Unable to restart a web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | AdminListener. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not invoke service method for the specified servlet. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | Internal web container error. |
User response | Gather server logs and contact IBM service. |
Problem | Internal web container error. |
User response | Gather server logs and contact IBM service. |
Problem | Exception received in http transport. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal web container error. |
User response | Gather server logs and contact IBM service. |
Problem | The specified attribute is not supported. |
User response | Remove the attribute from any XML file that contains it. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | Could not load the specified Web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | A request or response serviced by a servlet is not of type HTTP. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | No servlet host found. |
User response | Make sure virtual hosts have been defined in virtualhosts.xml. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | None. |
User response | None. |
Problem | Could not find the specified resource. |
User response | Be sure the resource exists. |
Problem | Failure to restart WebGroup. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not initialize the default server. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | Could not remove an attribute. |
User response | The attribute might not have been present. Be sure attribute exists and retry. |
Problem | None. |
User response | None. |
Problem | Could not get the specified remote attribute. |
User response | Could be caused by connectivity problems. Wait and try again. |
Problem | The specified servlet could not be found. |
User response | Make sure the servlet exists and is defined properly in the web.xml file. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Specified servlet is temporarily unavailable. |
User response | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Problem | Could not start the transport for the administration service. |
User response | Gather logs and contact IBM support. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | Could not instantiate a class for use by the object pool. |
User response | Be sure the class exists and is visible on the application classpath. |
Problem | Could not initialize the specified servlet. |
User response | Make sure the servlet class file is available on the application classpath. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Two initialization parameters have the same xml id. |
User response | Make sure all initialization parameters have unique id's. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | Problem releasing a session. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Unable to remove the specified remote attribute. |
User response | Potentially a network problem. Wait and try again. |
Problem | Servlet is no longer available for service. |
User response | Restart the web application containing the servlet. |
Problem | Missing flag value. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Failure to create distributed attribute list. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | Could not find a virtual host for the web application. |
User response | Be sure the web application is bound to a valid virtual host. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem invoking the specified error reporter. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Invalid Integer Format. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | IO error encountered. |
User response | Varies depending on reported root cause. |
Problem | Attempting to output a buffer of size less than 0. |
User response | Only write buffers of size of 0 or greater. |
Problem | The specified servlet host could not be found. |
User response | Be sure the virtual host specifications in virtualhosts.xml are valid. |
Problem | A servlet encountered the specified error. |
User response | Varies by root cause. |
Problem | Problem encountered while shutting down the server. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | The specified initialization parameter is missing a value. |
User response | Be sure the definition for the parameter in the web.xml file is complete. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Internal server error. |
User response | Gather server logs and contact IBM Service. |
Problem | Problem encountered invoking the specified servlet. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | The server connection was reset. |
User response | Retry any previously failing operations. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | Invalid content length. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem encountered parsing servlet parameters. |
User response | Check parameter definitions in the web.xml file. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | None. |
User response | None. |
Problem | Problem encountered disabling the specified servlet. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Security problem encountered during request processing. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Security problem encountered during request processing. |
User response | Varies with root cause. |
Problem | Internal server error. |
User response | Gather logs and contact IBM service. |
Problem | Servlet mapping defined with the specified servlet, but servlet was not defined. |
User response | Make sure the servlet is defined in the web.xml file. |
Problem | Could not find the bindings for the web application. |
User response | Be sure that the ibm-web-bnd.xmi file exists for the application. |
Problem | Number format problem in the specified environment entry. |
User response | Correct the environment entry. |
Problem | Invalid type encountered in java:comp binding. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Failure starting a server transport. |
User response | Be sure that the defined transport port is not in use by another application. |
Problem | A virtual host has not been bound to the specified web module. |
User response | Specify a virtual host in the web application's ibm-web-bnd.xmi file. |
Problem | Unable to load the specified WAR file. Most likely a definition problem. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not find the definition for the specified web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem encountered reading the web module definition for the web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | A resource defined in the web application is empty. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem encountered reading the web module definition for the web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem encountered removing the specified web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | This is an internal system error and is probably caused by an earlier failure. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Could not load the specified file. |
User response | Be sure the specified file exists. |
Problem | Could not load the specified file. |
User response | Be sure the specified file exists. |
Problem | An attempt was made to set the response buffer size after the response was already commited. |
User response | Remove the setBufferSize() call or move it to a position before the response commit. |
Problem | Could not determine the context path for a web application. |
User response | Be sure a context path has been defined for the web application in the application.xml file. |
Problem | Could not load the specified session context. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Problem encountered rolling back the specified user transaction. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | Application server identifier. |
User response | None. |
Problem | The servlet specification level supported by the application server. |
User response | None. |
Problem | The JSP specification level supported by the application server. |
User response | None. |
Problem | Two web applications on the same virtual host share the same context root. |
User response | Either change the context root of one of the web applications or move one to a different virtual host. |
Problem | Could not restart the specified web application. |
User response | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | No virtual host has been bound to the web application. Using default. |
User response | If a different virtual host is desired, specify one in the web application bindings. |
Problem | None. |
User response | None. |
Problem | Session manager has not been configured for the web container. |
User response | Define the session manager properties in the server.xml file. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | A JSP file that is deployed in web.xml and is indicated to load-on-startup failed to translate or compile. |
User response | Examine the server logs in order to determine the root cause of the failure. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | LocalTransaction rolled-back due to setRollbackOnly action by the application |
User response | Examine the server logs in order to determine the root cause of the failure. Also check your application for setRollBackOnly calls. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Problem | A JSP page that uses server-side Javascript via the BSF engine was detected. |
User response | Replace server-side Javascript with other mechanisms, such as JSP 2.0 Expression Language in WAS 6.0 |
Problem | The keystore or truststore type specified is invalid. |
User response | Modify the SSL configuration so that the keystore or truststore type is a valid type. You can check the keystore and truststore types by loading them in WebSphere's IKeyMan tool. |
Problem | A problem has occured attempting to access a resource provided by a resource manager (such as a database). |
User response | Ensure the expected resource managers and resources are accessible. For example, ensure that all data sources are correctly defined. |
Problem | An SQLException occured when attempting to close a connection to the resource manager. |
User response | No action is required, as this should not affect the running of the transaction service. |