This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Connection timeout with unreachable server
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 02, 2010
03:25 AM
Connection timeout with unreachable server
Hi
When testing a license key with
Is there any switch or option to lower this connection timeout? I found ls_conn_timeout, but this is set to 20 sec by default, but I observed far longer blocking times.
When testing a license key with
lc_checkout(job, feat, ver, 1, LM_CO_LOCALTEST, &vcode, LM_DUP_NONE)the application oftentimes blocks for more than one minute if the specified license server is not reachable. But it returns immediately, if there is no network connection at all, i.e., if the network cable is physically unplugged.
Is there any switch or option to lower this connection timeout? I found ls_conn_timeout, but this is set to 20 sec by default, but I observed far longer blocking times.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 02, 2010
06:38 AM
I am facing a similar issue with lc_heartbeat() call. When the network goes down, then sometimes this call never returns. I have been communicating with FlexEra from the past 8 months but still no progress.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 09, 2010
08:01 AM
Check out the documentation for TCP_NODELAY. It tends to fix this issue but it has some drawbacks (and probably to more than just your application).
I see this behavior quite often. It is just normal networking timeouts when trying to connect to a machine that is supposed to be there but isn't responding. You'll probably see the same types of delays with ping, rsh, etc.
I see this behavior quite often. It is just normal networking timeouts when trying to connect to a machine that is supposed to be there but isn't responding. You'll probably see the same types of delays with ping, rsh, etc.