[Backlogmanager] [FIWARE-JIRA] (HELP-6211) FIWARE.Request.Tech.Data.CEP.CEP problem

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-6211:
------------------------------------

    Assignee: Backlog Manager

> FIWARE.Request.Tech.Data.CEP.CEP problem
> ----------------------------------------
>
>                 Key: HELP-6211
>                 URL: https://jira.fiware.org/browse/HELP-6211
>             Project: Help-Desk
>          Issue Type: extRequest
>          Components: FIWARE-TECH-HELP
>            Reporter: ilknur chulani
>            Assignee: Backlog Manager
>            Priority: Blocker
>         Attachments: image001_01D184F987E3A020.png, ISTMOS.json, NEMEA_CEP (1).json
>
>
> Urgent question from a FINISH accelerator SME.
> ------------------------------------------------------------------------------
> Von: Anastasios Oikonomidis [mailto:t.oikonomidis at asn.gr]
> Gesendet: Dienstag, 22. März 2016 17:32
> An: Peter Einramhof <einramhof at atb-bremen.de<mailto:einramhof at atb-bremen.de>>
> Cc: 'Stamatis Poulimenos' <spoulimenos at asn.gr<mailto:spoulimenos at 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 at asn.gr<mailto:t.oikonomidis at asn.gr>
> _______________________________________________
> Fiware-finish-coaching mailing list
> Fiware-finish-coaching at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-finish-coaching



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)