Question
What are possible causes of -140: Bad message command ?
Answer
Based on the details provided in FNP_11.16.3 product documentation (Programming reference guide) and release note for FNP-11.16.3:
If an ISV upgrades the lmgrd and vendor daemon alone, the error that would be observed by an older version (version < 11.16.3) client (when ls_max_connections limit is breached) is: “LM_BADCOMMAND” Error code: “-140” - “A bad command was found in a message”.
On later versions of clients, Once connection limit has reached, the vendor daemon disconnects further connections with error code as
-237(LM_VD_MAX_CLIENTS_REACHED).
This is related to the new vendor variable, ls_max_connections, has been added in FNP-11.16.3, to configure the maximum number of
connections to the vendor daemon at any point in time. It can also be used to prevent the license server from running out of file descriptors.
To configure the maximum number of connections to the vendor daemon at any point in time.
• The default value is 0, indicating that the restriction is disabled.
• The minimum value allowed is 1 and the maximum is 1 000 000.
NOTE:
Kindly be advised that , In 11.16.3.0, the "ls_max_connections" vendor variable was added to lsvendor.c to set the maximum connection on vendor daemon. In FNP-11.16.4, the "ls_max_connections" vendor variable is no longer available in lsvendor.c.
Instead, an option file keyword "MAX_CONNECTIONS" has been introduced to set the maximum connection limit on vendor daemon. This allows the end customers to access the appropriate value for their environments and set the limit appropriately.
So, On non-Windows (POSIX-compliant) platforms, the vendor daemon will consider the minimum value out of the following:
• 'getrlimit()' call will be made once at vendor daemon startup to calculate the system limit for the number of open file descriptors
• the value set for 'MAX_CONNECTIONS'.
>> Connection limit for the vendor daemon. The range is (31 - 10,00,000). The default value is 10,00,000 (if not specified).
Related Articles
Bad message command. / FlexNet Licensing error:-140,10006 12Number of Views Possible causes for duplicates after updating to Snow Inventory Server 6.9.4 176Number of Views Bad Handshake Detected Message in Server Log When Using Java API 5Number of Views Understand “No such file or directory” errors for eth0:0 on modern Linux systems 17Number of Views Common causes of high CPU usage by the ndtrack component of FlexNet inventory agent 407Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago