[sip-comm-dev] Spurious? disconnects, NetworkConfigurationWatcher


#1

I've been experiencing what seem to be spurious disconnects in SIP
Communicator on Windows. The application frequently notifies my that
the connectivity has been lost and reconnects my accounts. This
behavior seems suspicious to me though because I haven't observed the
connectivity losses anywhere else but inside SIP Communicator. I have
an IRC client (namely, Pidgin) running, I even installed and started
Skype and logged into Gmail chat. I'm also downloading with high
speeds using uTorrent at times. Yet only SIP Communicator reports
problems with the connectivity. One of the times I managed to "lose"
my connectivity by clicking on the Video tab in Tools > Options which
seemed to freeze or put a relatively high strain on the application.

I briefly looked at NetworkConfigurationWatcher because I didn't see
exceptions related to connectivity failures in the logs. My n00b
opinion is that we could at the very least set the last check time
after the checks are performed, not at their very beginning. Another
observation which is unrelated to the problem described here is that
spurious wakeups may be considered if the interface retrieval and
checks are not lightning fast.

Has anyone had similar experiences?

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

I've been experiencing what seem to be spurious disconnects in SIP
Communicator on Windows. The application frequently notifies my that
the connectivity has been lost and reconnects my accounts.
[...]

I briefly looked at NetworkConfigurationWatcher because I didn't see
exceptions related to connectivity failures in the logs. My n00b
opinion is that we could at the very least set the last check time
after the checks are performed, not at their very beginning. Another
observation which is unrelated to the problem described here is that
spurious wakeups may be considered if the interface retrieval and
checks are not lightning fast.

Has anyone had similar experiences?

Yes, although mainly when I started it under debugging (but not actually having any breakpoints). I blame the "isAfterStandby"-check for those issues and worked more or less around it by simply increasing the 2*CHECK_INTERVAL to 10*CHECK_INTERVAL (Line 98). I agree that setting the time after doing the checks would make sense.

Regards,
Ingo

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net