Delay after connection_reestablished before OPCUAClient.isReconnecting is back to false about node-opcua HOT 4 CLOSED

@ePluvinage the current behavior is that the client.isReconnecting flag goes back to true straight after the "connection_reestablished" event is raised.
Let's change the behavior as you suggested as it make more sense that isReconnecting=true at the time the connection_reestablished event is raised.

from node-opcua.

connection_reestablished only signifies that the secure channel has been re-established. However, the session may still need to be restored at this stage. There is much more to do to reestablish a session, rebuild the subscription, and reinstate the monitored items; only then is the reconnection process completed.

It would be best if you listened to the events emitted by the session

  // session_restored is raised when the session and related subscription
  // have been fully repaired after a reconnection.
  session.on("session_restored", ()=>{});

from node-opcua.

Thanks a lot for you answer.
I had tried that as well and it doesn't solve the issue since:

• Session_restored event is fired before Connection_reestablished
• When session_restored is fired, both session.isReconnecting and client.isReconnecting are still true.

Please see the code and screen shot below :

      opcuaSession.on("session_restored", () => {
        this.logger.error('Session restored')
        this.logger.error(opcuaClient.isReconnecting)
        this.logger.error(opcuaSession.isReconnecting)
      })

from node-opcua.

fixed in [email protected]

from node-opcua.