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

[fiware-stackoverflow] Proton Orion Subscription - Error when parsing notification XML

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 02-03-2016 at 13:03
      Please, ANSWER this question AT https://stackoverflow.com/questions/35747048/proton-orion-subscription-error-when-parsing-notification-xml

      Question:
      Proton Orion Subscription - Error when parsing notification XML

      Description:
      I had configured Orion and Proton FIWARE Generic Enablers and made a subscription in Orion to send a notification to Proton when an entity of type Node is modified.

      It happens that Proton is returning an error related with the parsing of the received XML.

      proton | Mar 02, 2016 11:46:47 AM com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
      proton | INFO: started event message body reader
      proton | Mar 02, 2016 11:46:47 AM com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
      proton | INFO: Event: NodeContextUpdate
      proton | Mar 02, 2016 11:46:47 AM com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
      proton | SEVERE: Could not parse XML NGSI event java.lang.NullPointerException, reason: null
      proton | last attribute name: null last value: null

      I found that at least another user had posted a similar question but the answer to that question does not fits (and solve) my situation.

      EDIT:

      Here is the POST request that Proton has received:

      ........POST /ProtonOnWebServer/rest/events HTTP/1.1
      User-Agent: orion/0.27.0-next libcurl/7.19.7
      Host: 192.168.99.100:8080
      Accept: application/xml, application/json
      Content-length: 901
      Content-type: application/xml

      <notifyContextRequest>
      <subscriptionId>570b7cad849a7fd6c9ebaaf3</subscriptionId>
      <originator>localhost</originator>
      <contextResponseList>
      <contextElementResponse>
      <contextElement>
      <entityId type="Node" isPattern="false">
      <id>Node3</id>
      </entityId>
      <contextAttributeList>
      <contextAttribute>
      <name>temperature</name>
      <type>double</type>
      <contextValue>23</contextValue>
      </contextAttribute>
      <contextAttribute>
      <name>pressure</name>
      <type>double</type>
      <contextValue>15</contextValue>
      </contextAttribute>
      </contextAttributeList>
      </contextElement>
      <statusCode>
      <code>200</code>
      <reasonPhrase>OK</reasonPhrase>
      </statusCode>
      </contextElementResponse>
      </contextResponseList>
      </notifyContextRequest>

      Thank you.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 15:15|CREATED monitor | # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 15:15|CREATED monitor | # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 18:10|UPDATED status: transition Answer| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 18:10|UPDATED status: transition Answer| # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 21:10|UPDATED status: transition Finish| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 21:10|UPDATED status: transition Finish| # answers= 1, accepted answer= True

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: