[Backlogmanager] [FIWARE-JIRA] (HELP-9429) [fiware-stackoverflow] Sending event to Orion from Cepheus

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Thu Jun 8 09:44:00 CEST 2017


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

Fernando Lopez updated HELP-9429:
---------------------------------
     HD-Chapter: Apps
    Description: 
Created question in FIWARE Q/A platform on 27-09-2016 at 19:09
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/39730875/sending-event-to-orion-from-cepheus


+Question:+
Sending event to Orion from Cepheus

+Description:+
I am using the latest version of orangeopensource/fiware-cepheus from GitHub.

The problem is that based on some existing examples my Cepheus-broker doesn't send any events to Orion which I explicitly declared on the "/tmp/cep-default-.json" file. It produces the following results on the log:

cepheus_1      | 2016-09-27 17:03:20.209  INFO 10 --- [nio-8080-exec-7] c.o.cepheus.cep.EsperEventProcessor      : EventIn: Event{type='Position', values={id=Room34, key=24}}
cepheus_1      | 2016-09-27 17:03:20.840  INFO 10 --- [Timer-default-0] c.orange.cepheus.cep.EventSinkListener   : EventOut: position / id:24 from insert into position select key as id from Position.win:time(10 minutes) group by key output last every 10 seconds


But the messages of success or error won't show. This could mean 2 things on EventSinkListener.java:


updateContext is null (line 76)
eventTypeOut.getBrokers() returns a null broker (line 79)


My cep-default-.json is as follows

{
  "host":"http://localhost:8080",
    "in":[
{
  "id":"position",
  "type":"Position",
  "attributes":[
    { "name":"key", "type":"string"}
  ]
}
    ],
    "out":[
      {
        "id":"position",
        "type":"Position",
        "attributes":[
          { "name":"key", "type":"string"}
        ],
        "brokers": [
          {
            "url":"http://172.17.0.3:1026",
            "serviceName": "myHome",
            "servicePath": "/enviroment"
          }
        ]
      }
    ],
    "statements":[
      "INSERT INTO position SELECT key as id FROM Position.win:time(10 min) GROUP BY key OUTPUT LAST EVERY 10 sec"
    ]
  }


Being confused about this I tried Example 4 changing the broker address (localhost:8082) to my Orion address (http://172.17.0.3:1026). But when running the script it prints the following:

UpdateContext failed for http://localhost:8082: java.net.ConnectException: Connection refused


I confirmed that http://172.17.0.3:1026 is used as the broker address on the config file, but it still uses localhost:8082 somehow.

Any ideas of what I'm doing wrong?

Thanks.


  was:

Created question in FIWARE Q/A platform on 27-09-2016 at 19:09
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/39730875/sending-event-to-orion-from-cepheus


+Question:+
Sending event to Orion from Cepheus

+Description:+
I am using the latest version of orangeopensource/fiware-cepheus from GitHub.

The problem is that based on some existing examples my Cepheus-broker doesn't send any events to Orion which I explicitly declared on the "/tmp/cep-default-.json" file. It produces the following results on the log:

cepheus_1      | 2016-09-27 17:03:20.209  INFO 10 --- [nio-8080-exec-7] c.o.cepheus.cep.EsperEventProcessor      : EventIn: Event{type='Position', values={id=Room34, key=24}}
cepheus_1      | 2016-09-27 17:03:20.840  INFO 10 --- [Timer-default-0] c.orange.cepheus.cep.EventSinkListener   : EventOut: position / id:24 from insert into position select key as id from Position.win:time(10 minutes) group by key output last every 10 seconds


But the messages of success or error won't show. This could mean 2 things on EventSinkListener.java:


updateContext is null (line 76)
eventTypeOut.getBrokers() returns a null broker (line 79)


My cep-default-.json is as follows

{
  "host":"http://localhost:8080",
    "in":[
{
  "id":"position",
  "type":"Position",
  "attributes":[
    { "name":"key", "type":"string"}
  ]
}
    ],
    "out":[
      {
        "id":"position",
        "type":"Position",
        "attributes":[
          { "name":"key", "type":"string"}
        ],
        "brokers": [
          {
            "url":"http://172.17.0.3:1026",
            "serviceName": "myHome",
            "servicePath": "/enviroment"
          }
        ]
      }
    ],
    "statements":[
      "INSERT INTO position SELECT key as id FROM Position.win:time(10 min) GROUP BY key OUTPUT LAST EVERY 10 sec"
    ]
  }


Being confused about this I tried Example 4 changing the broker address (localhost:8082) to my Orion address (http://172.17.0.3:1026). But when running the script it prints the following:

UpdateContext failed for http://localhost:8082: java.net.ConnectException: Connection refused


I confirmed that http://172.17.0.3:1026 is used as the broker address on the config file, but it still uses localhost:8082 somehow.

Any ideas of what I'm doing wrong?

Thanks.


     HD-Enabler: Wirecloud

> [fiware-stackoverflow] Sending event to Orion from Cepheus
> ----------------------------------------------------------
>
>                 Key: HELP-9429
>                 URL: https://jira.fiware.org/browse/HELP-9429
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Álvaro Arranz
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 27-09-2016 at 19:09
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/39730875/sending-event-to-orion-from-cepheus
> +Question:+
> Sending event to Orion from Cepheus
> +Description:+
> I am using the latest version of orangeopensource/fiware-cepheus from GitHub.
> The problem is that based on some existing examples my Cepheus-broker doesn't send any events to Orion which I explicitly declared on the "/tmp/cep-default-.json" file. It produces the following results on the log:
> cepheus_1      | 2016-09-27 17:03:20.209  INFO 10 --- [nio-8080-exec-7] c.o.cepheus.cep.EsperEventProcessor      : EventIn: Event{type='Position', values={id=Room34, key=24}}
> cepheus_1      | 2016-09-27 17:03:20.840  INFO 10 --- [Timer-default-0] c.orange.cepheus.cep.EventSinkListener   : EventOut: position / id:24 from insert into position select key as id from Position.win:time(10 minutes) group by key output last every 10 seconds
> But the messages of success or error won't show. This could mean 2 things on EventSinkListener.java:
> updateContext is null (line 76)
> eventTypeOut.getBrokers() returns a null broker (line 79)
> My cep-default-.json is as follows
> {
>   "host":"http://localhost:8080",
>     "in":[
> {
>   "id":"position",
>   "type":"Position",
>   "attributes":[
>     { "name":"key", "type":"string"}
>   ]
> }
>     ],
>     "out":[
>       {
>         "id":"position",
>         "type":"Position",
>         "attributes":[
>           { "name":"key", "type":"string"}
>         ],
>         "brokers": [
>           {
>             "url":"http://172.17.0.3:1026",
>             "serviceName": "myHome",
>             "servicePath": "/enviroment"
>           }
>         ]
>       }
>     ],
>     "statements":[
>       "INSERT INTO position SELECT key as id FROM Position.win:time(10 min) GROUP BY key OUTPUT LAST EVERY 10 sec"
>     ]
>   }
> Being confused about this I tried Example 4 changing the broker address (localhost:8082) to my Orion address (http://172.17.0.3:1026). But when running the script it prints the following:
> UpdateContext failed for http://localhost:8082: java.net.ConnectException: Connection refused
> I confirmed that http://172.17.0.3:1026 is used as the broker address on the config file, but it still uses localhost:8082 somehow.
> Any ideas of what I'm doing wrong?
> Thanks.



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


More information about the Backlogmanager mailing list

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