5.2.20
08/25/2019

[#191] auto generated stanza ID causes connection issue
Summary auto generated stanza ID causes connection issue
Queue gloox
Queue Version 1.0
Type Bug
State Accepted
Priority 3. High
Owners js (at) camaya (dot) net
Requester marcus.frenkel (at) gmail (dot) com
Created 11/01/2010 (3219 days ago)
Due
Updated 10/15/2013 (2140 days ago)
Assigned
Resolved

History
10/15/2013 01:07:31 AM Jakob Schröter Comment #2
Assigned to Jakob Schröter
State ⇒ Accepted
Reply to this comment
Sorry this took so long. I have changed the colon for a dot now in 
svn. Will be in 1.0.9.
If you are still using gloox it would be great if you could test and 
report back. Thanks!
11/01/2010 03:40:55 PM marcus (dot) frenkel (at) gmail (dot) com Comment #1
State ⇒ Unconfirmed
Queue ⇒ gloox
Summary ⇒ auto generated stanza ID causes connection issue
Type ⇒ Bug
Priority ⇒ 3. High
Reply to this comment
It is a very strange issue, I will try to explain it.

Using gloox 1.0 for win32 client. It always happens on 3G internet 
connection (but speed is pretty fast) and sometimes on other 
connections. Server connection is TLS required.

Currently I can reproduce the problem with vcard request stanza, but 
it happens on private xml request which case currently I cannot always 
reproduce.

=======
Scenario 1: Using VcardManager::fetchVcard
Gloox sends this stanza:
<iq to='userA@server.com'id='uid:4ccecced:000036ee' type='get' 
from='User_ME@server.com/res1' xmlns='jabber:client'><vCard 
xmlns='vcard-temp'/></iq>
Result: vcard is received OK.

Gloox sends this stanza:
<iq to='userB@server.com' id='uid:4cceca42:00006a8e' type='get' 
from='User_ME@server.com/res1' xmlns='jabber:client'><vCard 
xmlns='vcard-temp'/></iq>
Result: Nothing is returned, from this point on gloox doesn't receive 
any data from the server while the socket is still open.

There is not particular differences between these users vcards, but 
when requesting vcard for USERB, connection hangs, no idea why. It 
happens for some users vcards, and for other users vcards is OK.
=======
Scenario 2: Request Vcard using custom tag
Gloox sends this stanza:
<iq to='userB@server.com' id='uid:4cceca42:00006a8e' type='get' 
from='User_ME@server.com/res1' xmlns='jabber:client'><vCard 
xmlns='vcard-temp'/></iq>
Result: Again nothing is returned, and connection hangs, one cannot 
receive any data (not only vcard but msgs too), but can send data fine 
(msg sent in this moment is delivered fine to the other party).

Gloox sends this stanza:
<iq to='userB@server.com' id='uid4cceca4200006a8e' type='get' 
from='User_ME@server.com/res1' xmlns='jabber:client'><vCard 
xmlns='vcard-temp'/></iq>
Result: Vcard received OK (only in log, not in vcard handler, bcs 
vcardmanager not used). The only difference from above is that the ID 
has the character ":" removed. With this kind of ID it always works.
=======
Scenario 3:
Using PSI, connected on the same server and tried on the same users 
vcards, I have tried to send all the stanzas above to request VCard 
(when ID contains ":" and when it doesn't) and PSI always returns the 
VCard.