powered by Jive Software

Messages in Yahoo are being delayed

I don’t know if it necessary happens to all the transports, but are seeing periodic delays in messages when using the Yahoo part of the gateway plugin:

10/31/2007

Sent

Delivered

Difference

CrudeGuy: hi i am going to start a

conversation

11:49:47 AM

11:50:42 AM

55

ybroker2: really?

11:49:58 AM

11:49:58 AM

0

ybroker2: outgoing messages aren’t working?

11:50:03 AM

11:50:04 AM

1

CrudeGuy: are they delayed?

11:50:08 AM

11:50:08 AM

0

CrudeGuy: what about this one?

11:50:11 AM

11:50:11 AM

0

ybroker2: thats not good

11:50:15 AM

11:50:15 AM

0

CrudeGuy: messages are just getting dropped

11:50:20 AM

11:50:21 AM

1

CrudeGuy: they are taking long to send

11:50:26 AM

11:50:26 AM

0

CrudeGuy: really?

11:50:34 AM

11:50:37 AM

3

ybroker2: yeah

11:50:36 AM

11:50:36 AM

0

ybroker2: there really are message delays

11:50:39 AM

11:50:41 AM

2

CrudeGuy: whoa!

11:50:47 AM

11:50:48 AM

1

ybroker2: this is not good at all

11:50:51 AM

11:50:51 AM

0

CrudeGuy: there are definately problems

11:50:55 AM

11:50:56 AM

1

ybroker2: yeah i still haven’t gotten your

first one

11:50:32 AM

11:50:58 AM

26

ybroker2: ytes, lots of problems

11:50:59 AM

11:51:00 AM

1

CrudeGuy: messages are getting all mixed up

11:51:05 AM

11:51:06 AM

1

ybroker2: its a good thing we have log snap

11:51:10 AM

11:51:10 AM

0

CrudeGuy: to capture the logs

11:51:13 AM

11:51:13 AM

0

CrudeGuy: i dont see a pattern yet

11:51:16 AM

11:51:17 AM

1

ybroker2: do you see a pattern?

11:51:20 AM

11:51:21 AM

1

ybroker2: yikes

11:50:13 AM

11:51:22 AM

69

CrudeGuy: no i just said that

11:51:24 AM

11:51:24 AM

0

CrudeGuy: whoa i just got that yikes

11:51:27 AM

11:51:28 AM

1

CrudeGuy: messages are definately being

delayed

11:51:31 AM

11:51:32 AM

1

ybroker2: yes, yes they are

11:51:34 AM

11:51:35 AM

1

ybroker2: we should fix this

11:51:37 AM

11:51:37 AM

0

ybroker2: as soon as possible

11:51:38 AM

11:51:39 AM

1

ybroker2: yes very soon

11:51:41 AM

11:51:41 AM

0

ybroker2: as in now

11:51:42 AM

11:51:42 AM

0

ybroker2: whta bout now

11:51:45 AM

11:51:45 AM

0

CrudeGuy: yes now

11:51:47 AM

11:51:47 AM

0

CrudeGuy: not later

11:51:48 AM

11:51:48 AM

0

CrudeGuy: but now

11:51:49 AM

11:51:50 AM

1

CrudeGuy: looks okay now

11:51:52 AM

11:51:53 AM

1

We are seeing this problem in both our test and production environments, so if anybody can relate or let us know what’s going (read: jadestorm please help us!), it would be appreciated. The test was done by rapidly sending a message to and from ybroker2 and CrudeGuy. The above table is CrudeGuy’s view of the convo, and the bottom set is ybroker2’s view of the convo. Notice the difference, especially with the message “yikes”. This was on 3.3.2 and Gateway vers. 1.1.2. We are going to do a test with 1.1.3a very shortly. If we find anything in the tcpdumps that signals that the OS itself is slow in receiving it, we’ll post that too.

ybroker2 (): really?

ybroker2 (): outgoing messages aren’t

working?

crudeguyyj (): are they delayed?

crudeguyyj (): what about this one?

ybroker2 (): yikes

ybroker2 (): thats not good

crudeguyyj (): messages are just getting

dropped

crudeguyyj (11:50:26 AM): they are

taking long to send

ybroker2 (): yeah i still haven’t gotten

your first one

ybroker2 (): yeah

crudeguyyj (11:50:37 AM): really?

ybroker2 (): there really are message

delays

crudeguyyj (): hi i am going to start a

conversation

crudeguyyj (): whoa!

ybroker2 (): this is not good at all

crudeguyyj (): there are definately

problems

ybroker2 (): ytes, lots of problems

crudeguyyj (): messages are getting all

mixed up

ybroker2 (): its a good thing we have

log snap

crudeguyyj (): to capture the logs

crudeguyyj (): i dont see a pattern yet

ybroker2 (): do you see a pattern?

crudeguyyj (): no i just said that

crudeguyyj (): whoa i just got that

yikes

crudeguyyj (): messages are definately

being delayed

ybroker2 (): yes, yes they are

ybroker2 (): we should fix this

ybroker2 (): as soon as possible

ybroker2 (): yes very soon

ybroker2 (): as in now

ybroker2 ): whta bout now

crudeguyyj (): yes now

crudeguyyj (): not later

crudeguyyj (): but now

crudeguyyj (): looks okay now

Hrm. Can you see in the debug logs the messages coming in and then leaving through Yahoo? It almost sounds like Yahoo was being a pest judging from the nature of those issues, or that there was some sort of network issue between your server and theirs. I know that’s not entirely helpful but that’s about the only thing I can think of. I regularly hold conversations over Yahoo and haven’t seen this behavior, so in theory it’s behavior. =/

Of course it would be nice if there were some sort of useful ack that the message actually got there.

Hey Daniel,

I think I’ve found the problem. And I don’t think it’s because of our Gateway. I ran the same test using Trillian and Yahoo and we still received delays. I think Yahoo doesn’t much care for the use of third party apps and it doesn’t have a no-delay guarantee like it does if both users were to use Yahoo Messenger.

I’m going to tests scsa.msg.yahoo.com, scsb.msg.yahoo.com, and scsc.msg.yahoo.com to see if they are any quicker than scs.msg.yahoo.com