Ignoring incoming message....... URGENT

[Former Member]

Hi all,

when i synchronise my application the data corresponding to that appliaction comes on the device (it is displayed in the trace) but my application is not able to read it from the persistence layer. I think the data is not added to the persistence layer..... have a look at the error i am getting.....

20051221 06:06:31:281] A [MI/Smartsync ] Dumping InboundMessage[0]

[20051221 06:06:31:281] A [MI/Smartsync ]

F04EB47A1EB15B4B8B24A01E244354150010500100000401842006040720060408new9ggggDE3Trip Completd1To Be Settd001001MBRABREAKFAST8.8800USD20060407

[20051221 06:06:31:296] A [MI/Smartsync ] Notifying SyncBoInDeltaObservers:

[20051221 06:06:31:296] A [MI/Smartsync ]

[20051221 06:06:31:296] D [MI/Smartsync ] com.sap.ip.me.smartsync.data.SyncBoManager.getSyncBoWithoutCheck invoked. boDesc=ZTRIPNEW SyncKey=0001017311

[20051221 06:06:31:296] D [MI/Smartsync ] PersistenceAdapterImpl(2): (ConvId = 4157F457D63E85478B0C3294C4EF020A, Thread = Thread-26) : Get entity a.ZTRIPNEW with key 0001017311

<b>[20051221 06:06:31:296] W [MI/Smartsync ] SyncBo 0001017311 could not be found for modify. Ignoring incoming message.</b>

after this statement the data shuld be added to the persistence layer. but that does not happen.....

can anybody tell where is the problem....

Thanks.....

[Former Member]

hello prakash,

this happens when the SyncBo instance is already removed

from the client data repository and a modify message

from the server is received. specific scenario is that

the user deleted 0001017311 SyncBO instance while at

the same time somebody had modified the 0001017311

values in the middleware or backend. the client will

ignore this modify message instead.

this is actually a conflict case:

CLN: delete, MW: modify

on your succeeding sync, in case of v2.5, you will be

receiving a conflict message with insert data in it.

and your data will get inserted if your application

MCD is set to Framework resolve in such case the server

state wins. in 2.1, the server state always wins,i.e.

the data will get inserted again. and the user has to

delete it again if he really wants to.

check on your mobile worklist monitor if conflict was

detected and a corresponding message is created into the

outbound queue.

regards

jo