webMethods Knowlegebase : Mediator returning read timeout error when a Partner invokes a Virtual service upgraded to v9.12 (1792841)

Problem

Recently migrated from version 9.6 to v9.12.

Getting a lot of read timeout errors when calling the migrated Virtual services after upgrading to version 9.12.

Increased the read timeout on the Virtual service at the routing protocols screen on endpoint settings.

Also set the read timeout to 60 seconds, but still seeing timeout errors.

It seems the native service on the webMethods Integration server is timing out.

Have the following extended settings set on Integration Server, but they are not being honored:

watt.net.maxClientKeepaliveConns=60

watt.net.timeout=600

watt.server.SOAP.request.timeout=-1

The timeout occurs after 40 seconds on the Partner side.

Integration pattern is Partner => RI => IS (Mediator) => Internal VIP (IS in application cluster which has native WSD).

The error seen is as follows:

"2017-10-02 14:28:21 EDT [MED.0050.0674D] [MED4020145085-867] Native service executed in 30,139 millisecond(s) for this transaction

2017-10-02 14:28:21 EDT [MED.0050.0684D] [MED4020145085-867] Mediator has received the response from the native service.

2017-10-02 14:28:21 EDT [MED.0110.0028E] [MED4020145085-867] <-- Proxy service: retrieveEmploymentRecordsVS(1.0). Error in the Mediator outbound client. Read timed out

org.apache.axis2.AxisFault: Read timed out

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at com.wm.app.b2b.server.wss.HTTPTransportSender.makeFault(HTTPTransportSender.java:1163)

at com.wm.app.b2b.server.wss.HTTPTransportSender.writeMessageWithWebM(HTTPTransportSender.java:608)

. . . ."