[Fiware-finish-coaching] CEP problem

[Chulani, Ilknur]

From: Peter Einramhof [mailto:einramhof at 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 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
Markou Mpotsari 1, Pefki, 15121, Athens, Greece
T: +30 2114001506
F: +30 2103001507
M: +30 6947707094
E: t.oikonomidis at asn.gr<mailto:t.oikonomidis at asn.gr>
skype: aoikon68

ATOS WARNING !
This message contains attachments that could potentially harm your computer.
Please make sure you open ONLY attachments from senders you know, trust and is in an e-mail that you are expecting.

AVERTISSEMENT ATOS !
Ce message contient des pièces jointes qui peuvent potentiellement endommager votre ordinateur.
Merci de vous assurer que vous ouvrez uniquement les pièces jointes provenant d’emails que vous attendez et dont vous connaissez les expéditeurs et leur faites confiance.

AVISO DE ATOS !
Este mensaje contiene datos adjuntos que pudiera ser que dañaran su ordenador.
Asegúrese de abrir SOLO datos adjuntos enviados desde remitentes de confianza y que procedan de un correo esperado.

ATOS WARNUNG !
Diese E-Mail enthält Anlagen, welche möglicherweise ihren Computer beschädigen könnten.
Bitte beachten Sie, daß Sie NUR Anlagen öffnen, von einem Absender den Sie kennen, vertrauen und vom dem Sie vor allem auch E-Mails mit Anlagen erwarten.
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-finish-coaching/attachments/20160323/04ac2a7e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4042 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-finish-coaching/attachments/20160323/04ac2a7e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ISTMOS.json
Type: application/octet-stream
Size: 4970 bytes
Desc: ISTMOS.json
URL: <https://lists.fiware.org/private/fiware-finish-coaching/attachments/20160323/04ac2a7e/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEMEA_CEP (1).json
Type: application/octet-stream
Size: 3665 bytes
Desc: NEMEA_CEP (1).json
URL: <https://lists.fiware.org/private/fiware-finish-coaching/attachments/20160323/04ac2a7e/attachment-0001.obj>