[HELP-12992] FIWARE.Request.Tech.Problem sending a CEP-Proton event to FIWARE ORION Context BRoker. - JIRA

Details

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

Sender Email:
dario.pellegrino@eng.it,stefano.depanfilis@fiware.org,jira-help-desk@jira.fiware.org
External Participants:
dario.pellegrino@eng.it,fiware-tech-help@lists.fiware.org
HD-Chapter:
Data
HD-Enabler:
Orion

Description

Dear all,

I have installed a CEP-PROTON instance and I am trying to configure it to
receive and send events from/to an ORION context broker instance. I have
configured on ORION a subscription to notify an event to CEP and it works
properly, but I have a problem to send an event to ORION.

When I receive the event from ORION I have configured a consumer (following
the documentation) to send the event to an entity on ORION but it does not
work

Here the Proton LOG

INFO: routeTimedObject: forwarding event KPIWasteContainer; entityType=KPI;
Certainty=0.0; Duration=0.0; entityId=KPI:PRUEBA; ExpirationTime=null;
Cost=0.0; Annotation=; Name=KPIWasteContainer; OccurrenceTime=1511871926381;
result=1450.0; EventSource=; EventId=56250546-f321-4c4c-b4ab-bfc18d2697da;
DetectionTime=1511871926381; Chronon=null; to consumer...

Nov 28, 2017 12:25:26 PM
com.ibm.hrl.proton.server.executorServices.SimpleThreadFactory$ProtonExcepti
onHandler uncaughtException

SEVERE: Uncaught exception in thread: Thread[2,5,main],exception:
com.ibm.hrl.proton.adapters.rest.client.RESTException:
com.ibm.hrl.proton.adapters.rest.client.RESTException: Could not perform
POST of event instance:

{"OccurrenceTime":"28\/11\/2017-12:25:26","result":"1450.0","EventSource":"" ,"entityType":"KPI","Certainty":"0.0","EventId":"56250546-f321-4c4c-b4ab-bfc 18d2697da","DetectionTime":"28\/11\/2017-12:25:26","Duration":"0.0","entityI d":"KPI:PRUEBA","Cost":"0.0","Annotation":"","Name":"KPIWasteContainer"}

with request headers:

Content-Type: application/json

User-Agent: Jakarta Commons-HttpClient/3.0

Host: 130.206.117.164

Content-Length: 300

to consumer http://130.206.117.164/v2/entities, responce result: 400

Here the Orion log

time=2017-11-28T12:22:33.711Z | lvl=INFO |
corr=cfc3807a-d436-11e7-9e79-fa163eab214f | trans=1511363186-603-00000000206

from=pending

srv=pending

subsrv=pending

comp=Orion

op=logMsg.h[1808]:lmTransactionStart | msg=Starting transaction from
192.168.240.127:60684/v2/entities

time=2017-11-28T12:22:33.711Z | lvl=WARN |
corr=cfc3807a-d436-11e7-9e79-fa163eab214f | trans=1511363186-603-00000000206

from=130.206.122.186

srv=pending

subsrv=<default>

comp=Orion

op=AlarmManager.cpp[405]:badInput | msg=Raising alarm BadInput
192.168.240.127: No entity id specified

time=2017-11-28T12:22:33.711Z | lvl=INFO |
corr=cfc3807a-d436-11e7-9e79-fa163eab214f | trans=1511363186-603-00000000206

from=130.206.122.186

srv=pending

subsrv=<default>

comp=Orion

op=logMsg.h[1892]:lmTransactionEnd | msg=Transaction ended

It seems that PROTON does not create correctly the rest call to ORION.

I have followed the documentation and in particular the Appendix A:
Integration with NGSI in the FIWARE project "Integration with Context Broker
JSON Format" and I do not know what I am doing wrong..

I have updated PROTON with the last versions of the WAR files.

Find attached the screenshoot of my consumer config and the json file with
my project on PROTON.

I hope you can help me .

Thanks in advance.

Best regards,

Dario Pellegrino

Dario Pellegrino
Direzione Ricerca e Innovazione - R&D Lab
<dario.pellegrino@eng.it> dario.pellegrino@eng.it

