Automatic Seat Deactivation

An instance with active floating license seat will attempt to deactivate its seat automatically when the instance ends for any of the following reasons:

• Normal shutdown requested by signal (i.e., SIGTERM)

• Call to process.exit().

• Abnormal shutdown due to uncaught exception or unhandled promise rejection.

Messages like this will appear at stdout and stderr as the instance shuts down to show progress and report errors:

A number of attempts will be made to deactivate.

There are some scenarios where the seat cannot be deactivated automatically:

• Unable to communicate with licensing server at shutdown time – i.e., network problem or outage.

• Power loss.

• Hardware failure/crash.

• Process is force killed -- i.e., SIGKILL.

• In some scenarios, instances running on Windows cannot deactivate automatically, due to Windows’s lack of signals. See Special Considerations for Windows.