1. #1
    Sencha Premium Member
    Join Date
    May 2012
    Posts
    16
    Vote Rating
    0
    mwindley is on a distinguished road

      0  

    Default Answered: Sync issue

    Answered: Sync issue


    I have had Todo example working yesterday but not today.
    Today I modify it to improve my understanding but have issues.

    I have restarted with original but it is now not functioning.

    I have the following error as a symptom from th eObject returned from the example code

    broadcast update [Object
    message: "local updates do need to be synched, but a remote sync is currently in progress"
    r: "error"


    then

    Logger.js:132ERROR: Error running RPC timeout checks
    Error
    line: 155
    message: "'undefined' is not an object (evaluating 'response.r')"
    sourceId: 4638233344
    sourceURL: "file:///Users/mauricewindley/Sites/myProjects/Todo/lib/io/src/cf/data/Protocol.js?_dc=1340182878018"
    __proto__: Error


    I am using Mac Intel, Lion, ST2, I have rest Safari local storage etc.

    Any hints on what I may have done wrong.

    Todos entered are displayed in the list, local storage shows undelivered stuff

    {"name":"sencha-io-undelivered-outgoing-envelopes","type":"channel","meta":{"direction":"out"},"id":3}

    Thanks in advance
    Maurice
    Regards Maurice

  2. Yes. One of the servers got into a bad state whilst holding a lock on a store. I've reset that server now. We have a solution, but its not been pushed to production yet.

    John

  3. #2
    Sencha User
    Join Date
    Mar 2012
    Posts
    47
    Vote Rating
    0
    Answers
    3
    romulus2012 is on a distinguished road

      0  

    Default


    I'm having the same issue too. I think that there is a problem with sencha servers.

  4. #3
    Sencha User
    Join Date
    Apr 2010
    Posts
    107
    Vote Rating
    -1
    Answers
    30
    merrells is an unknown quantity at this point

      0  

    Default


    Yes. One of the servers got into a bad state whilst holding a lock on a store. I've reset that server now. We have a solution, but its not been pushed to production yet.

    John

Thread Participants: 2