Engineering Ingegneria Informatica spa
Viale Regione Siciliana, 7275 - 90146 Palermo(Italy)
Phone: +39-091.7511864
Mobile: +39-392.4674892

Twitter: @DPellegrino73

<http://www.eng.it/> www.eng.it

__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the following links:

Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

[Created via e-mail received from: Dario Pellegrino <dario.pellegrino@eng.it>]

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

[FIWARE-JIRA] (HELP-12992) [Fiware-tech-help] Problem sending a CEP-Proton event to FIWARE ORION Context BRoker

27/Dec/17 5:33 AM

9 kB

FW External User
w4t (2).json

28/Nov/17 1:24 PM

2 kB

FW External User

image002_01D3686C83022970.jpg

24 kB

29/Nov/17 4:28 AM
image002_01D3686C83022970.jpg

24 kB

28/Nov/17 1:24 PM

Activity

Ascending order - Click to sort in descending order

FW External User created issue - 28/Nov/17 1:24 PM

Backlog Manager made changes - 28/Nov/17 1:29 PM

Field	Original Value	New Value
Component/s		FIWARE-TECH-HELP [ 10278 ]

Stefano De Panfilis made changes - 29/Nov/17 4:28 AM

External Participants		dario.pellegrino@eng.it,fiware-tech-help@lists.fiware.org
Sender Email	dario.pellegrino@eng.it	dario.pellegrino@eng.it,stefano.depanfilis@fiware.org

Hide

Permalink

Stefano De Panfilis added a comment - 29/Nov/17 4:28 AM

Dear Veronika,

Have you assigned this to Fabiana?

@dario: just in case have you checked this with Pasquale?

Ciao
Stefano

Il 28 Nov 2017 5:16 PM, "Dario Pellegrino" <dario.pellegrino@eng.it> ha
scritto:

> Dear all,
>
> I have installed a CEP-PROTON instance and I am trying to configure it to
> receive and send events from/to an ORION context broker instance. I have
> configured on ORION a subscription to notify an event to CEP and it works
> properly, but I have a problem to send an event to ORION.
>
> When I receive the event from ORION I have configured a consumer
> (following the documentation) to send the event to an entity on ORION but
> it does not work
>
>
>
> Here the Proton LOG
>
>
>
> *INFO: routeTimedObject: forwarding event KPIWasteContainer;
> entityType=KPI; Certainty=0.0; Duration=0.0; entityId=KPI:PRUEBA;
> ExpirationTime=null; Cost=0.0; Annotation=; Name=KPIWasteContainer;
> OccurrenceTime=1511871926381; result=1450.0; EventSource=;
> EventId=56250546-f321-4c4c-b4ab-bfc18d2697da; DetectionTime=1511871926381;
> Chronon=null; to consumer...*
>
> *Nov 28, 2017 12:25:26 PM
> com.ibm.hrl.proton.server.executorServices.SimpleThreadFactory$ProtonExceptionHandler
> uncaughtException*
>
> *SEVERE: Uncaught exception in thread: Thread[2,5,main],exception:
> com.ibm.hrl.proton.adapters.rest.client.RESTException:
> com.ibm.hrl.proton.adapters.rest.client.RESTException: Could not perform
> POST of event instance:*
>
>
> *

{"OccurrenceTime":"28\/11\/2017-12:25:26","result":"1450.0","EventSource":"","entityType":"KPI","Certainty":"0.0","EventId":"56250546-f321-4c4c-b4ab-bfc18d2697da","DetectionTime":"28\/11\/2017-12:25:26","Duration":"0.0","entityId":"KPI:PRUEBA","Cost":"0.0","Annotation":"","Name":"KPIWasteContainer"}

*
>
> with request headers:
>
> Content-Type: application/json
>
>
>
> User-Agent: Jakarta Commons-HttpClient/3.0
>
>
>
> Host: 130.206.117.164
>
>
>
> Content-Length: 300
>
>
>
> *to consumer http://130.206.117.164/v2/entities
> <http://130.206.117.164/v2/entities>, responce result: 400*
>
>
>
>
>
> Here the Orion log
>
> *time=2017-11-28T12:22:33.711Z | lvl=INFO |
> corr=cfc3807a-d436-11e7-9e79-fa163eab214f |
> trans=1511363186-603-00000000206 | from=pending | srv=pending |
> subsrv=pending | comp=Orion | op=logMsg.h[1808]:lmTransactionStart |
> msg=Starting transaction from 192.168.240.127:60684/v2/entities
> <http://192.168.240.127:60684/v2/entities>*
>
> *time=2017-11-28T12:22:33.711Z | lvl=WARN |
> corr=cfc3807a-d436-11e7-9e79-fa163eab214f |
> trans=1511363186-603-00000000206 | from=130.206.122.186 | srv=pending |
> subsrv=<default> | comp=Orion | op=AlarmManager.cpp[405]:badInput |
> msg=Raising alarm BadInput 192.168.240.127 <http://192.168.240.127>: No
> entity id specified*
>
> *time=2017-11-28T12:22:33.711Z | lvl=INFO |
> corr=cfc3807a-d436-11e7-9e79-fa163eab214f |
> trans=1511363186-603-00000000206 | from=130.206.122.186 | srv=pending |
> subsrv=<default> | comp=Orion | op=logMsg.h[1892]:lmTransactionEnd |
> msg=Transaction ended*
>
>
>
>
>
> It seems that PROTON does not create correctly the rest call to ORION.
>
> I have followed the documentation and in particular the Appendix A:
> Integration with NGSI in the FIWARE project “Integration with Context
> Broker JSON Format” and I do not know what I am doing wrong….
>
> I have updated PROTON with the last versions of the WAR files.
>
>
>
> Find attached the screenshoot of my consumer config and the json file with
> my project on PROTON.
>
>
>
> I hope you can help me .
>
> Thanks in advance.
>
> Best regards,
>
> Dario Pellegrino
>
>
>
>
>
> Dario Pellegrino
> Direzione Ricerca e Innovazione - R&D Lab
> dario.pellegrino@eng.it
>
> Engineering Ingegneria Informatica spa
> Viale Regione Siciliana, 7275 - 90146 Palermo(Italy)
> Phone: +39-091.7511864 <+39%20091%20751%201864>
> Mobile: +39-392.4674892 <+39%20392%20467%204892>
>
> Twitter: @DPellegrino73
>
> www.eng.it
>
>
>
>
>
>
>
>
>
>

Show

