Hi baalbaki,

It seems that the two environments have different network infrastructures or anyway with substantially different behavior when shutting down a Lightstreamer server.

In the first case, the client immediately detects the disconnection of the client session and correctly throws a PushConnException and signals the unsubscription of all active subscriptions.
In the second case, however, the client does not immediately detect the disconnection but the session simply becomes silent.
After the proper timeout the session goes into the Stalled state. Then once the PushServerException is received, that is considered a serious error.

In any case is the application that must take the necessary actions to create a new session (and new subscriptions).

Regards,
Giuseppe