I experience the following scenario while synchronizing:
- A MAM25_005 object is being created on the client by a user, he wants to synchronize with the backend to post this object.
- Sync 1 (button-wise): the synchronisation goes ok until somewhere in between (as noticed in MEREP_MON on netweaver). Suddenly the following error message is thrown in the trace on the client:
HttpSynchronizer caught exception java.io.IOException: Server returned HTTP response code: 500 for URL: http://IP:8041/meSync/servlet/meSync?sysid=CQ6&client=100&~language=en&PACKET_SIZE=2500&ACKNOWLEDGE=X&
java.io.IOException: Server returned HTTP response code: 500 for URL: http://IP:8041/meSync/servlet/meSync?sysid=CQ6&client=100&~language=en&PACKET_SIZE=2500&ACKNOWLEDGE=X&
The MAM_005 object is by then allready posted in the SAP system, but is not deleted yet, it is locked for synchronisation in other words.
Synchronisation 2 (button-wise): The synchronisation behaves ok, but after the sync following message is shown on the client:
Ignored old data has been received for user...
Data is not complete for user x and framework X
Data is complete for user X and framework MOBILEENGINE_JSP
(we use repititive synchronisation) Now, the MAM_005 is deleted, but not all MAM objects are updated yet (as in 'data is not complete')
After sync 3 (button-wise), we see the correct messages and all data seems to be landed on the device correctly...
Anybody any idea why this happens?