.NET Open Client: It is not possible to change the HTTP Timeout between requests

Changes to the Progress.Session.HttpTimeout runtime property do not take effect if the change is made after the AppObject and its related connection object have been created. So it is not possible to change the HTTP Timeout value for a specific request.

Aug 15, 2023
Knowledge

Title

URL Name

NET-Open-Client-It-is-not-possible-to-change-the-HTTP-Timeout-between-requests

Article Number

000239761

Environment

Product: OpenEdge Version: All supported versions OS: All supported platforms Other: .NET Open Client

Question/Problem Description

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

This is expected behavior. The properties defined through the "Progress.Open4GL.RunTimeProperties" class are only picked up when the AppObject is instantiated, so changing the values of these properties after the AppObject has been instantiated has no effect.

Resolution

It was determined that the Progress Product is functioning as designed.

An enhancement to the product can be requested through the Progress Community via an Ideas submission. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.

For detailed information on how to submit an Idea, please refer to Article How to submit an enhancement request for a Progress product?.

As an alternative use the workaround below.

Workaround

The following workaround is only applicable to the Session-Free connection model (e.g. conn.SessionModel = 1).

Set the Progress.Open4GL.DynamicAPI.IPoolProps_Fields.HTTP_TIMEOUT property for the Connection object before executing the request. Make sure that the minimum connections for the connection pool is set to 0 (this is the default value). Then the HTTP client will get rebuilt on each request and the changes to the HTTP timeout value should take affect.

Sample code:

// Set HTTP Timeout to 1 minute
Progress.Open4GL.RunTimeProperties.SetIntProperty("PROGRESS.Session.HttpTimeout", 60);

conn = new Connection("http://hostname:8810/apsv"", null, null, null);
conn.SessionModel = 1;
conn.MinConnections = 0;
 
appObj = new OpenAppObject(conn, "foo");
 
appObj.runProcedure("ping.p", new ParameterSet(0));

// Set HTTP Timeout to 5 minutes before running a long running request
conn.SetStringProperty(Progress.Open4GL.DynamicAPI.IPoolProps_Fields.HTTP_TIMEOUT, "300");

appObj.runProcedure("ping.p", new ParameterSet(0));

// Reset HTTP Timeout back to 1 minute
conn.SetStringProperty(Progress.Open4GL.DynamicAPI.IPoolProps_Fields.HTTP_TIMEOUT, "60");

Notes

References to Other Documentation:

.NET Open Clients, PROGRESS.Session.HttpTimeout
https://docs.progress.com/de-DE/bundle/openedge-dotnet-open-clients/page/PROGRESS.Session.HttpTimeout.html

Progress Article(s):
.NET Open Client request to Application Server times out after 100 seconds

Keyword Phrase

Last Modified Date

8/15/2023 1:37 PM

.NET Open Client: It is not possible to change the HTTP Timeout between requests

Files(0)

Was this article helpful?

Was this article helpful?

.NET Open Client: It is not possible to change the HTTP Timeout between requests

Information

Related Articles