| By Date: | <-- --> |
| By Thread: | <-- --> |
|
as of my latest checkin. Replication thread objects are all created
early, and the notification logic in markUnReachable is now correct.
Check out the log messages below to see backoff in action. I was confused initially by REGISTER_TEST_MAX_WAIT = 30 whereas the data shows the actual max wait to be 32 seconds. Turns out that REGISTER_TEST_MAX_WAIT is not actually the max wait time, rather we double the wait time until we have exceeded REGISTER_TEST_MAX_WAIT and then we stop doubling. I changed this value to 32 as a quick if inelegant way to fix the confusion (until someone decides to change the value of this parameter!). -Walter 2006-02-02T04:54:49.491624Z":134:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:54:53.491971Z":135:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:55:01.493392Z":136:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:55:17.496138Z":137:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:55:49.497367Z":140:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:56:21.498518Z":143:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) 2006-02-02T04:56:53.500094Z":146:SIP:DEBUG:saffron.pingtel.com::B63F6BB0:SipRegistrar: RegistrarTest SyncRpcReset::invoke(saffron.pingtel.com, ha1.pingtel.com) |
_______________________________________________ sipx-dev mailing list sipx-dev (at) list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev