Introduction
This article is intended to offer some hints as to why there may be a crash in the LLS. It is not an exhaustive list of reasons but it may give some indication as to why there is a crash.
Use Case 1: JVM out of memory.
The local license server uses a JVM. It is possible that with a high volume of requests to the server, the JVM memory allocation is exhausted and there is the possibility that the server crashes. This is an unlikely scenario as the JVM will usually perform garbage collection and free up memory. Ideally, the server should be used on a machine that has a high allocation of memory that is available to the JVM through JVM settings.
Use Case 2: LLS Database grows significantly large
It has been seen that in certain situations the LLS can consume large amounts of disk space. This may be when usage is collected on the server but not synced to the back office. If the DB grows sufficiently large and there is not enough room on the disk, the server could crash.
Again this is an unlikely occurrence and is mitigated by synching the usage records with the back office or by using a sufficiently large disk.
Use Case 3: DB corruption
This is an issue that occurs when there is a hard power event on the server machine. It is possible that the server is writing information to the database and power is lost on the machine. IT has been seen that this can result in a corruption of the database and a crash when the server starts up again.
This can be mitigated by enabling the database backup functionality of the server. This will take regular backups of the database and allow you to restore the DB in the event of corruption.
Use Case 4: Virus scanner or endpoint scanner
It is sometimes possible that a virus scanner or security endpoint scanner could interpret some of the functionality of the LLS as a potential cause for alarm and prompt the user to allow or disallow. Disallowing could, potentially, cause the LLS to stop working as it is not able to perform some of its tasks correctly. It is advised to allow the LLS in virus scans or endpoint scans.
More Information
As mentioned this is not an exhaustive list and more use cases will be added to this as more are reported
Related Articles
How Many Reservation Lists Can The Local License Server Manage? 5Number of Views Local License Server Service Error - Error 1067: The Process Terminated Unexpectedly 35Number of Views How to Change the FlexNet Embedded Windows Local License Server Wrapper Logs Location 11Number of Views How to Acquire and Return a License from the Local License Server 10Number of Views Java Reporting in Revenera Usage Intelligence 10Number 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. | |
Case id: 00001065
Activity: Status change: 2 hours ago