Bugs item #3484716, was opened at 2012-02-05 11:49
Message generated for change (Settings changed) made by freyther
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3484716&group_id=167540
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Synchronisation / Invitation
Group: None
Status: Closed
Resolution: Fixed
>Priority: 5
Private: No
Submitted By: Alexander Waldmann (netcorps)
Assigned to: Alexander Waldmann (netcorps)
Summary: INVITATION_ACKNOWLEDGEMENT_TIMEOUT 3 seconds
Initial Comment:
public interface ITransmitter {
public static final long INVITATION_ACKNOWLEDGEMENT_TIMEOUT = 3000;
The low timeout is causing the problems mentioned in the bug
https://sourceforge.net/tracker/?func=detail&aid=3475609&group_id=167540&atid=843359
If the user that sent an invitation and does not receive the invite ack fast
enough, he/she quits the freshly created session.
BUT the remote peer might still receive the invitation later, and confirm it,
and actually enter a dead session with the host (without the host knowing about
it).
So a quick fix would be to increase this timeout, but i guess there has to be
some sort of magical logic behind this configuration value, unless it is a typo
and should be 30 seconds instead of 3...
Anyone knows why this was configured with 3 seconds?
----------------------------------------------------------------------
Comment By: Alexander Waldmann (netcorps)
Date: 2012-03-25 03:32
Message:
If a bug has been accepted and a fix has been committed to SVN the
developer should set the bug to "Fixed", but not close or set to pending.
----------------------------------------------------------------------
Comment By: Alexander Waldmann (netcorps)
Date: 2012-02-15 12:37
Message:
Fix waiting for review.
----------------------------------------------------------------------
Comment By: Alexander Waldmann (netcorps)
Date: 2012-02-15 12:33
Message:
Load is below 1% on the test machine.
The issue is within jabber.org being slow.
----------------------------------------------------------------------
Comment By: Stefan Rossbach (kargor)
Date: 2012-02-05 19:05
Message:
No nobody knows, at least 20 seconds should be ok.
My ping to Japan is about 300 ms, so the client machine have to be on high
load so it cannot reply in this timeout sequence.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3484716&group_id=167540
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dpp-robot mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dpp-robot
