Explanation | The configured value for the maximum number of requests allowed per socket is not valid. |
Action | Configure a valid value for the maximum number of requests allowed per socket. |
Explanation | The configured value for the incoming buffer size is not valid. |
Action | Configure a valid value for the incoming buffer size. |
Explanation | The configured value for the header buffer size is not valid. |
Action | Configure a valid value for the header buffer size. |
Explanation | The configured value for the outgoing buffer size is not valid. |
Action | Configure a valid value for the outgoing buffer size. |
Explanation | The configured value for the persistent timeout parameter is not valid. |
Action | Configure a valid value for the persistent timeout parameter. |
Explanation | The configured value for the read timeout parameter is not valid. |
Action | Configure a valid value for the read timeout parameter. |
Explanation | The configured value for the write timeout parameter is not valid. |
Action | Configure a valid value for the write timeout parameter. |
Explanation | The configured value for the field size limit is not valid. |
Action | Configure a valid value for the field size limit. |
Explanation | The configured value for the number of headers limit is not valid. |
Action | Configure a valid value for the number of headers limit. |
Explanation | The configured value for the maximum number of bytes for an incoming message body is not valid. |
Action | Configure a valid value for the maximum number of bytes for an incoming message body. |
Explanation | The specified default configuration cannot be found for the specified ID. |
Action | Verify the server configuration, then perform a clean restart. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An HTTP endpoint requires at least one port to be configured. |
Action | Assign a valid port value to the httpPort, or the httpsPort, or both. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The request cannot be handled by an application on the server. |
Action | Make sure that the application is defined and deployed, and has been correctly referenced by the client. |
Explanation | The HTTP endpoint could not be started due to a configuration problem. |
Action | Examine the message and exception logs for related errors. |
Explanation | The HTTP endpoint could not be started due to an unexpected problem. |
Action | Examine the message and exception logs for related errors. |
Explanation | The HTTP endpoint was configured with onError=FAIL, which causes the server to stop if there is a problem starting the endpoint. |
Action | Examine the message and exception logs for related errors. To prevent the server from stopping due to a problem while starting the endpoint, make sure that onError is set to WARN or IGNORE. |
Explanation | A HTTP endpoint requires a host value that can be resolved to an active network interface. |
Action | Ensure the host value refers to an active network interface, or use * to bind to all interfaces. |
Explanation | The defaultHostName variable specifies a host value that could not be resolved to an active network interface. |
Action | Ensure that the configured defaultHostName value refers to an active network interface. |
Explanation | The default virtual host is required by the runtime environment. |
Action | No action is required. |
Explanation | All non-default virtual hosts must define at least one host alias (host:port) to identify inbound requests that should be routed to that virtual host. The specified virtual host does not have any host aliases defined, which will prevent any requests from being routed to it. |
Action | Update the virtualHost element in the server.xml file to define at least one hostAlias attribute. |
Explanation | The configured host alias contains invalid characters or syntax that is incorrect. |
Action | Update the virtual host element in the server.xml file to either correct or remove the invalid host alias. Note that IPv6 addresses must be enclosed in []. |
Explanation | The specified host alias conflicts with an existing host alias. |
Action | Ensure that all host aliases defined as virtual host elements in the server.xml file are unique. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |