Summary

This article describes the only method for avoiding or reducing timeouts when receiving the LM_HOSTDOWN error

Synopsis

Following situation:

A server with features F1, F2, F3, F4, F5, F6, F7, F8, F9

A user has borrowed 5 features: F1, F3, F5, F7, F9

User disconnects and starts the application. The application has 9 features, 5 of them are borrowed (valid), the other 4 are not borrowed and cannot be checked out because user is offline (invalid).

To validate the 9 features I need to check out them. On 4 of them (F2, F4, F6, F8) I would get a LM_HOSTDOWN error after a timeout, the other 5 can be checked out, because they are borrowed.

The problem is that the application will await the timeout 4 times, which is unnecessary. In some cases there are more than 30 unvailable features and only some are borrowed, then the application is waiting a long long time.

I could cancel the validation at the first LM_HOSTDOWN error, but then I would not get the other features which are borrowed.

How can this be solved?

I want the timeout appear exactly once, but I still want to validate all the borrowed features.

Discussion

The Windows only option 'FLEXLM_TIMEOUT' would allow you to minimize the timeout when attempting to connect to the license server. More information on this is available in the License Administration Guide for each version of FlexNet Publisher. This value controls the 10 second timeouts that you have observed and can be set in microseconds from 0 to 2,146,483,647. Please be aware that the use of this option will affect all vendors on your license server.