PROX0054W=PROX0054W: Routing Rule {0} will be ignored. All of the required elements of the specified routing rule are not completely defined and cannot be routed to. Make sure a URI Group, virtual host, and routing action are specified in this routing rule. PROX0064I=PROX0064I: Filters deployed by the proxy are listed below in execution order by protocol and filter point: {0} All of the installed filters are displayed. None PROX0063W=PROX0063W: A filter named {0} does not exist. Indicates an attempt was made to modify a filter that does not exist. Ensure the filter name was typed correctly. Also, filter names are case sensitive. PROX0069W=PROX0069W: The static routing file directory is not set and static routing is enabled. 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. Review the configuration and set the static file routing directory to a valid directory that contains the exported static routing XML file. PROX0053W=PROX0053W: Problems occurred while creating error logs. No logging will occur due to the unhandled event. Make sure the specified log file name(s) are valid and accessible. PROX0073I=PROX0073I: HTTP Proxy quiesce completed. The HTTP Proxy quiesce is completed. None PROX0059E=PROX0059E: Object cache instance {0} is not properly configured for proxy-cache use. The proxy server requires a specific configuration for its object cache. The proxy server cannot start with this condition. Either disable proxy server caching, or ensure the proxy server object cache is configured to enable NIO support. PROX0068W=PROX0068W: The specified time mapping could not be converted to a valid time object. A value that was not valid was provided that prevented the time mapping from being converted into a valid time. 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. PROX0052W=PROX0052W: Problems occurred while handling error page application URI. Error Page URI={0} A host for the error page application could not be found. Make sure that the error page application URI is located in an available Web module or routing rule. PROX0072I=PROX0072I: HTTP Proxy quiesce started. The HTTP Proxy received a start quiesce request. None PROX0058W=PROX0058W: The following rewrite rule is improperly formatted and will not be active - FROM URL PATTERN: {0} TO URL PATTERN: {1} Indicates one or both of the supplied URL patterns cannot be parsed Make sure that the patterns do not contain any typos and are formatted according to RFC 2396 PROX0062I=PROX0062I: The ordinal of filter: {0} was set to: {1} A filter's ordinal was modified. None. PROX0061W=PROX0061W: Filter: {0} is internal and cannot be modified. Indicates a user incorrectly attempted to modify an internal filter. Only custom filters can be modified. None. PROX0067W=PROX0067W: The method {0} was unable to complete successfully due to an argument that is not valid: {1} A value that was not valid was provided that caused the method to fail. Review mbean command and use correct argument(s). PROX0071I=PROX0071I: HTTP Proxy has informed the load balancer of readiness. The HTTP Proxy is successfully responding to load balancer inquiries. None PROX0057W=PROX0057W: The URL {0} from is improperly formatted and cannot be parsed. A URL received from a server is not formatted according to RFC 2396. Correct the format of the specified URL. PROX0051E=PROX0051E: Caught unhandled exception from doFilter in filter={0}; exception={1}. The identified filter failed to handle an event. No error response will be built because the response is already committed. Review the log file for related reasons as to why the filter failed. If the problem persists, contact the vendor for the filter. PROX0070W=PROX0070W: The static routing file directory does not contain any files and static routing is enabled. 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. 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. PROX0060I=PROX0060I: The filter {0} has the following filter initialization custom property set: {1} {2} Indicates a filter initialization custom property recognized by the proxy was set. None. PROX0066I=PROX0066I: No filters are available to be displayed. Indicates no filters are available to be displayed for the specified filter protocol(s) and filter point(s). None PROX0050E=PROX0050E: Caught unhandled exception from doFilter in filter={0}; exception={1}. The identified filter failed to handle an event. A proxy server internal error response will be built. Review the log file for related reasons as to why the filter failed. If the problem persists, contact the vendor for the filter. PROX0056I=PROX0056I: The custom property {0} with the value {1} is recognized but not active on the proxy. 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. Restart the proxy server if you require the custom property value to be operational at this time. PROX0065I=PROX0065I: A subset of the filters deployed by the proxy are listed below in execution order by protocol and filter point: {0} Filters are being displayed based on the protocol and filter point specified. None PROX0055I=PROX0055I: The custom property {0} with the value {1} is recognized and active on the proxy. Indicates that the specified custom property has been successfully processed by the proxy server. None.