PROX

PROX0000I: {0} deployment recognized with configuration root={1}.

Explanation

The proxy server will attempt to load its configuration from the specified location.

Action

No action is required.

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 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.

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

PROX0101I: Proxy Server being started as {0}.

Explanation

The proxy server has started with the specified deployment type specified

Action

No user action is required for this type of message

PROX0102I: The proxy channel chains {0} have been started.

Explanation

The channel chains that are identified by channel chain group have been started. The proxy server will receive requests on the associated ports.

Action

No user action is required for this type of message

PROX0107W: The proxy-environment.xml file in the cell-scope could not be located.

Explanation

This configuration document contains the cell-wide definitions for the proxy server configuration. The file is missing or corrupted. This warning message could be ignored if generic server routing rules are not defined.

Action

Review the proxy server creation. Contact the 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 document contains the cluster and server definitions for the proxy server configuration. The file is missing or corrupted.

Action

Review the proxy server creation. Contact the vendor if the configuration has not been customized.

PROX0109W: The trusted security proxy host name/ip address {0} created an exception.

Explanation

The proxy server received an exception when converting the text host name or ip address to an InetAddress object.

Action

Configure the proxy server to use trusted security proxies by adding hostnames or ip addresses. Separate multiple entries on one line with a space or comma.

PROX0110I: The server at {0} is a trusted security proxy.

Explanation

The Proxy Server is configured to recognize the identified server as a trusted intermediary.
Special request headers received from that server will be forwarded to the application server.

Action

No user action is required.

PROX0111I: The Proxy Server will retry socket connection to target {0}. Retry count {1}, retry limit {2}. An attempt to establish a socket connection failed with exception {3}.

Explanation

The http.connectRetryLimit custom property is used to configure the Proxy Server to retry failed socket connections.

Action

No user action is required unless you want to disable the configuration setting.

PROX5200E: Error loading command {0}: {1}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

PROX5201E: Proxy server not supported on node specified in command

Explanation

The proxy server is only supported on nodes that are at WebSphere Application Server Network Deployment V6.0.2 or a higher version.

Action

Add a new WebSphere Application Server V6.0.2 or higher node using the command utilities that are provided and augment the profile for that node to include the proxy server templates. Use that node to create a proxy server.

PROX5202E: On Demand Router not supported on node specified in command

Explanation

The On Demand Router is only supported on WebSphere Application Server XD nodes.

Action

Add a WebSphere Application Server XD node and use that node to create the On Demand Router.

PROX5203E: This command is only valid for secure proxy servers.

Explanation

The security level can only be displayed or modified for a secure proxy server that was created as part of a secure proxy profile.

Action

Re-issue the command specifying a server that is a secure proxy server.

PROX5204E: An invalid value was specified for the security level parameter.

Explanation

Valid values for the security level are high, medium and low

Action

Re-issue the command specifying a valid security level.

PROX5205E: This command is only valid for secure proxy server profiles.

Explanation

Only a secure proxy server profile can be imported with this command.

Action

Re-issue the command on a secure proxy profile.

PROX5206E: This command is only valid for secure proxy servers.

Explanation

Only a secure proxy server can be imported with this command.

Action

Re-issue the command on a secure proxy server.

PROX6101E: The custom advisor mapping type is missing.

Explanation

The custom advisor mapping type is not defined.

Action

Ensure that the type field in options step is defined. The type value is case sensitive.

PROX6102E: The cluster name is not defined in the generic cluster mapping.

Explanation

The cluster name is needed for the generic cluster mapping.

Action

Review the configuration and ensure that a valid generic cluster name is provided.

PROX6103E: The cluster name is not defined in the cluster mapping.

Explanation

The cluster name is needed for the cluster mapping.

Action

Review the configuration and ensure that a valid cluster name is provided.

PROX6104E: The cluster name is not defined in the cluster mapping.

Explanation

The cluster name is needed for the cluster mapping.

Action

Review the configuration and ensure that a valid cluster name is provided.

PROX6105E: The cell, node and server name are not defined in the application server mapping.

Explanation

The cell name, node name and server name are required for the application server mapping.

Action

Review the configuration and ensure that a valid cell name, node name and server name are provided.

PROX6106E: The application name is not defined in the application server mapping.

Explanation

The application name is required for the application server mapping.

Action

Review the configuration and ensure that a valid application name is provided.

PROX6107E: The mapping type for the custom advisor is not valid..

Explanation

The mapping type for the custom advisor is not valid. Valid values are GSC, Cluster and AppServer.

Action

Review the configuration and ensure that a valid mapping type for the custom advisor is provided.