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

FIWARE.Request.Tech.Data.CEP.CEP problem

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Blocker
    • Resolution: Dismissed
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Data
    • HD-Enabler:
      CEP

      Description

      Urgent question from a FINISH accelerator SME.
      ------------------------------------------------------------------------------

      Von: Anastasios Oikonomidis t.oikonomidis@asn.gr
      Gesendet: Dienstag, 22. März 2016 17:32
      An: Peter Einramhof <einramhof@atb-bremen.de<einramhof@atb-bremen.de>>
      Cc: 'Stamatis Poulimenos' <spoulimenos@asn.gr<spoulimenos@asn.gr>>
      Betreff: CEP remains problematic
      Wichtigkeit: Hoch

      Hallo Peter,

      We have done a lot of work regarding CEP and more than a lot of efforts, but it remains very problematic.

      We have created a CEP project (find JSON file attached as ISTMOS.json).

      We have stopped and started the engine as it is described in the documentation:

      PUT: http://my.ip:my_port/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer
      BODY FOR STOP:

      {"action":"ChangeState","state":"stop"}

      BODY FOR START:

      {"action":"ChangeState","state":"start"}

      We have exported the JSON file of the project through the AuthoringTool to the appropriate folder.

      There is only one simple EPA (Basic) in the project, a temporal context that runs always and a REST consumer to send data to a remote script for debugging (final destination will be the Orion CB).
      Unfortunately, despite our numerous efforts (restarting tomcat, restarting the engine, even rebooting the VM dozens of times) we keep receiving the following message:

      500 Internal Server Error
      Could not parse json event java.lang.NullPointerException, reason: null

      The following text is from the catalina.out log file:

      INFO: started event message body reader
      Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
      INFO: name value: from_gateway looking for: Name
      Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
      SEVERE: Could not parse json event java.lang.NullPointerException, reason: null
      on timer - composite context instance, with TERMINATOR at 1458661813110
      on timer - composite context instance, with TERMINATOR at 1458661815661

      Before all these, we have created another project (NEMEA_CEP.json) and we have managed to send events and get feedback from the consumer.
      Right now the very same project responds well to POSTs but returns absolutely no feedback via consumer while we haven’t changed the JSON file!

      We have tried with different kinds of instances within the FIWARE cloud, finally the only one that seems to work well is the CEP_r3.3.3 which is based on a Spanish system.
      We saw that others also use the same system, so we have concluded it is the most stable and reliable. Yet, it doesn’t seem to work as it is expected, or there is an error very well hidden.
      One more remark we would like to make is that it is not possible to send any kind of events to any CEP instance unless we edit the /opt/tomcat10/webapps/ISTMOS/EmptyDefinition.json file! So, each time we need to change anything, we should first execute a GET http://my.ip:my_port/ProtonOnWebServerAdmin/resources/definitions/ISTMOS call in order to retrieve all definitions in detail and add them manually to the relevant EmtpyDefinition.json file! That is really a hard task, prone to create mistakes. Even though, we have performed this task very carefully every time, but still no luck.

      We have thoroughly read every possible documentation, users and developers guide, watched videos and presentations, dozens of relevant questions we have found online but still we have found no answer to our problem.

      So, please, we need your help to dig deeper into CEP and get it to work. Maybe a WebX call in order to show your our efforts on screen would be helpful, or anything else that you suggest.

      Thank you very much in advance

      Best regards

      [ASN_SmallLogo]
      Tasos Oikonomidis
      Software Development Manager
      E: t.oikonomidis@asn.gr<t.oikonomidis@asn.gr>

      _______________________________________________
      Fiware-finish-coaching mailing list
      Fiware-finish-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-finish-coaching

      1. ISTMOS.json
        5 kB
        Karaboga, Burak
      2. NEMEA_CEP (1).json
        4 kB
        Karaboga, Burak
      1. image001_01D184F987E3A020.png
        4 kB

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          33m 30s 1 Karaboga, Burak 23/Mar/16 12:15 PM
          fla Fernando Lopez made changes -
          Fix Version/s 2021 [ 12600 ]
          fla Fernando Lopez made changes -
          Assignee Backlog Manager [ backlogmanager ]
          mev Manuel Escriche made changes -
          Assignee Karaboga, Burak [ burak ]
          mev Manuel Escriche made changes -
          Assignee Karaboga, Burak [ burak ]
          backlogmanager Backlog Manager made changes -
          Summary FIWARE.Request.Tech.CEP problem FIWARE.Request.Tech.Data.CEP.CEP problem
          HD-Chapter Data [ 10838 ]
          mev Manuel Escriche made changes -
          HD-Enabler CEP [ 10869 ]
          backlogmanager Backlog Manager made changes -
          Summary [Fiware-finish-coaching] CEP problem FIWARE.Request.Tech.CEP problem
          burak Karaboga, Burak made changes -
          Resolution Dismissed [ 10102 ]
          Status Open [ 1 ] Closed [ 6 ]
          burak Karaboga, Burak made changes -
          Attachment NEMEA_CEP (1).json [ 20040 ]
          Attachment ISTMOS.json [ 20041 ]
          Attachment image001_01D184F987E3A020.png [ 20042 ]
          ichulani ilknur chulani made changes -
          Description From: Peter Einramhof [mailto:einramhof@atb-bremen.de]
          Sent: Wednesday, March 23, 2016 11:38 AM
          To: Chulani, Ilknur
          Subject: WG: CEP remains problematic
          Importance: High

          Dear Ilknur,

          one of our FInish teams keeps encountering issues with the Complex Event Processing GE.
          They have tried numerous things already, but they never managed to really solve the issues – see below.

          Do you have any suggestion how to solve this issue or can you point out the most appropriate person/way for dealing with this issue?

          Thanks in advance and best regards,
          Peter.


          Von: Anastasios Oikonomidis [mailto:t.oikonomidis@asn.gr]
          Gesendet: Dienstag, 22. März 2016 17:32
          An: Peter Einramhof <einramhof@atb-bremen.de<mailto:einramhof@atb-bremen.de>>
          Cc: 'Stamatis Poulimenos' <spoulimenos@asn.gr<mailto:spoulimenos@asn.gr>>
          Betreff: CEP remains problematic
          Wichtigkeit: Hoch

          Hallo Peter,

          We have done a lot of work regarding CEP and more than a lot of efforts, but it remains very problematic.

          We have created a CEP project (find JSON file attached as ISTMOS.json).

          We have stopped and started the engine as it is described in the documentation:

          PUT: http://my.ip:my_port/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer
          BODY FOR STOP: {"action":"ChangeState","state":"stop"}
          BODY FOR START: {"action":"ChangeState","state":"start"}

          We have exported the JSON file of the project through the AuthoringTool to the appropriate folder.

          There is only one simple EPA (Basic) in the project, a temporal context that runs always and a REST consumer to send data to a remote script for debugging (final destination will be the Orion CB).
          Unfortunately, despite our numerous efforts (restarting tomcat, restarting the engine, even rebooting the VM dozens of times) we keep receiving the following message:

          500 Internal Server Error
          Could not parse json event java.lang.NullPointerException, reason: null

          The following text is from the catalina.out log file:

          INFO: started event message body reader
          Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          INFO: name value: from_gateway looking for: Name
          Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          SEVERE: Could not parse json event java.lang.NullPointerException, reason: null
          on timer - composite context instance, with TERMINATOR at 1458661813110
          on timer - composite context instance, with TERMINATOR at 1458661815661

          Before all these, we have created another project (NEMEA_CEP.json) and we have managed to send events and get feedback from the consumer.
          Right now the very same project responds well to POSTs but returns absolutely no feedback via consumer while we haven’t changed the JSON file!

          We have tried with different kinds of instances within the FIWARE cloud, finally the only one that seems to work well is the CEP_r3.3.3 which is based on a Spanish system.
          We saw that others also use the same system, so we have concluded it is the most stable and reliable. Yet, it doesn’t seem to work as it is expected, or there is an error very well hidden.
          One more remark we would like to make is that it is not possible to send any kind of events to any CEP instance unless we edit the /opt/tomcat10/webapps/ISTMOS/EmptyDefinition.json file! So, each time we need to change anything, we should first execute a GET http://my.ip:my_port/ProtonOnWebServerAdmin/resources/definitions/ISTMOS call in order to retrieve all definitions in detail and add them manually to the relevant EmtpyDefinition.json file! That is really a hard task, prone to create mistakes. Even though, we have performed this task very carefully every time, but still no luck.

          We have thoroughly read every possible documentation, users and developers guide, watched videos and presentations, dozens of relevant questions we have found online but still we have found no answer to our problem.

          So, please, we need your help to dig deeper into CEP and get it to work. Maybe a WebX call in order to show your our efforts on screen would be helpful, or anything else that you suggest.

          Thank you very much in advance

          Best regards

          [ASN_SmallLogo]
          Tasos Oikonomidis
          Software Development Manager
          E: t.oikonomidis@asn.gr<mailto:t.oikonomidis@asn.gr>

          _______________________________________________
          Fiware-finish-coaching mailing list
          Fiware-finish-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-finish-coaching
          Urgent question from a FINISH accelerator SME.
          ------------------------------------------------------------------------------

          Von: Anastasios Oikonomidis [mailto:t.oikonomidis@asn.gr]
          Gesendet: Dienstag, 22. März 2016 17:32
          An: Peter Einramhof <einramhof@atb-bremen.de<mailto:einramhof@atb-bremen.de>>
          Cc: 'Stamatis Poulimenos' <spoulimenos@asn.gr<mailto:spoulimenos@asn.gr>>
          Betreff: CEP remains problematic
          Wichtigkeit: Hoch

          Hallo Peter,

          We have done a lot of work regarding CEP and more than a lot of efforts, but it remains very problematic.

          We have created a CEP project (find JSON file attached as ISTMOS.json).

          We have stopped and started the engine as it is described in the documentation:

          PUT: http://my.ip:my_port/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer
          BODY FOR STOP: {"action":"ChangeState","state":"stop"}
          BODY FOR START: {"action":"ChangeState","state":"start"}

          We have exported the JSON file of the project through the AuthoringTool to the appropriate folder.

          There is only one simple EPA (Basic) in the project, a temporal context that runs always and a REST consumer to send data to a remote script for debugging (final destination will be the Orion CB).
          Unfortunately, despite our numerous efforts (restarting tomcat, restarting the engine, even rebooting the VM dozens of times) we keep receiving the following message:

          500 Internal Server Error
          Could not parse json event java.lang.NullPointerException, reason: null

          The following text is from the catalina.out log file:

          INFO: started event message body reader
          Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          INFO: name value: from_gateway looking for: Name
          Mar 22, 2016 4:48:10 PM com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          SEVERE: Could not parse json event java.lang.NullPointerException, reason: null
          on timer - composite context instance, with TERMINATOR at 1458661813110
          on timer - composite context instance, with TERMINATOR at 1458661815661

          Before all these, we have created another project (NEMEA_CEP.json) and we have managed to send events and get feedback from the consumer.
          Right now the very same project responds well to POSTs but returns absolutely no feedback via consumer while we haven’t changed the JSON file!

          We have tried with different kinds of instances within the FIWARE cloud, finally the only one that seems to work well is the CEP_r3.3.3 which is based on a Spanish system.
          We saw that others also use the same system, so we have concluded it is the most stable and reliable. Yet, it doesn’t seem to work as it is expected, or there is an error very well hidden.
          One more remark we would like to make is that it is not possible to send any kind of events to any CEP instance unless we edit the /opt/tomcat10/webapps/ISTMOS/EmptyDefinition.json file! So, each time we need to change anything, we should first execute a GET http://my.ip:my_port/ProtonOnWebServerAdmin/resources/definitions/ISTMOS call in order to retrieve all definitions in detail and add them manually to the relevant EmtpyDefinition.json file! That is really a hard task, prone to create mistakes. Even though, we have performed this task very carefully every time, but still no luck.

          We have thoroughly read every possible documentation, users and developers guide, watched videos and presentations, dozens of relevant questions we have found online but still we have found no answer to our problem.

          So, please, we need your help to dig deeper into CEP and get it to work. Maybe a WebX call in order to show your our efforts on screen would be helpful, or anything else that you suggest.

          Thank you very much in advance

          Best regards

          [ASN_SmallLogo]
          Tasos Oikonomidis
          Software Development Manager
          E: t.oikonomidis@asn.gr<mailto:t.oikonomidis@asn.gr>

          _______________________________________________
          Fiware-finish-coaching mailing list
          Fiware-finish-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-finish-coaching
          backlogmanager Backlog Manager made changes -
          Field Original Value New Value
          Link This issue relates to HELC-1337 [ HELC-1337 ]
          backlogmanager Backlog Manager created issue -

            People

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

              Dates

              • Created:
                Updated:
                Resolved: