WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


PROX

PROX0050E: Caught unhandled exception from doFilter in filter={0}; exception={1}.
Explanation The identified filter failed to handle an event. A proxy-internal error response will be built.
Action Review the log for related reasons as to why the filter failed. If the problem persists, contact the filter's vendor.
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 for related reasons as to why the filter failed. If the problem persists, contact the filter's vendor.
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 the error page application URI is located in an available webmodule 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 can not 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 the specified custom property has been successfully processed by the proxy.
Action None.
PROX0056I: The custom property {0} with the value {1} is recognized but not active on the proxy.
Explanation Indicates the specified custom property has been recognized by the proxy, but the proxy must be restarted 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 can not 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 can not be parsed
Action Make sure 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 can not start with this condition.
Action Either disable proxy server caching, or ensure the proxy server's object cache is configured to enable NIO support.
PROX0060I: HTTP Proxy has informed the load balancer of readiness.
Explanation The HTTP Proxy is successfully responding to load balancer inquiries.
Action None
PROX0061I: HTTP Proxy quiesce started.
Explanation The HTTP Proxy received a start quiesce request.
Action None
PROX0062I: HTTP Proxy quiesce completed.
Explanation The HTTP Proxy quiesce is completed.
Action None
Reference topic    

Terms of Use | Feedback

Last updated: Feb 18, 2011 4:35:06 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.proxy.filter.resources.filter.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)