There might be a delay in response from those assets that are affected by the hot deployment of packages because Integration Server blocks the execution of assets that belong to or have dependency on the packages that are being deployed.

While employing the block and wait approach, if there is a long running task, Integration Server waits for the task to complete before attempting hot deployment. If the tasks are not done within the specified timeout period, the hot deployment fails. To make sure that the hot deployment is done successfully, you must configure the hot deployment timeout value to a value more than the time taken for the task to complete.

All ports are associated with packages. During hot deployment, when Integration Server unloads the existing package information from memory, the ports that are associated with these packages are disabled. These ports will be enabled when the packages are activated successfully. Therefore, if you are hot deploying a package that has a port associated with it, access to services using those ports will be affected while the package is reloaded and activated.