Problem

According to the documentation, for every endpoint configuration, there are two timeouts properties that can be configured:

HTTP Connection Timeout

Number. Optional. The time interval (in seconds) after which a connection attempt will timeout. If a value 0 is specified (or if the value is not specified), Mediator will use the value specified in the Connection Timeout field (in the Integration Server Administrator, go to Settings > Extended). Default: 30 seconds.

Read Timeout

Number. Optional. The time interval (in seconds) after which a socket read attempt will timeout. If a value 0 is specified (or if the value is not specified), Mediator will use the value specified in the Read Timeout field (in the Integration Server Administrator, go to > Settings > Extended.). Default: 30 seconds.

BOTH are defined in the same way in the documentation regarding the possible values and their default values.

By the other hand, PluggableUI by default sets:

Endpoint properties - HTTP Properties

HTTP connection timeout: <empty>

Read timeout: <empty>

Currently this is just for Virtual Services and obviously not for Virtual REST Services which can’t be managed from this UI (but it was the same in the past old versions).

HOWEVER, BusinessUI is setting In Routing Endpoints (for Virtual Services and Virtual REST services), for any kind of routing, the timeouts as:

HTTP Connection Timeout (seconds) == 30

Read Timeout (seconds) == <empty>

However, this behavior (the value of HTTP Connection Timeout is always filled with 30), implies that the default value configured in pg.endpoint.connectionTimeout on mediator is not used, and force the user to get into the endpoint properties and change that value.