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

FIWARE.Request.Tech.Data.CEP.[Fiware-finodex-coaching] CEP problem

        Details

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

          Description

          We are having troubles while running IBM CEP. We have deployed it in our
          server. When an event occurs, we dont obtain any output event or file and
          we get this in catalina log:

          may 20, 2015 8:53:52 AM
          com.ibm.hrl.proton.admin.webapp.resources.DefinitionsResource
          getAllDefinitions
          INFORMACIÓN: starting getAllDefinitions
          may 20, 2015 8:53:52 AM
          com.ibm.hrl.proton.admin.webapp.resources.DefinitionsResource
          getAllDefinitions
          INFORMACIÓN: finished getAllDefinitions
          may 20, 2015 8:54:22 AM
          com.ibm.hrl.proton.admin.webapp.resources.DefinitionsResource
          getAllDefinitions
          INFORMACIÓN: starting getAllDefinitions
          may 20, 2015 8:54:22 AM
          com.ibm.hrl.proton.admin.webapp.resources.DefinitionsResource
          getAllDefinitions
          INFORMACIÓN: finished getAllDefinitions
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: starting updateInstanceState
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: perfoming action: change definitions...
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          performServiceCall
          INFORMACIÓN: performing request:
          http://localhost:8080/manager/text/stop?path=/ProtonOnWebServer
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: properties file
          path:/usr/local/tomcat7/webapps/ProtonOnWebServer/Proton.properties
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: new definitions file path: /usr/local/CEP/set1.json
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          performServiceCall
          INFORMACIÓN: performing request:
          http://localhost:8080/manager/text/start?path=/ProtonOnWebServer
          may 20, 2015 9:22:17 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: finished updateInstanceState
          may 20, 2015 9:22:33 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: starting updateInstanceState
          may 20, 2015 9:22:33 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: perfoming action: change state to stop
          may 20, 2015 9:22:33 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          performServiceCall
          INFORMACIÓN: performing request:
          http://localhost:8080/manager/text/stop?path=/ProtonOnWebServer
          may 20, 2015 9:22:33 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: finished updateInstanceState
          may 20, 2015 9:22:45 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: starting updateInstanceState
          may 20, 2015 9:22:45 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: perfoming action: change state to start
          may 20, 2015 9:22:45 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          performServiceCall
          INFORMACIÓN: performing request:
          http://localhost:8080/manager/text/start?path=/ProtonOnWebServer
          may 20, 2015 9:22:45 AM
          com.ibm.hrl.proton.admin.webapp.resources.ProtonInstancesResource
          updateInstanceState
          INFORMACIÓN: finished updateInstanceState
          may 20, 2015 9:28:05 AM
          com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          INFORMACIÓN: started event message body reader
          may 20, 2015 9:28:06 AM
          com.ibm.hrl.proton.webapp.providers.EventJSONMessageReader readFrom
          GRAVE: Could not parse json event org.apache.wink.json4j.JSONException: The
          key [Name] was not in the map, reason: The key [Name] was not in the map
          may 20, 2015 9:38:52 AM
          com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
          INFORMACIÓN: started event message body reader
          may 20, 2015 9:38:52 AM
          com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
          INFORMACIÓN: Event: TripContextUpdate
          may 20, 2015 9:38:52 AM
          com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
          GRAVE: Could not parse XML NGSI event java.lang.NullPointerException,
          reason: null
          last attribute name: null last value: null
          may 20, 2015 9:38:52 AM
          com.ibm.hrl.proton.webapp.providers.EventXmlNgsiMessageReader readFrom
          INFORMACIÓN: finished event message body reader
          may 20, 2015 9:38:52 AM com.ibm.hrl.proton.webapp.resources.EventResource
          submitNewEvent
          INFORMACIÓN: starting submitNewEvent
          may 20, 2015 9:38:52 AM com.ibm.hrl.proton.webapp.resources.EventResource
          submitNewEvent
          GRAVE: Could not send event, reason: java.lang.NullPointerException,
          message: null

          –

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

          [Created via e-mail received from: MAPT Talkykar <miguel@talkykar.com>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-850 FIWARE.Request.Coach.FINODEX.CEP problem

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              backlogmanager Backlog Manager added a comment -

              Assignee before migration = Tali Yatzkar Haham

              Show
              backlogmanager Backlog Manager added a comment - Assignee before migration = Tali Yatzkar Haham
              Hide
              Permalink
              backlogmanager Backlog Manager added a comment -

              Original time span = 29 days, 0:10:17

              Show
              backlogmanager Backlog Manager added a comment - Original time span = 29 days, 0:10:17
              Hide
              Permalink
              TALI Fabiana Fournier added a comment -

              Dear Miguel,

              I got this issue only now, I'm not sure if you solved it by now or not.
              From the log it seems that the CEP can't process the event you sent it.

              If you still has this problem please stop tomcat, delete the log, start again, and send me the:
              1. New log file
              2. The CEP definition file the CEP is running with
              3. The input events you send to the CEP (together with the headers if you are using the REST api).

              Thanks,
              Tali Yatzkar Haham,
              FIWARE CEP

              Show
              TALI Fabiana Fournier added a comment - Dear Miguel, I got this issue only now, I'm not sure if you solved it by now or not. From the log it seems that the CEP can't process the event you sent it. If you still has this problem please stop tomcat, delete the log, start again, and send me the: 1. New log file 2. The CEP definition file the CEP is running with 3. The input events you send to the CEP (together with the headers if you are using the REST api). Thanks, Tali Yatzkar Haham, FIWARE CEP

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: