Timeout fetching XML-Schema for Validation
Hi all,
we are using XSD Schemas to validate SOAP Requests in the following way:
The schema URL will be something like https://host/path/to/file.xsd
Everytime the Parse-XML rule runs the XSD Schema will be fetched from the other server. Due to a bug in the network configuration the XSD providing server won't respond to us.
This causes Pega to wait (forever? we cancelled our tests after 10 minutes) and our service consumers will timeout due to not receiving a response from us.
The solution to the problem is obviously to fix the bug in the network configuration.
Nevertheless I am very curious and want to know if there's a way to configure how long the parse rule will wait for the schema before it aborts with an error message?
Hi all,
we are using XSD Schemas to validate SOAP Requests in the following way:
The schema URL will be something like https://host/path/to/file.xsd
Everytime the Parse-XML rule runs the XSD Schema will be fetched from the other server. Due to a bug in the network configuration the XSD providing server won't respond to us.
This causes Pega to wait (forever? we cancelled our tests after 10 minutes) and our service consumers will timeout due to not receiving a response from us.
The solution to the problem is obviously to fix the bug in the network configuration.
Nevertheless I am very curious and want to know if there's a way to configure how long the parse rule will wait for the schema before it aborts with an error message?
Accepted Solution
Pegasystems Inc.
US
From SR-131634, an enhancement request has been entered for a configurable timeout when fetching a schema in XML validation.
Thanks Hari Kumar! Hari pointed out a solution using 'when' rule field under 'XML validation' may be it could be used to determine whether URL is up or not. If URL is not accessible then don't proceed further with the XML validation; fail sooner. From the exception stack trace, It can found out whether when rule called before the URL access or not. If when rule is called before accessing the URL then this suggestion can be used as local change. Downside is that extra check for the validity of URL for each call.
Infosys
US
Hello Gopinathan,
your idea sounds doable. The extra check for each call is something I wouldn't like too much. As there is no such setting on the rule form level I was hoping to learn about a setting in one of the configuration xml files.
If there is no further suggestion we might try to implement your proposed solution. Additionally I'll open an SR and reference it here.
Thank you so far
Pegasystems Inc.
US
It is reasonable to expect PRPC to timeout in a reasonable amount of time while attempting to get a schema document.
I suspect we should be able to implement a default timeout of a few minutes and then provide a dynamic system setting for tweaking it.
Pegasystems Inc.
US
Thanks John. We'll track this and when it comes to resolution, circle back and see if we can capture it here for the benefit of other members.
Pegasystems Inc.
US
Are you sure the schema-providing server NEVER responds? I remember reading that some (popular public) sites explicitly delay the response when a DTD or a schema is requested (because of otherwise excessive traffic and to encourage HTTP caching practices).
Infosys
US
Hello Ora,
in our case the schema-providing server actually does respond but due to a bug in the firewall that response never arrives at our Pega instance. Therefor we would have waited forever.
The bug in the firewall has been resolved and we are able to continue our work. Nevertheless, my support request has been converted to an enhancement request which is still in evaluation.
Accepted Solution
Pegasystems Inc.
US
From SR-131634, an enhancement request has been entered for a configurable timeout when fetching a schema in XML validation.