View Issue Details

IDProjectCategoryView StatusLast Update
0013901MMW v4Synchronizationpublic2017-01-16 14:39
Reportermarek Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionnot fixable 
Product Version4.1.14 
Target Version4.1.15 
Summary0013901: Upload of synced content list from MMA to MMW can fail on timeout
DescriptionThere is a user that experiences an issue with wifi sync. It is always terminated on upload of synced items to MMW. Is it possible that it take so much time (19 s) on MMW side?
Additional InformationOLA-573-16055
TagsNo tags attached.
Fixed in build

Activities

Ludek

2017-01-13 17:39

developer   ~0046933

Last edited: 2017-01-13 17:41

Requested MMW log via ticket OLA-573-16055:
Based on the MMW log (corresponding MMA log is JIT3A89W4S ) I see:

- at 64 seconds MMA browsed for
SyncList:DeviceID:FA6A10315604.0.cd22029b-1f2e-440c-a687-0694636135e6\Playlists, Start: 0, Count: 200
=> MMW returned 39 playlists

- at 65 seconds MMA browsed for
SyncList:DeviceID:FA6A10315604.0.cd22029b-1f2e-440c-a687-0694636135e6\Playlists\bc3acf48-d68a-483c-8bac-4f65ddf128ca, Start: 0, Count: 24
=> MMW returned 24 child playlists

- at 65 seconds MMA browsed for
SyncList:DeviceID:FA6A10315604.0.cd22029b-1f2e-440c-a687-0694636135e6\Playlists\bc3acf48-d68a-483c-8bac-4f65ddf128ca, Start: 24, Count: 24
=> MMW returned 0 child playlists

- at 85 seconds MMA sent
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?><SyncSummary succeed="1" />

- at 86 MMA sent
SyncFinished:DeviceID:FA6A10315604.0.cd22029b-1f2e-440c-a687-0694636135e6

So question is why MMA did not continue to read further playlist at 65 seconds?
Maybe a network connection problem?
Do you see something useful in MMA log JIT3A89W4S ?

Ludek

2017-01-16 14:39

developer   ~0046978

After analyzing with Marek it looks that on the user's machine must be something that is blocking incoming HTTP POST requests from MMA -> MMW.