Results 1 to 6 of 6
  1. #1

    Unexpected UPDATE command

    I'm getting the following error message:

    Unexpected UPDATE command in snapshot for key KEY1. Event propagated in an inconsistent way.
    Last edited by ManKeer; June 22nd, 2020 at 10:40 AM.

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,007
    We are aware only of similar messages, of this form:
    - Unexpected UPDATE command in snapshot for key xxxx
    - Unexpected UPDATE event for key xxxx
    - Unexpected update for item xxxx on yyyy
    Please clarify if you refer to one of these; or please specify the Server version.

  3. #3
    I have updated the original post

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,007
    When the Data Adapter feeds an item subscribed to in COMMAND mode, it has to provide the "snapshot" first, then the real time updates.
    Since this kind of item represents a table, by "snapshot" we mean the current contents of the table at the time of subscription.
    By convention, these current contents have to be supplied as a sequence of ADD commands, one for each row (i.e. key) in the table.
    After that, you should send an "end of snapshot" notification; at this point you can supply ADD, UPDATE, and DELETE commands to reflect real time updates.
    You must have sent an UPDATE command before the "end of snapshot" notification, which makes no sense for Lightstreamer Server.

  5. #5
    Thank you Dario for your suuport,

    I have figured out the cause of this problem, I'm using smartUpdate with isSnapshot set to true in all cases, my solution is to pass true for the first call smartUpdate, after that I have passed the isSnapshot with false, and the Unexpected UPDATE command totally disappeared.

  6. #6
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,007
    Yes, I confirm that you can just use the isSnapshot flag properly and you don't need to send the end-of-snapshot notification, which is optional.
    Just note that if you don't send the end-of-snapshot notification, the client won't receive, in turn, the end-of-snapshot notification, until the first real-time update is produced. Obviously, this may not be important in your case.

 

 

Similar Threads

  1. Replies: 7
    Last Post: November 15th, 2017, 08:52 AM
  2. Error handling for: [Unexpected update for item]
    By tony99nyr in forum Adapter SDKs
    Replies: 3
    Last Post: April 7th, 2014, 09:29 AM
  3. Replies: 2
    Last Post: March 29th, 2013, 02:59 AM
  4. Replies: 1
    Last Post: April 17th, 2012, 09:19 AM
  5. Replies: 1
    Last Post: August 20th, 2009, 08:47 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 12:38 PM.