Inbound processing of container with index 1668 failed: Can not find top ro

[Former Member]

HELLO,

WE HAVE PROBLEMS WITH SOME USERS.

SOMETIMES THEIR TABLETS HAVE TO RESET, BUT WE CAN NOT KNOW WHAT THE PROBLEM IS.

WE ARE TRYING TO REPRODUCE THIS ERROR, BUT WE CAN NOT SUCCEED IT. THESE USER HAVE IN TRANSACTION 'MEREP_MON' TWO DELETE FOR THE SAME PAQNO. OUR SYNCBOS ARE RELATED. THE USER TABLET SHOW THE MESSAGE:

Inbound processing of container with index 1668 failed: Can not find top row with descriptor cY05_NOTTIE_TOP and key 11390 : <InboundProcessingError timestamp="2008-03-14-13-05-37"><RowProcessorDispatcherDump type="nonObservable" ><Action>d</Action><TopRowKey>0000011390</TopRowKey><ChildRowKey> </ChildRowKey><RequestId>6092BB9ACBDBA341BFF62FF726AECA81</RequestId><StateID>6092BB9ACBDBA341BFF62FF726AECA81</StateID></RowProcessorDispatcherDump></InboundProcessingError>

java.lang.IllegalArgumentException: Can not find top row with descriptor cY05_NOTTIE_TOP and key 11390

WE THINK TAHT THE FIRST DELETE IS EXECUTED RIGHT, BUT THE SECOND DELETE PRUDUCE AN ERROR.

HOW COULD WE REPRODUCE THIS ERROR IN OUR TABLET?

THAKS

[Former Member]

Hi Victor,

I would check the delete handler in the backend for that - could be that ther eis a problem out there.

At least: check MEREP_MON as well to see the data flow for that BO and any messages in the middleware.

Hope that helps to light some candles in the dark.

Regards,

Oliver

[Former Member]

Hi VIctor,

you can check the index data in worklist montior for that mobile ID.Looking at data it might give you an idea what went wrong.

Thanks

Regards

Devendra Kumar Phate