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

FIWARE.Request.Tech.Data.CEP.Problem with CEP

        Details

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

          Description

          Hi,

          We are experiencing an error when using Proton. We are using Proton in combination with fiware/Orion.
          In the logs of the tomcat server I have found this error (see attachment):

          Jul 29, 2015 12:06:02 PM com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
          SEVERE: Could not parse XML NGSI event java.lang.NullPointerException, reason: null
          last attribute name: null last value: null

          I think it has something to do with the two files from the protonserver and proton admin server. From the documentation on the Fi-ware Wiki we found that we could adapt the two files:

          • Proton.propterties
          • Protonadmin.propterties

          Could you provide some insights into the relation between

          • the metadataFileName in Proton.propterties --> to what file should this point, the CEP.json file?
          • Definitions_repository_location in Protonadmin.properties.

          I feel we are having a mismatch between those 3 parameters. Stackoverflow or jira.fiware did not help me any further and we are stuck on this topic.
          I do think the proton engine is running, since I do not get an error when browsing to the page ip:port/ProtonOnWebServer1/rest/events

          Do you have any idea what the exact problem is? I have attached the files.

          Kind regards,

          Hans-Christian van der Werf

          Disclaimer
          Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

          This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.

          _______________________________________________
          Fiware-tech-help mailing list
          Fiware-tech-help@lists.fi-ware.org
          https://lists.fi-ware.org/listinfo/fiware-tech-help

          [Created via e-mail received from: "Werf, Hans-christian van der" <Hans-christian.van.der.Werf@ordina.nl>]

          1. File
            protonadmin.properties
            2 kB
            FW External User
          2. File
            proton.properties
            1 kB
            FW External User
          3. Text File
            catalina out.txt
            3 kB
            FW External User

            Activity

            Hide
            Permalink
            TALI Fabiana Fournier added a comment -

            Hello Hans-Christian.

            First, I would advise you to look at the appendix "Context Broker" in the Proton User Guide which can be downloaded from FIWARE at: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/CEP_GE_-_IBM_Proactive_Technology_Online_User_and_Programmer_Guide

            About the files you mentioned:
            Protonadmin.properties - shouldn't be modified. It should work as it is.
            Proton.properties - the metadataFileName should indeed point to the json definitions file that you're exporting from the Authoring tool.

            By the logs you sent me, my guess is that either you have a corrupted version of the ProtonOnWebServer.war file, which you can redownload from FIWARE / GIT repository.
            My second guess is that you are pointing to an invalid json file / an empty one. As can be seen in the file "proton.properties" you sent us, this could be the case, as you are pointing to EmptyDefinitions.json, which is a default that we put there, but do need to be edited.

            Please note, that when ProtonOnWebServer does deploy correctly on Tomcat, you should see in the logs a message similar to this:

            INFO: Properties are :
            metadatFile =/<metadataFileName>.json
            inputPortNumber =3002
            outputPortNumber =3302

            Please try to work around with all these ideas, and let me know if I can help you any further.

            Regards,

            Itai Peri
            Software Developer
            Smart Decisions Group

            Show
            TALI Fabiana Fournier added a comment - Hello Hans-Christian. First, I would advise you to look at the appendix "Context Broker" in the Proton User Guide which can be downloaded from FIWARE at: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/CEP_GE_-_IBM_Proactive_Technology_Online_User_and_Programmer_Guide About the files you mentioned: Protonadmin.properties - shouldn't be modified. It should work as it is. Proton.properties - the metadataFileName should indeed point to the json definitions file that you're exporting from the Authoring tool. By the logs you sent me, my guess is that either you have a corrupted version of the ProtonOnWebServer.war file, which you can redownload from FIWARE / GIT repository. My second guess is that you are pointing to an invalid json file / an empty one. As can be seen in the file "proton.properties" you sent us, this could be the case, as you are pointing to EmptyDefinitions.json, which is a default that we put there, but do need to be edited. Please note, that when ProtonOnWebServer does deploy correctly on Tomcat, you should see in the logs a message similar to this: INFO: Properties are : metadatFile =/<metadataFileName>.json inputPortNumber =3002 outputPortNumber =3302 Please try to work around with all these ideas, and let me know if I can help you any further. Regards, Itai Peri Software Developer Smart Decisions Group

              People

              • Assignee:
                TALI Fabiana Fournier
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: