Express (Distributed operating systems), v8.0 > Reference > Messages
PROX
PROX0050E: Caught unhandled exception from doFilter in filter={0}; exception={1}.
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.
PROX0051E: Caught unhandled exception from doFilter in filter={0}; exception={1}.
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.
PROX0052W: Problems occurred while handling error page application URI. Error Page URI={0}
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.
PROX0053W: Problems occurred while creating error logs.
Explanation No logging will occur due to the unhandled event. Action Make sure the specified log file name(s) are valid and accessible.
PROX0054W: Routing Rule {0} will be ignored.
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.
PROX0055I: The custom property {0} with the value {1} is recognized and active on the proxy.
Explanation Indicates that the specified custom property has been successfully processed by the proxy server. Action None.
PROX0056I: The custom property {0} with the value {1} is recognized but not active on the proxy.
Explanation Indicates that the specified custom property is recognized by the proxy server, but 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.
PROX0057W: The URL {0} from is improperly formatted and cannot be parsed.
Explanation A URL received from a server is not formatted according to RFC 2396. Action Correct the format of the specified URL.
PROX0058W: The following rewrite rule is improperly formatted and will not be active - FROM URL PATTERN: {0} TO URL PATTERN: {1}
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
PROX0059E: Object cache instance {0} is not properly configured for proxy-cache use.
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.
PROX0060I: The filter {0} has the following filter initialization custom property set: {1} {2}
Explanation Indicates a filter initialization custom property recognized by the proxy was set. Action None.
PROX0061W: Filter: {0} is internal and cannot be modified.
Explanation Indicates a user incorrectly attempted to modify an internal filter. Only custom filters can be modified. Action None.
PROX0062I: The ordinal of filter: {0} was set to: {1}
Explanation A filter's ordinal was modified. Action None.
PROX0063W: A filter named {0} does not exist.
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.
PROX0064I: Filters deployed by the proxy are listed below in execution order by protocol and filter point: {0}
Explanation All of the installed filters are displayed. Action None
PROX0065I: A subset of the filters deployed by the proxy are listed below in execution order by protocol and filter point: {0}
Explanation Filters are being displayed based on the protocol and filter point specified. Action None
PROX0066I: No filters are available to be displayed.
Explanation Indicates no filters are available to be displayed for the specified filter protocol(s) and filter point(s). Action None
PROX0067W: The method {0} was unable to complete successfully due to an argument that is not valid: {1}
Explanation A value that was not valid was provided that caused the method to fail. Action Review mbean command and use correct argument(s).
PROX0068W: The specified time mapping could not be converted to a valid time object.
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.
PROX0069W: The static routing file directory is not set and static routing is enabled.
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.
PROX0070W: The static routing file directory does not contain any files and static routing is enabled.
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.
PROX0071I: HTTP Proxy has informed the load balancer of readiness.
Explanation The HTTP Proxy is successfully responding to load balancer inquiries. Action None
PROX0072I: HTTP Proxy quiesce started.
Explanation The HTTP Proxy received a start quiesce request. Action None
PROX0073I: HTTP Proxy quiesce completed.
Explanation The HTTP Proxy quiesce is completed. Action None