Adium

Ticket #5367 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

Rate Limiting error still in 1.0b9 for AIM

Reported by: tokala@gmail.com Owned by: leak
Milestone: Adium X 1.0 Component: Service/AIM
Version: 1.0b9 Severity: regression
Keywords: rate limiting, AIM, joscar, beta, buddy icon Cc:
Patch Status:

Description (last modified by evands) (diff)

Error: Rate Limiting issues still present in Aug 19 2006 beta version for AIM protocol

I will be including a screenshot of the problem. It seems that it's connected to buddy icon requests occuring while account is disabled. I will post excerpts from debug windows in here as well.

Debug:

14:11:43: <RAFjoscarAIMAccount: 0xdde130>:1:tokalahusky: Updating status for Online
14:11:43: *** net.kano.joustsim.oscar.DefaultAppSession@71dc3d disconnecting tokalahusky

Joscar Debug:

[2:11:41 PM EDT] BuddyIconTracker: Requesting buddy icon for example6
[2:11:42 PM EDT] ExternalServiceManager$4: External service for arbiter net.kano.joustsim.oscar.oscar.service.chatrooms.RoomFinderServiceArbiter@d91f1f(0xd) timed out after 10.001s; retrying
[2:11:42 PM EDT] ExternalServiceManager$4: External service for arbiter net.kano.joustsim.oscar.oscar.service.chatrooms.RoomFinderServiceArbiter@1e64a8(0xd) timed out after 14.998s; retrying
[2:11:46 PM EDT] BuddyIconTracker$3: Re-requesting buddy icon {ExtraInfoData=ExtraInfoData: flags=0x1 (FLAG_HASH_PRESENT), data=38 3f ef 0e 73 b8 50 6e ba 59 87 3c f9 83 ff d5, Screenname=example5}
[2:11:46 PM EDT] BuddyIconTracker: Requesting buddy icon for example5
[2:11:46 PM EDT] BuddyIconTracker$3: Re-requesting buddy icon {ExtraInfoData=ExtraInfoData: flags=0x1 (FLAG_HASH_PRESENT), data=a7 be 6a b0 07 aa c4 51 13 87 42 11 5a db 8f 05, Screenname=example4}
[2:11:46 PM EDT] BuddyIconTracker: Requesting buddy icon for example4
[2:11:51 PM EDT] BuddyIconTracker$3: Re-requesting buddy icon {ExtraInfoData=ExtraInfoData: flags=0x1 (FLAG_HASH_PRESENT), data=a3 88 b8 45 78 be 99 10 3b ba 20 35 6f aa 21 87, Screenname=example3}
[2:11:51 PM EDT] BuddyIconTracker: Requesting buddy icon for example3
[2:11:51 PM EDT] BuddyIconTracker$3: Re-requesting buddy icon {ExtraInfoData=ExtraInfoData: flags=0x0 (), data=02 01 e0 68 c0, Screenname=example2}
[2:11:51 PM EDT] BuddyIconTracker: Requesting buddy icon for example2
[2:11:51 PM EDT] BuddyIconTracker$3: Re-requesting buddy icon {ExtraInfoData=ExtraInfoData: flags=0x1 (FLAG_HASH_PRESENT), data=ad 8a 04 24 27 fa 81 0f a6 5d 78 df 82 24 05 7e, Screenname=example1}

Attachments

Picture-1.gif Download (218.3 KB) - added by tokala@… 6 years ago.
Screenshot of issue
2006-08-24.log.bz2 Download (18.5 KB) - added by boredzo 5 years ago.
Saved text from Adium Debug Window, previously uploaded by anonymous without compression.

Change History

Changed 6 years ago by tokala@…

Screenshot of issue

comment:1 follow-up: ↓ 4 Changed 6 years ago by mlf

please provide a tcpdump (see UsingTcpdump ), and please attach your joscardebug.log. Are you _actively_ IMing with AIM people when you are disconnected? Do you connect through a home wireless router? Does this problem also happen with .89.1 or iChat or the official AIM client, or if you use 1.0b9 and are directly connected to your cable/dsl modem? How many people are on your buddy list? fyi, buddy icons are handled by a different server than your messages go up to.

comment:2 Changed 6 years ago by tick

  • Severity changed from major to regression

comment:3 Changed 6 years ago by tick

  • Component changed from AIM to adium-joscar

comment:4 in reply to: ↑ 1 Changed 6 years ago by anonymous

okay - well, i dumped a session in which i was able to reproduce the behavior. unfortunately the tcpdump is nearly 30MB and the joscar log is 1.3MB. what's the best way to get these to you guys?

looking at it again, the behavior seems to occur once you login using Adium, log out, and connect on iChat before trying to login on Adium again. the only way to stop the constant buddyicon getting mechanism is to kill Adium. (even when Adium knows the account isn't connected, it keeps trying to fetch icons). after killing iChat, Adium's behavior still remains severely impacted (can't login to any AIM accounts). this problem was not noted in any other clients.

comment:5 Changed 6 years ago by catfish_man

Feel free to contact me on aim (check the wiki for my contact info) and file transfer the log to me.

comment:6 Changed 6 years ago by anonymous

additional notes: buddy list size ~ 175 connection method = corporate internet, 100Mb ethernet, no proxy

comment:7 Changed 6 years ago by evands

  • Description modified (diff)

comment:8 Changed 6 years ago by evands

  • Owner changed from nobody to leak

comment:9 Changed 6 years ago by Robby

In the past few days I have experienced massive amounts of "rate limiting errors". Today it all ended in me not being able to connect to ICQ, this affecting not only Adium, but the ancient ICQ client and iChat also.

(b14, buddy list size ~83, DSL through WLAN router, no proxy)

comment:10 Changed 6 years ago by evands

  • Status changed from new to closed
  • Resolution set to fixed

ICQ rate limiting errors are not related to this ticket, as ICQ does not connect using joscar in Adium 1.0b14.

(In [18120]): joscar [484] which fixes rate limiting problems. Fixes #5367. Fixes #5252.

comment:11 Changed 5 years ago by evands

  • Component changed from adium-joscar to AIM

Rate limiting problems are fixed in libgaim AIM, as well.

Changed 5 years ago by boredzo

Saved text from Adium Debug Window, previously uploaded by anonymous without compression.

Note: See TracTickets for help on using tickets.