Overview

An instance with an active floating license seat attempts to deactivate its seat automatically when the instance ends. Deactivating the seat immediately makes it available to another instance.

When Automatic Deactivation Happens

Automatic deactivation is attempted when the instance ends for any of the following reasons:

• Normal shutdown requested by signal – for example SIGTERM;

• A call to process.exit();

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

Messages like this appear at stdout and stderr as the instance shuts down, showing progress and reporting errors. Several attempts are made to deactivate:

When Automatic Deactivation Cannot Happen

There are scenarios where the seat cannot be deactivated automatically:

• Unable to communicate with the licensing server at shutdown time – a network problem or outage;

• Power loss;

• Hardware failure or crash;

• The process is force killed – for example SIGKILL;

• In some scenarios, instances running on Windows cannot deactivate automatically, because Windows does not support Unix-style signals (see Special Considerations for Windows).