Explanation | The identified filter failed to handle an event. A proxy server internal error response will be built. |
Action | Review the log file for related reasons as to why the filter failed. If the problem persists, contact the vendor for the filter. |
Explanation | The identified filter failed to handle an event. No error response will be built because the response is already committed. |
Action | Review the log file for related reasons as to why the filter failed. If the problem persists, contact the vendor for the filter. |
Explanation | A host for the error page application could not be found. |
Action | Make sure that the error page application URI is located in an available Web module or routing rule. |
Explanation | No logging will occur due to the unhandled event. |
Action | Make sure the specified log file name(s) are valid and accessible. |
Explanation | All of the required elements of the specified routing rule are not completely defined and cannot be routed to. |
Action | Make sure a URI Group, virtual host, and routing action are specified in this routing rule. |
Explanation | Indicates that the specified custom property has been successfully processed by the proxy server. |
Action | None. |
Explanation | Indicates that the specified custom property is recognized by the proxy server, but you must restart the proxy server for this value to become active. |
Action | Restart the proxy server if you require the custom property value to be operational at this time. |
Explanation | A URL received from a server is not formatted according to RFC 2396. |
Action | Correct the format of the specified URL. |
Explanation | Indicates one or both of the supplied URL patterns cannot be parsed |
Action | Make sure that the patterns do not contain any typos and are formatted according to RFC 2396 |
Explanation | The proxy server requires a specific configuration for its object cache. The proxy server cannot start with this condition. |
Action | Either disable proxy server caching, or ensure the proxy server object cache is configured to enable NIO support. |
Explanation | Indicates a filter initialization custom property recognized by the proxy was set. |
Action | None. |
Explanation | Indicates a user incorrectly attempted to modify an internal filter. Only custom filters can be modified. |
Action | None. |
Explanation | A filter's ordinal was modified. |
Action | None. |
Explanation | Indicates an attempt was made to modify a filter that does not exist. |
Action | Ensure the filter name was typed correctly. Also, filter names are case sensitive. |
Explanation | All of the installed filters are displayed. |
Action | None |
Explanation | Filters are being displayed based on the protocol and filter point specified. |
Action | None |
Explanation | Indicates no filters are available to be displayed for the specified filter protocol(s) and filter point(s). |
Action | None |
Explanation | A value that was not valid was provided that caused the method to fail. |
Action | Review mbean command and use correct argument(s). |
Explanation | A value that was not valid was provided that prevented the time mapping from being converted into a valid time. |
Action | Review the time mapping configuration and specify a valid time. Hours are represented between 0-23 inclusive and minutes between 0-59 inclusive. For example, 10:30. |
Explanation | When static routing is enabled, the static routing file directory must be set to a valid directory that contains the exported static routing XML file. |
Action | Review the configuration and set the static file routing directory to a valid directory that contains the exported static routing XML file. |
Explanation | When static routing is enabled, the static routing file directory must contain the exported XML routing files or the proxy will fail to route requests. |
Action | Review the configuration and ensure the static routing file directory contains one or more XML files generated from the TargetTreeMbean on the Deployment Manager of the target cells. |
Explanation | The HTTP Proxy is successfully responding to load balancer inquiries. |
Action | None |
Explanation | The HTTP Proxy received a start quiesce request. |
Action | None |
Explanation | The HTTP Proxy quiesce is completed. |
Action | None |