Client sending large number of disposition frames.

[serkantkaraca]

This is regarding a service side investigation where we identified large number of disposition frames then usual. Can you please help me identify why client sends large number of disposition frames? See sample logs below with frame counts where disposition frame id is 21.

• in-connection4435862(XXXXXX): namespace: XXXXXX, operation: write, duration (ticks): 1200141623, total bytes: 4240487, elapsed: 00:06:00.0421626, frame count: 16:0,17:0,18:0,19:1133,20:0,21:113144,22:0,23:0,24:0,25:39313,26:8192,27:69,28:21827
• in-connection4435868(XXXXXX): namespace: XXXXXX, operation: write, duration (ticks): 1200141541, total bytes: 4258477, elapsed: 00:06:00.0371822, frame count: 16:0,17:0,18:0,19:1135,20:0,21:113422,22:0,23:0,24:0,25:39667,26:8192,27:69,28:21848
• in-connection4358738(XXXXXX): namespace: XXXXXX, operation: write, duration (ticks): 1200008413, total bytes: 5023918, elapsed: 00:05:59.9903898, frame count: 16:0,17:0,18:0,19:1139,20:0,21:113779,22:0,23:0,24:0,25:65703,26:8192,27:31,28:6304
• in-connection4358736(XXXXXX): namespace: XXXXXX, operation: write, duration (ticks): 1200008413, total bytes: 5018611, elapsed: 00:05:59.9961345, frame count: 16:0,17:0,18:0,19:1134,20:0,21:113304,22:0,23:0,24:0,25:65971,26:8192,27:31,28:6364

Environment

EH Go client 1.0.1.

[fafg]

did you already try with the latest version? It would be possible to update to v3.2.0?

[serkantkaraca]

This was hit only once. Moving to up to date library won't really prove it is fixed. Any idea what may cause large number of disposition frames to be sent?