Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5704

FIWARE.Question.Tech.Data.OrionContextBroker.RuntimeError

    Details

      Description

      Created question in FIWARE Q/A platform on 18-01-2016 at 23:01
      Please, ANSWER this question AT http://stackoverflow.com/questions/34864957/runtime-error-field-coordinates-is-missing-in-bsonobj

      Question:
      Runtime Error (field 'coordinates' is missing in BSONObj <{}>)

      Description:
      I had a OCB running that allowed me to update an entity value remotelly and had a local accumulator server running that was being notified. I just update OCB and now it's in version 0.26.1 and everytime I try to update I get an error.

      This is the update:

      { "contextElements":
      [ {
      "type": "Room",
      "isPattern": "false",
      "id": "Room1",
      "attributes":
      [

      { "name": "volume", "type": "float", "value": "67.000000" }

      ,

      { "name": "temperature", "type": "float", "value": "39.000000" }

      ,
      {
      "metadatas": [

      { "name": "location", "type": "string", "value": "WGS84" }

      ],
      "name": "position",
      "type": "coords",
      "value": "40.418889, -3.691944"
      }

      ] }
      ],

      "updateAction": "APPEND" }
      EOF

      contextBroker.log :

      time=2016-01-18T22:57:13.793CET | lvl=ERROR | trans=1453154140-565-00000000004 | function=getObjectField | comp=Orion | msg=safeMongo.cpp[53]: Runtime Error (field 'coords' was supposed to be an object but type=4 in BSONObj <

      { attrName: "position", coords: [ -3.691944, 40.418889 ] }

      >)
      time=2016-01-18T22:57:13.793CET | lvl=ERROR | trans=1453154140-565-00000000004 | function=getField | comp=Orion | msg=safeMongo.cpp[198]: Runtime Error (field 'coordinates' is missing in BSONObj <{}>)

      curl response:

      curl: (52) Empty reply from server
      No JSON object could be decoded

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        14h 17m 1 Fermín Galán 19/Jan/16 2:20 PM
        In Progress In Progress Impeded Impeded
        1s 1 Fermín Galán 19/Jan/16 2:20 PM
        Impeded Impeded In Progress In Progress
        1h 46m 1 Fermín Galán 19/Jan/16 4:06 PM
        In Progress In Progress Answered Answered
        2s 1 Fermín Galán 19/Jan/16 4:06 PM
        Answered Answered Closed Closed
        2s 1 Fermín Galán 19/Jan/16 4:06 PM

          People

          • Assignee:
            fermin Fermín Galán
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: