Will long running jobs time out if I use an Options file to set the Flexlm Timeout to four hours.

Question

Steven on 9 Feb 2013

1
Link

Direct link to this question

https://au.mathworks.com/matlabcentral/answers/62806-will-long-running-jobs-time-out-if-i-use-an-options-file-to-set-the-flexlm-timeout-to-four-hours

Edited: Walter Roberson on 28 May 2015

If I set the FlexLM timeout function to four hours in my options file, and the users have jobs that run longer than four hours, will the jobs time out?

What constitutes IDLE?

0 Comments
Show -2 older commentsHide -2 older comments

Sign in to comment.

Sign in to answer this question.

Answer 1

Ori on 3 Nov 2013

0
Link

Direct link to this answer

https://au.mathworks.com/matlabcentral/answers/62806-will-long-running-jobs-time-out-if-i-use-an-options-file-to-set-the-flexlm-timeout-to-four-hours#answer_113995

Edited: Walter Roberson on 28 May 2015

License Server receiving / not receiving heartbeats from the client is what constitutes IDLE.

If I understand correctly:

1. Heartbeats are being sent as long as MATLAB is open, hence it is never considered IDLE even during long simulations, and TIMEOUT never elapses.

2. Even after heartbeats cease (e.g. connection to the license server was lost), you still have 2 hours until the license is returned to the pool on the Server side, and the the application is suspended on the client side, not closed.

Ori Kaplan

OpenLM license solutions