WebSphere Proxy messages

PROX0000I: {0} deployment recognized with configuration root={1}.
Explanation: The proxy will attempt to load its configuration from the specified location.
User Response: None.

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.
User Response: 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.
User Response: Review the log for related reasons as to why the filter failed. If the problem persists, contact the filter's vendor.

PROX0052E: Problems occurred while handling error page application URI. Error Page URI={0}
Explanation: A host for the error page application could not be found.
User Response: Make sure the error page application URI is located in a configured webmodule or in a URIGroup if it is not located on an application server.

PROX0101I: Proxy Server being started as {0}.
Explanation: The proxy has started with the deployment type specified
User Response: No user action for this type of message

PROX0102I: The proxy channel chains {0} have been started.
Explanation: The channel chains identified by channel chain group has been started. The proxy will receive requests on the ports associated.
User Response: No user action for this type of message

PROX0103W: The proxy routing rule {0} does not have an action; This rule will not be considered for routing.
Explanation: The identified rule does not have a valid routing action.
User Response: Review the Proxy server/cluster configuration and associate a valid routing action with this Routing rule.

PROX0104W: The proxy routing rule {0} does not have a valid virtual host alias; This rule will not be considered for routing.
Explanation: The identified rule does not have a valid virtual host alias.
User Response: Review the Proxy server/cluster configuration and associate a valid virtual host alias with this Routing rule.

PROX0105W: The proxy routing rule {0} does not have an valid uri group; This rule will not be considered for routing.
Explanation: The identified rule does not have a valid uri group.
User Response: Review the Proxy server/cluster configuration and associate a valid uri group with this Routing rule.

PROX0106W: The URI group {0} does not have valid pattern(s); This group will not be available.
Explanation: The identified group does not have valid pattern(s).
User Response: Review the Proxy environment configuration and associate valid patterns with this URI group.

PROX0107W: The proxy-environment.xml file in the cell-scope could not be located.
Explanation: This configuration doucument contains the cell-wide definitions for proxy configuration. The file is missing or corrupted.
User Response: Review the Proxy server creation. Contact vendor if the configuration has not been customized.

PROX0108W: The proxy-settings.xml file in the cluster/server-scope could not be located.
Explanation: This configuration doucument contains the cluster/server definitions for proxy configuration. The file is missing or corrupted.
User Response: Review the Proxy server creation. Contact vendor if the configuration has not been customized.

PROX5000I: IBM WebSphere Validation
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5001I: IBM WebSphere Proxy Environment Validation
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5004W: Failed to recognize object of type {0}
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5011E: The uri group {0} does not have any URI patterns.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5013E: A URI pattern, on the URI Group {0}, is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5015E: The name of a Generic Server cluster in {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5017E: The Peer Access Point name in a Remote cell override in {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5019E: The URI group name in a URI group defined in {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5021E: The generic server endpoint hostname in a generic server endpoint defined in {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5023E: The generic server endpoint port in {0} is out of range.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5025E: A generic server cluster with the name: {0} already exists.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5027E: A remote cell override with the name: {0} already exists.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5029E: A URI group with the name: {0} already exists.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5031E: The Generic server cluster {0} does not have any members.
Explanation: The cluster needs to have valid members in order for the proxy to route to the cluster.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5033E: The cluster member in {0} has a workload management weight that is too low.
Explanation: The cluster member weight should be between 0 and 20.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5035E: The cluster member in {0} has a workload management weight that is too high.
Explanation: The cluster member weight should be between 0 and 20.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5100I: IBM WebSphere Validation
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5101I: IBM WebSphere Proxy Environment Validation
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5104W: Failed to recognize object of type {0}
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5111E: The name for a routing rule in {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5113E: A route action for the rule {0} is absent.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5115E: A peer access point (representing a websphere cell) is needed for the cell route action in {0}.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5116E: A generic server cluster name is needed for the generic server cluster route action in {0}.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5117E: A redirect url is needed for the redirect route action in {0}.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5119E: A uri group name is required for the static cache rule in {0}.
Explanation: No additional information is available.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5121W: A proxy route action has both generic cluster {0} and websphere cell {1} specified.
Explanation: The proxy server can only route to either a generic cluster or a websphere cell for a specific routing rule. By default it will route to the websphere cell.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5123E: The peer access point name specified in the route action {0} is invalid or does not exist.
Explanation: A remote websphere cell must be configured with a valid peer access point in the coregroup bridge service for the proxy to route to the cell.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.

PROX5125E: The peer access point name specified in the route action {0} is invalid or does not exist.
Explanation: A generic server cluster must be configured with a valid name in the proxy configuration for the proxy to route to the cell.
User Response: Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.