View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013901 | MMW v4 | Synchronization | public | 2017-01-12 12:45 | 2017-01-16 14:39 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | not fixable | ||
| Product Version | 4.1.14 | ||||
| Target Version | 4.1.15 | ||||
| Summary | 0013901: Upload of synced content list from MMA to MMW can fail on timeout | ||||
| Description | There 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 Information | OLA-573-16055 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
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 ? |
|
|
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. |
