[Backlogmanager] [FIWARE-JIRA] (HELP-9546) [fiware-stackoverflow] How to make rush work with my orionInstance

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Fri Jun 9 09:51:03 CEST 2017


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

Fernando Lopez deleted HELP-9546:
---------------------------------


> [fiware-stackoverflow] How to make rush work with my orionInstance
> ------------------------------------------------------------------
>
>                 Key: HELP-9546
>                 URL: https://jira.fiware.org/browse/HELP-9546
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 02-12-2014 at 18:12
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/27255831/how-to-make-rush-work-with-my-orioninstance
> +Question:+
> How to make rush work with my orionInstance
> +Description:+
> Following my previous question How to show an entity from OrionContextBroker in the MapViewer widget I configured my context broker instance using Rush and I am using https://ngsiproxy.lab.fi-ware.org as NGSI proxy.    
> I start the orionContextBroker instance like this: contextBroker -rush localhost:5001 and everything seems to be working correctly (I can insert/query data etc), but when the MapViewerWidget gets loaded I get this message from the OrionInstance log:
> INFO at 17:32:53  clientSocketHttp.cpp[152]: Starting transaction to ngsiproxy.lab.fi-ware.org:443/callbacks/19:32:59-1:19:33:01-1
> WARNING at 17:32:53  clientSocketHttp.cpp[342]: Notification failure for localhost:5001 (curl_easy_perform failed: Couldn't connect to server)
> INFO at 17:32:53  clientSocketHttp.cpp[359]: Transaction ended
> 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