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

FIWARE.Question.Tech.Incompatibility with fiware/orion:2.0.0.

    Details

      Description

      Created question in FIWARE Q/A platform on 07-11-2018 at 09:11
      Please, ANSWER this question AT https://stackoverflow.com/questions/53185745/incompatibility-with-fiware-orion2-0-0

      Question:
      Incompatibility with fiware/orion:2.0.0

      Description:
      This is a question related with this issue

      https://github.com/ging/fiware-cygnus/issues/6

      I've deployed the iot stack with docker. These are the used containers:

      fiware/orion:2.0.0
      ging/fiware-cygnus:latest

      ging/fiware-cygnus:latest

      "Id": "sha256:b6baf1cbd18e6ba6ab5ec7d8e1d9c8a08bbc18b45037faa345e8465c890f454c",
      "RepoTags": [ "ging/fiware-cygnus:latest" ],
      "RepoDigests": [
      "ging/fiware-cygnus@sha256:4fcf44666651ca63f1a74203bc12a7ffd9a1268f8d514dff1a83db269a1c6923"
      ],
      "Created": "2018-10-17T15:52:19.749023834Z"

      [And other containers not involved in the issue ...]

      Currently the image fiware/orion:2.0.0 is sending the headers as follows.

      --------------------------------------------------
      Standard FlowFile Attributes
      Key: 'entryDate'
      Value: 'Wed Oct 31 12:15:25 UTC 2018'
      Key: 'lineageStartDate'
      Value: 'Wed Oct 31 12:15:25 UTC 2018'
      Key: 'fileSize'
      Value: '144'
      FlowFile Attribute Map Content
      Key: 'Accept'
      Value: 'application/json'
      Key: 'Content-Length'
      Value: '144'
      Key: 'Content-Type'
      Value: 'application/json; charset=UTF-8'
      Key: 'Fiware-Correlator'
      Value: 'a5a196d6-dd06-11e8-8f35-0242ac1c0004'
      Key: 'Fiware-Service'
      Value: 'testService'
      Key: 'Fiware-Servicepath'
      Value: '/testPath'
      Key: 'Host'
      Value: 'cygnus:5050'
      Key: 'Ngsiv2-AttrsFormat'
      Value: 'normalized'
      Key: 'User-Agent'
      Value: 'orion/2.0.0 libcurl/7.29.0'
      Key: 'filename'
      Value: '102283488692700'
      Key: 'path'
      Value: './'
      Key: 'restlistener.remote.source.host'
      Value: '172.28.0.4'
      Key: 'restlistener.remote.user.dn'
      Value: 'none'
      Key: 'restlistener.request.uri'
      Value: '/v2/notify'
      Key: 'uuid'
      Value: 'b20ecd8d-7d6e-4edd-be39-242a1ae1cc49'
      --------------------------------------------------

      Specifically, the header "Fiware-Servicepath" does not match what is expected this line of code. "fiware-servicepath," Fiware-ServicePath "," fiware-servicepath"

      And this causes the following error:

      `2018-10-31 12:15:41,201 ERROR [Timer-Driven Process Thread-1] o.a.nifi.processors.ngsi.NGSIToMongo NGSIToMongo[id=8f96c89d-850a-3578-b512-2b3f5f4fdacd] java.lang.NullPointerException

      I think that it is caused by this line

      String fiwareServicePath = (flowFile.getAttribute("fiware-servicepath")==null) ? flowFile.getAttribute("Fiware-ServicePath"):flowFile.getAttribute("fiware-servicepath");

      IN

      fiware-cygnus/nifi-ngsi-bundle/nifi-ngsi-processors/src/main/java/org/apache/nifi/processors/ngsi/NGSI/utils/NGSIUtils.java

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        HD-Enabler Cygnus [ 11304 ]
        Description
        Created question in FIWARE Q/A platform on 07-11-2018 at 09:11
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/53185745/incompatibility-with-fiware-orion2-0-0


        +Question:+
        Incompatibility with fiware/orion:2.0.0

        +Description:+
        This is a question related with this issue

        https://github.com/ging/fiware-cygnus/issues/6

        I've deployed the iot stack with docker. These are the used containers:


        fiware/orion:2.0.0
        ging/fiware-cygnus:latest


        ging/fiware-cygnus:latest

        "Id": "sha256:b6baf1cbd18e6ba6ab5ec7d8e1d9c8a08bbc18b45037faa345e8465c890f454c",
        "RepoTags": [ "ging/fiware-cygnus:latest" ],
        "RepoDigests": [
        "ging/fiware-cygnus@sha256:4fcf44666651ca63f1a74203bc12a7ffd9a1268f8d514dff1a83db269a1c6923"
        ],
        "Created": "2018-10-17T15:52:19.749023834Z"


        [And other containers not involved in the issue ...]

        Currently the image fiware/orion:2.0.0 is sending the headers as follows.

        --------------------------------------------------
        Standard FlowFile Attributes
        Key: 'entryDate'
                Value: 'Wed Oct 31 12:15:25 UTC 2018'
        Key: 'lineageStartDate'
                Value: 'Wed Oct 31 12:15:25 UTC 2018'
        Key: 'fileSize'
                Value: '144'
        FlowFile Attribute Map Content
        Key: 'Accept'
                Value: 'application/json'
        Key: 'Content-Length'
                Value: '144'
        Key: 'Content-Type'
                Value: 'application/json; charset=UTF-8'
        Key: 'Fiware-Correlator'
                Value: 'a5a196d6-dd06-11e8-8f35-0242ac1c0004'
        Key: 'Fiware-Service'
                Value: 'testService'
        Key: 'Fiware-Servicepath'
                Value: '/testPath'
        Key: 'Host'
                Value: 'cygnus:5050'
        Key: 'Ngsiv2-AttrsFormat'
                Value: 'normalized'
        Key: 'User-Agent'
                Value: 'orion/2.0.0 libcurl/7.29.0'
        Key: 'filename'
                Value: '102283488692700'
        Key: 'path'
                Value: './'
        Key: 'restlistener.remote.source.host'
                Value: '172.28.0.4'
        Key: 'restlistener.remote.user.dn'
                Value: 'none'
        Key: 'restlistener.request.uri'
                Value: '/v2/notify'
        Key: 'uuid'
                Value: 'b20ecd8d-7d6e-4edd-be39-242a1ae1cc49'
        --------------------------------------------------



          Specifically, the header "Fiware-Servicepath" does not match what is expected this line of code. "fiware-servicepath," Fiware-ServicePath "," fiware-servicepath"
          
          And this causes the following error:
          
          `2018-10-31 12:15:41,201 ERROR [Timer-Driven Process Thread-1] o.a.nifi.processors.ngsi.NGSIToMongo NGSIToMongo[id=8f96c89d-850a-3578-b512-2b3f5f4fdacd] java.lang.NullPointerException


        I think that it is caused by this line

        String fiwareServicePath = (flowFile.getAttribute("fiware-servicepath")==null) ? flowFile.getAttribute("Fiware-ServicePath"):flowFile.getAttribute("fiware-servicepath");


        IN

        fiware-cygnus/nifi-ngsi-bundle/nifi-ngsi-processors/src/main/java/org/apache/nifi/processors/ngsi/NGSI/utils/NGSIUtils.java
        Created question in FIWARE Q/A platform on 07-11-2018 at 09:11
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/53185745/incompatibility-with-fiware-orion2-0-0


        +Question:+
        Incompatibility with fiware/orion:2.0.0

        +Description:+
        This is a question related with this issue

        https://github.com/ging/fiware-cygnus/issues/6

        I've deployed the iot stack with docker. These are the used containers:


        fiware/orion:2.0.0
        ging/fiware-cygnus:latest


        ging/fiware-cygnus:latest

        "Id": "sha256:b6baf1cbd18e6ba6ab5ec7d8e1d9c8a08bbc18b45037faa345e8465c890f454c",
        "RepoTags": [ "ging/fiware-cygnus:latest" ],
        "RepoDigests": [
        "ging/fiware-cygnus@sha256:4fcf44666651ca63f1a74203bc12a7ffd9a1268f8d514dff1a83db269a1c6923"
        ],
        "Created": "2018-10-17T15:52:19.749023834Z"


        [And other containers not involved in the issue ...]

        Currently the image fiware/orion:2.0.0 is sending the headers as follows.

        --------------------------------------------------
        Standard FlowFile Attributes
        Key: 'entryDate'
                Value: 'Wed Oct 31 12:15:25 UTC 2018'
        Key: 'lineageStartDate'
                Value: 'Wed Oct 31 12:15:25 UTC 2018'
        Key: 'fileSize'
                Value: '144'
        FlowFile Attribute Map Content
        Key: 'Accept'
                Value: 'application/json'
        Key: 'Content-Length'
                Value: '144'
        Key: 'Content-Type'
                Value: 'application/json; charset=UTF-8'
        Key: 'Fiware-Correlator'
                Value: 'a5a196d6-dd06-11e8-8f35-0242ac1c0004'
        Key: 'Fiware-Service'
                Value: 'testService'
        Key: 'Fiware-Servicepath'
                Value: '/testPath'
        Key: 'Host'
                Value: 'cygnus:5050'
        Key: 'Ngsiv2-AttrsFormat'
                Value: 'normalized'
        Key: 'User-Agent'
                Value: 'orion/2.0.0 libcurl/7.29.0'
        Key: 'filename'
                Value: '102283488692700'
        Key: 'path'
                Value: './'
        Key: 'restlistener.remote.source.host'
                Value: '172.28.0.4'
        Key: 'restlistener.remote.user.dn'
                Value: 'none'
        Key: 'restlistener.request.uri'
                Value: '/v2/notify'
        Key: 'uuid'
                Value: 'b20ecd8d-7d6e-4edd-be39-242a1ae1cc49'
        --------------------------------------------------



          Specifically, the header "Fiware-Servicepath" does not match what is expected this line of code. "fiware-servicepath," Fiware-ServicePath "," fiware-servicepath"
          
          And this causes the following error:
          
          `2018-10-31 12:15:41,201 ERROR [Timer-Driven Process Thread-1] o.a.nifi.processors.ngsi.NGSIToMongo NGSIToMongo[id=8f96c89d-850a-3578-b512-2b3f5f4fdacd] java.lang.NullPointerException


        I think that it is caused by this line

        String fiwareServicePath = (flowFile.getAttribute("fiware-servicepath")==null) ? flowFile.getAttribute("Fiware-ServicePath"):flowFile.getAttribute("fiware-servicepath");


        IN

        fiware-cygnus/nifi-ngsi-bundle/nifi-ngsi-processors/src/main/java/org/apache/nifi/processors/ngsi/NGSI/utils/NGSIUtils.java
        backlogmanager Backlog Manager made changes -
        Summary [fiware-stackoverflow] Incompatibility with fiware/orion:2.0.0 FIWARE.Question.Tech.Incompatibility with fiware/orion:2.0.0.
        andres.munoza Andres Muñoz made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        andres.munoza Andres Muñoz made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        andres.munoza Andres Muñoz made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        joaquin.salvachua Joaquín Salvachúa made changes -
        Assignee Joaquín Salvachúa [ joaquin.salvachua ] Andres Muñoz [ andres.munoza ]
        jmcantera Jose Manuel Cantera made changes -
        Assignee Jose Manuel Cantera [ jmcantera ] Joaquín Salvachúa [ joaquin.salvachua ]
        veronika Veronika Vlnkova made changes -
        Assignee Jose Manuel Cantera [ jmcantera ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            andres.munoza Andres Muñoz
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: