From: Peter Einramhof 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 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:

BODY FOR 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