Stefano De Panfilis added a comment - 29/Nov/17 4:28 AM Dear Veronika, Have you assigned this to Fabiana? @dario: just in case have you checked this with Pasquale? Ciao Stefano Il 28 Nov 2017 5:16 PM, "Dario Pellegrino" <dario.pellegrino@eng.it> ha scritto: > Dear all, > > I have installed a CEP-PROTON instance and I am trying to configure it to > receive and send events from/to an ORION context broker instance. I have > configured on ORION a subscription to notify an event to CEP and it works > properly, but I have a problem to send an event to ORION. > > When I receive the event from ORION I have configured a consumer > (following the documentation) to send the event to an entity on ORION but > it does not work > > > > Here the Proton LOG > > > > *INFO: routeTimedObject: forwarding event KPIWasteContainer; > entityType=KPI; Certainty=0.0; Duration=0.0; entityId=KPI:PRUEBA; > ExpirationTime=null; Cost=0.0; Annotation=; Name=KPIWasteContainer; > OccurrenceTime=1511871926381; result=1450.0; EventSource=; > EventId=56250546-f321-4c4c-b4ab-bfc18d2697da; DetectionTime=1511871926381; > Chronon=null; to consumer...* > > *Nov 28, 2017 12:25:26 PM > com.ibm.hrl.proton.server.executorServices.SimpleThreadFactory$ProtonExceptionHandler > uncaughtException* > > *SEVERE: Uncaught exception in thread: Thread [2,5,main] ,exception: > com.ibm.hrl.proton.adapters.rest.client.RESTException: > com.ibm.hrl.proton.adapters.rest.client.RESTException: Could not perform > POST of event instance:* > > > * {"OccurrenceTime":"28\/11\/2017-12:25:26","result":"1450.0","EventSource":"","entityType":"KPI","Certainty":"0.0","EventId":"56250546-f321-4c4c-b4ab-bfc18d2697da","DetectionTime":"28\/11\/2017-12:25:26","Duration":"0.0","entityId":"KPI:PRUEBA","Cost":"0.0","Annotation":"","Name":"KPIWasteContainer"} * > > with request headers: > > Content-Type: application/json > > > > User-Agent: Jakarta Commons-HttpClient/3.0 > > > > Host: 130.206.117.164 > > > > Content-Length: 300 > > > > *to consumer http://130.206.117.164/v2/entities > < http://130.206.117.164/v2/entities >, responce result: 400* > > > > > > Here the Orion log > > *time=2017-11-28T12:22:33.711Z | lvl=INFO | > corr=cfc3807a-d436-11e7-9e79-fa163eab214f | > trans=1511363186-603-00000000206 | from=pending | srv=pending | > subsrv=pending | comp=Orion | op=logMsg.h [1808] :lmTransactionStart | > msg=Starting transaction from 192.168.240.127:60684/v2/entities > < http://192.168.240.127:60684/v2/entities >* > > *time=2017-11-28T12:22:33.711Z | lvl=WARN | > corr=cfc3807a-d436-11e7-9e79-fa163eab214f | > trans=1511363186-603-00000000206 | from=130.206.122.186 | srv=pending | > subsrv=<default> | comp=Orion | op=AlarmManager.cpp [405] :badInput | > msg=Raising alarm BadInput 192.168.240.127 < http://192.168.240.127 >: No > entity id specified* > > *time=2017-11-28T12:22:33.711Z | lvl=INFO | > corr=cfc3807a-d436-11e7-9e79-fa163eab214f | > trans=1511363186-603-00000000206 | from=130.206.122.186 | srv=pending | > subsrv=<default> | comp=Orion | op=logMsg.h [1892] :lmTransactionEnd | > msg=Transaction ended* > > > > > > It seems that PROTON does not create correctly the rest call to ORION. > > I have followed the documentation and in particular the Appendix A: > Integration with NGSI in the FIWARE project “Integration with Context > Broker JSON Format” and I do not know what I am doing wrong…. > > I have updated PROTON with the last versions of the WAR files. > > > > Find attached the screenshoot of my consumer config and the json file with > my project on PROTON. > > > > I hope you can help me . > > Thanks in advance. > > Best regards, > > Dario Pellegrino > > > > > > Dario Pellegrino > Direzione Ricerca e Innovazione - R&D Lab > dario.pellegrino@eng.it > > Engineering Ingegneria Informatica spa > Viale Regione Siciliana, 7275 - 90146 Palermo(Italy) > Phone: +39-091.7511864 <+39%20091%20751%201864> > Mobile: +39-392.4674892 <+39%20392%20467%204892> > > Twitter: @DPellegrino73 > > www.eng.it > > > > > > > > > >

Stefano De Panfilis made changes - 29/Nov/17 4:28 AM

Attachment

image002_01D3686C83022970.jpg [ 60067 ]

Veronika Vlnkova made changes - 30/Nov/17 6:53 AM

Assignee

Fabiana Fournier [ tali ]

FW External User made changes - 26/Dec/17 11:35 PM

Sender Email

dario.pellegrino@eng.it,stefano.depanfilis@fiware.org

dario.pellegrino@eng.it,stefano.depanfilis@fiware.org,jira-help-desk@jira.fiware.org

FW External User made changes - 26/Dec/17 11:35 PM

Attachment

[FIWARE-JIRA] (HELP-12992) [Fiware-general-help] [SPAM] [FIWARE-JIRA] (HELP-13082) [SPAM] Website Job Application [ 61165 ]

FW External User made changes - 27/Dec/17 5:33 AM

Attachment

[FIWARE-JIRA] (HELP-12992) [Fiware-tech-help] Problem sending a CEP-Proton event to FIWARE ORION Context BRoker [ 62806 ]

Fernando Lopez made changes - 31/Dec/17 1:16 PM

Attachment

[FIWARE-JIRA] (~~HELP-12992~~) [Fiware-general-help] [SPAM] [FIWARE-JIRA] (HELP-13082) [SPAM] Website Job Application [ 61165 ]

Fernando Lopez made changes - 31/Dec/17 1:16 PM

Comment

