Looking in the DM development guide it says to change the default session timeout use for example <Session id="1" timeout="2000"> (millliseconds).
I have tried using, for example 60000 for 1 min but it does not make any difference to the default timeout which seems to be around 30 seconds.
Is there anything else that stopping this parameter having an effect? How can I increass the timeout?
Hi John,
the Session@timeout attribute configures the timeout for a request in this session and overrides the Timeout of a single command (ms) in the element edit wizard (under More TCP/IP settings for the connection).
This setting can be overruled by the Session/Connection@timeout attribute, which specifies the timeout for a connection in the session.
In Stream Viewer, you should see that a retry of the request happens (in case no response was received) after the specified timeout time.
You mention that you observe a timeout after around 30s. I'm assuming you are referring to the element timeout as this is by default 30s (This can be configured in the The element goes into timeout state when it is not responding for (sec) setting under More TCP/IP settings for that connection). The element goes into timeout after the time it first observed a command timeout + the duration configured in the element timeout setting. E.g. suppose you have Session/Connection@timeout set to 10000 and use the default element timeout (30s), then the element would go into timeout 40s after sending the request if no response was received.
Another reason why it could appear not to work is when no retry is performed as DataMiner considers to have received a response. This is e.g. the case when you receive a response with a status code in the 4xx or 5xx range (for more information, see here) which would result in the element to go into timeout.
Do you see a retry being performed in Stream Viewer? If so, after what period do you see the retry being performed? What version of DataMiner are you using?