Hi again Kertesz,
Hm. Maybe i did something wrong, but i get this:
Can't load log handler "net.java.sip.communicator.plugin.reconnectplugin"
The "net.java.sip.communicator.util.FileHandler.level" handler was there (/usr/lib/jitsi/lib/logging.properties), but the reconnectplugin was not - i added it to the end of the file and in the handler list but i dont know if thats ok.
Thats exactly what you had to do.
So, this time on my desktop it reconnected only after i pinged the SIP server - then all accounts reconnected at once, including the Yahoo and Gmail.
I have 2 accounts that use an OpenVPN connection (1 jabber + 1 SIP - the servers are given by ip) + 1 Gmail and 1 Yahoo account configured. The VPN connection reconnects usually quite fast and i can access resources on it, but usually Jitsi takes its time and if it does reconnect, i dont have the whole SIP contact list, only if i untick/tick it on the accounts list.
I don't see anything suspicious at the logs, you wake up your PC at
16:41:03.069, and after everything going down, the last interface came
up at 16:41:06.720 when every provider start connecting and the
providers went one by one on, and only one was not connected when
Jitsi was shutdown at 16:42:00.157.
I will check once again the delays between reconnects, currently every
next account is reconnected after a certain time, this time start from
8 sec. by growing with 30 sec. till it reaches 5 min. As you have many
interfaces going from down to up after standby it may happen some
provider to go to maximum delay (will reconnect after 5 minutes).
Thanks for the logs and testing
On Fri, Apr 1, 2011 at 4:47 PM, Kertesz Laszlo <email@example.com> wrote:
----- Original Message -----
From: "Damian Minkov" <firstname.lastname@example.org>
Cc: "Bauersachs Ingo" <email@example.com>
Sent: Friday, April 1, 2011 4:23:03 PM
Subject: [jitsi-dev] Re: Unable to reconnect after network change
Yes two hours are enough Aha I see what you mean, this only works
with parallel resolver enabled, will fix it.
Hey Kertesz you can enable
'net.java.sip.communicator.plugin.reconnectplugin.level =FINER' and
'net.java.sip.communicator.util.FileHandler.level = FINER' in your
logging.properties and when this happen can send the logs there will
be info what network change we have detected.
On Fri, Apr 1, 2011 at 4:14 PM, Bauersachs Ingo >> <firstname.lastname@example.org> wrote:
>> actually this is already done there in NetworkUtils.
>> NetworkConfigurationChangeListener.configurationChanged on every
> Yes and no. It only resets the ParallelResolver - and I can't use
> the ParallelResolver. The call to ResolverConfig.refresh(); in
> ParallelResolver.reset should probably be moved to
> NetworkUtils.reloadDnsResolverConfig and called regardless of what
> instance the parallelResolver field has assigned.
> This is probably even my fault when I created the patch to disable
> the ParallelResolver.
>> It could be other problem you are experiencing or this events are
>> some reason not delivered.
> UnknownHostException pretty much indicate unavailable DNS servers...
>> How long do you wait before considering
>> accounts are unable to connect.
> Is almost two hours enough?
O zi buna,