[ Comment by jira-help-desk@jira.fiware.org :

Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.

Content preview: [ https://jira.fiware.org/browse/HELP-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
   ] FW External User updated ~~HELP-12992~~: > [Fiware-general-help] [SPAM] [FIWARE-JIRA]
   (HELP-13082) [SPAM] Website Job Application > > > Key: ~~HELP-12992~~ > URL:
  https://jira.fiware.org/browse/HELP-12992 > Project: Help-Desk > Issue Type:
   extRequest > Reporter: FW External User > Attachments: [FIWARE-JIRA] (HELP-13082)
   [Fiware-general-help] [SPAM] Website Job Application > > > Spam detection
   software, running on the system "fiware-forge-01", has > identified this
  incoming email as possible spam. The original message > has been attached
  to this so you can view it (if it isn't spam) or label > similar future email.
   If you have any questions, see > the administrator of that system for details.
   > Content preview: [ https://jira.fiware.org/browse/HELP-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
   > ] FW External User updated HELP-13082: Attachment: [FIWARE-JIRA] (HELP-13082)
   > [Fiware-general-help] [SPAM] Website Job Application [...] > Content analysis
   details: (6.1 points, 4.5 required) > pts rule name description > ---- >
  1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist > [URIs: latedeliver.com]
   > 2.5 URIBL_DBL_SPAM Contains a spam URL listed in the DBL blocklist > [URIs:
   latedeliver.com] > 0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1 > 3.8 HELO_LOCALHOST
   HELO_LOCALHOST > -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% >
  [score: 0.0000] > > You can get more information about our cookies and privacy
   policies on the following links: > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
   > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
   > Fiware-general-help mailing list > Fiware-general-help@lists.fiware.org
   > https://lists.fiware.org/listinfo/fiware-general-help > [Created via e-mail
   received [...]

Content analysis details: (6.9 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
                            [URIs: latedeliver.com]
2.5 URIBL_DBL_SPAM Contains a spam URL listed in the DBL blocklist
                            [URIs: latedeliver.com]
0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1
3.8 HELO_LOCALHOST HELO_LOCALHOST
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

]

Fernando Lopez made changes - 31/Dec/17 1:16 PM

Comment

Veronika Vlnkova made changes - 08/Jan/18 6:01 PM

Assignee

Fabiana Fournier [ tali ]

Jose Manuel Cantera [ jmcantera ]

Jose Manuel Cantera made changes - 08/Jan/18 6:05 PM

Status

Open [ 1 ]

In Progress [ 3 ]

Hide

Permalink

Jose Manuel Cantera added a comment - 08/Jan/18 6:06 PM

you are missing the entity id

op=AlarmManager.cpp[405]:badInput | msg=Raising alarm BadInput
192.168.240.127: No entity id specified

Show

Jose Manuel Cantera added a comment - 08/Jan/18 6:06 PM you are missing the entity id op=AlarmManager.cpp [405] :badInput | msg=Raising alarm BadInput 192.168.240.127: No entity id specified

Jose Manuel Cantera made changes - 10/Jan/18 9:27 AM

Status	In Progress [ 3 ]	Closed [ 6 ]
Resolution		Fixed [ 1 ]

Backlog Manager made changes - 11/Jan/18 2:10 AM

Summary

[Fiware-tech-help] Problem sending a CEP-Proton event to FIWARE ORION Context BRoker

FIWARE.Request.Tech.Problem sending a CEP-Proton event to FIWARE ORION Context BRoker.

Fernando Lopez made changes - 19/Jan/18 2:59 PM

HD-Enabler		Orion [ 10875 ]
HD-Chapter		Data [ 10838 ]

Fernando Lopez made changes - 27/May/21 10:57 AM

Fix Version/s

2021 [ 12600 ]

Transition

Time In Source Status

Execution Times

Last Executer

Last Execution Date

Open

In Progress

41d 4h 40m

Jose Manuel Cantera

08/Jan/18 6:05 PM

In Progress

Closed

1d 15h 22m

Jose Manuel Cantera

10/Jan/18 9:27 AM

People

Assignee:

Jose Manuel Cantera

Reporter:

FW External User

Votes:

0 Vote for this issue

Watchers:

5 Start watching this issue

Dates

Created:

28/Nov/17 1:24 PM

Updated:

27/May/21 10:57 AM

Resolved:

10/Jan/18 9:27 AM

Agile

View on Board