HTTP
The next table lists all error codes related to the Http[s]ConnectorServlet.
| Major | Minor | Message | Details |
|---|---|---|---|
| HTTP | 0001 | unknown host | Check your configuration (in the web.xml file). |
| 0002 | URLResource_1_0::_cleanup failed | Contact support. | |
| 0003 | could not find all parameters to normalize | Check your configuration (in the web.xml file). | |
| 0004 | SSLConnection_1_0::_cleanup failed while closing the ssl-socket | Contact support. | |
| 0005 | SSLConnection_1_0::_cleanup failed while closing the plain-socket | Contact support. | |
| 0006 | received HTTP status code 407 (proxy authentication required) from outbound proxy | The configured outbound proxy sent HTTP status code 407 (proxy authentication required). Hint: Check the parameters OutboundProxy and OutboundProxyAuthorization of the Http[s]ConnectorServlet. | |
| 0007 | received unknown HTTP status code from outbound proxy. assuming error | The configured outbound proxy sent an unsupported HTTP status code. Check the configuration of the parameter OutboundProxy of the Http[s]ConnectorServlet. | |
| 0008 | connection to <IP>:<port> from local port: <port> failed (<details>). HINT: check the init-params InetAddress, SSLProtocol, SSLCipherSuites, SSLCACertificateFile, SSLCheckPeerHostname, SSLClientCertificateFile, OutboundProxy, and OutboundProxyAuthorization (if applicable) for this Http(s)ConnectorServlet | Check your configuration. Check if your backend is up and running. | |
| 0009 | connection failed. | Check the log file for further details. Check if your backend is up and running. | |
| 0010 | file is empty, but at least one server should be configured. | Check your configuration. | |
| 0011 | can't parse address '%s'. Expected '<host\|inetaddr>:<port>' for ipv4 or '<host>:<port>' for ipv6. | Check your configuration. | |
| 0012 | could not normalize Hostname. | Check your configuration. | |
| 0013 | could not fully normalize Hostname. | Check your configuration. | |
| 0014 | no entry for name (via key) found. | Check the log file for more information. Check that at least one backend is up and running. | |
| 0015 | no entry for name (via state) found. | Check the log file for more information. Check that at least one backend is up and running. | |
| 0016 | received HTTP status code from outbound proxy. Assuming destination host is not available | Make sure that the configured outbound proxy (parameter OutboundProxy) is up and running. | |
| 0017 | PlainConnection_1_0::_cleanup failed | Contact support. | |
| 0018 | parsing timeout/max failed | The backend sent an unknown Keep-Alive header. | |
| 0019 | connection failed. HINT: check the init-param 'InetAddress' or 'OutboundProxy' (if applicable) for this Http(s)ConnectorServlet | Check your configuration. Make sure that the backend is up and running. | |
| 0020 | connection failed. | Check the log file for further details. Check if your backend is up and running. | |
| 0021 | an unexpected exception occurred | Contact support. The logout URI will not be called anymore. | |
| 0022 | an unknown exception occurred | Contact support. The logout URI will not be called anymore. | |
| 0023 | HttpsConnectorServlet_1_0::_cleanup failed | Contact support. | |
| 0024 | configuring 'SSLClientKeyFile' requires also 'SSLClientCertificateFile' | Check your configuration (in the web.xml file). | |
| 0025 | dynamic client certificates (SSLDynamicClientCertificate=true) and a static client certificate (SSLClientCertificateFile) not supported | Check your configuration (in the web.xml file). | |
| 0026 | dynamic client certificates (SSLDynamicClientCertificate=true) and SSL caching (SSLCache=on) is not supported | Check your configuration (in the web.xml file). | |
| 0027 | SSL caching per session (SSLCache=session) and connection pooling (KeepAlive=true) is not supported without KeepAlive.ByClient | Check your configuration (in the web.xml file). | |
| 0028 | dynamic client certificates and connection pooling (KeepAlive=true) only supported if 'KeepAlive.ByClient=true' is set | Check your configuration (in the web.xml file). | |
| 0029 | SSL caching per session (SSLCache=on) and connection pooling by client (KeepAlive.ByClient=true) is not supported | Check your configuration (in the web.xml file). | |
| 0030 | creating an ssl-connection failed | Check the log file for further details. Check if the backend is up and running. | |
| 0031 | get private key failed | Check the log file for further details. Check your SSL certificates and keys. | |
| 0032 | get certificate failed | check the log file for further details. Check your SSL certificates and keys. | |
| 0033 | key not found | Check the log file for further details. Contact support. | |
| 0034 | decoding failed | Check the log file for further details. Contact support. | |
| 0035 | HttpConnectorServlet_1_0::_cleanup failed | Contact support. | |
| 0036 | can not try loadbalancing with only one configured server | Check your configuration (in the web.xml file). At least two backends must be configured for load balancing. | |
| 0037 | you can configure exactly one dynamic InetAddress | Check your configuration (in the web.xml file). | |
| 0038 | couldn't instantiate watchServlet configuration | Check your configuration (in the web.xml file). Also check the log file for further details. | |
| 0039 | couldn't instantiate watchServlet | Check your configuration (in the web.xml file). Also check the log file for further details. | |
| 0040 | invalid config: AwaitingResponse ='false' and KeepAlive='true' not possible | Check your configuration (in the web.xml file). | |
| 0041 | unknown OutboundProxy | Check your configuration (in the web.xml file). | |
| 0042 | removing session provider implementation failed | Contact support. | |
| 0043 | response already commited | Contact support. | |
| 0044 | method not allowed | The HTTP method received from the frontend is not allowed. You can add the method to the parameter AllowedMethods of the HttpConnectorServlet. | |
| 0045 | HttpConnectorServlet_1_0::handleRequest failed (HttpException) | Contact support. | |
| 0046 | HttpConnectorServlet_1_0::handleRequest failed (IOException) | Contact support. | |
| 0047 | Your backend seems to have performance problems or has very long lasting transactions. You may need to set/raise the init-param 'RequestTimeout' for this Http(s)ConnectorServlet | Check your backend. | |
| 0048 | HttpConnectorServlet_1_0::handleRequest failed (BadRequestException) | The frontend sent an invalid request. Check the log file for further details. | |
| 0051 | Can't store state into session | Contact support. | |
| 0052 | could not create Cookie from state | Check the log file for further details. The backend may not receive the stored cookies. | |
| 0053 | unknown path | Check the log file for further details. The backend may not receive the stored cookies. | |
| 0054 | IOException caught during read. HINT: the content provider has problems sending the response, you should inform the application owner | Check the log file for further details. The backend may have closed the connection while the proxy was reading the body, or sent an invalid response the proxy could not parse (for example, a normal response with chunked transfer encoding). | |
| 0055 | incomplete response | Check log for further details. The backend did not send the whole body. | |
| 0057 | illegal providerName | Contact support. | |
| 0058 | state not of type HttpConnectorState | Contact support. | |
| 0059 | upstream server not available | All backends seem to be down while trying to call them with the logout URI. | |
| 0060 | upstream server failed | One backend sent an error while sending the logout URI, and no other backend is available. Check the log file for further details. | |
| 0061 | HttpConnectorServlet_1_0::logout failed | Contact support. | |
| 0062 | gmtime_r failed | Contact support. | |
| 0063 | port missing | Check your configuration (in the web.xml file). | |
| 0064 | dynamic addresses are not supported for this servlet | Check your configuration (in the web.xml file). | |
| 0065 | calling 'retry' failed | Only one backend is configured; a retry call failed. Make sure that the backend is up and running. | |
| 0066 | no entry for name found (StatelessResourceManager) | Check your configuration (in the web.xml file). | |
| 0067 | primary entry= not valid, retry failed | Make sure that the backend is up and running. | |
| 0068 | looped too many times over resources without getting a valid one | Make sure that at least one of the configured backends is up and running. | |
| 0069 | no entry for name found (SessionResourceManager) | Check your configuration (in the web.xml file). | |
| 0070 | single entry is not valid (the backend is down) | Only one backend is configured, which was previously marked as being down and which you still cannot use. This is because the retry timeout period (retryTimeout) has not expired yet. Check in the navajo.log file why the backend was marked as "down". | |
| 0071 | no valid entry found | Make sure that at least one of the configured backends is up and running. | |
| 0072 | entry not valid, retry failed | Make sure that at least one of the configured backends is up and running. | |
| 0073 | invalid param | Check your configuration (in the web.xml file). | |
| 0074 | system::LibManager::openGlobal() failed | Contact support. | |
| 0075 | Exception caught | Contact support. | |
| 0076 | entry already contained | Contact support. | |
| 0077 | calling 'resolve' failed | Check your configuration (in the web.xml file). The configured hostname cannot be resolved. | |
| 0078 | IOException caught during read, websocket connection will be closed | The WebSocket backend sent an error. Check the log file for further details. | |
| 0079 | reading the websocket stream failed | The WebSocket backend may have closed the connection. Check the log file for further details. | |
| 0081 | Poll not supported because there is a filter which doesn't support it in the chain | The parameter Poll of the Http[s]ConnectorServlet can only be "true", if all filters in the chain support simple streaming behavior. If you get this error message, there must be one or more filters in the chain that do not support simple streaming behavior, like, for example, the LuaFilter, the InflateFilter, the DeflateFilter, etc. | |
| 0082 | Enabling SSLCheckPeerHostname also requires setting SSLCACertificateFile. | As the peer hostname check does some additional certificate validation, it requires setting the CA of the peer certificate file. Set the SSLCACertificateFile for the corresponding HttpsConnectorServlet, or enable the previous hostname check behavior via the bc.net.ssl.EnableLegacyHostnameCheck flag. | |
| 0083 | The following error occurred: <cause of error> The parameter'CheckForMultipleIpAddresses will be ignored | An error when using the parameter CheckForMultipleIpAddresses on the Http[s]ConnectorServlet occurred. Consequently, the value of the parameter CheckForMultipleIpAddresses is ignored. For more information, see the log. |