Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Data
-
HD-Enabler:CEP
Description
Dear Juan,
I discussed it with our dev lead and showed her where this exception is
thrown. She said that it seems to be related to internal socket
communication problem that might be related to inconsistency due to
previous run incorrect termination. She said that it doesn't seem to be
related to the application definition or to the event data. Her suggestion
is to stop tomcat, make sure it is terminated, and restart it.
Hope it will solve your problem
Best regards,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com 972-4-8296320
From: Tali Yatzkar-Haham/Haifa/IBM
To: Juan Hurtado <juan.hurtadotomero@gmail.com>
Date: 29/10/2015 01:29 PM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Thank you for this check. Now we have a way to test it in our env.
I still didn't get answer from our dev lead that is on a business trip.
Hope to get back to you soon after she is back.
Best regards,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com 972-4-8296320
From: Juan Hurtado <juan.hurtadotomero@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 29/10/2015 12:18 PM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Hello Tali,
I have attached the POST sent directly to CEP. The result is the same.
Could you please check if there is anything wrong?
Thanks beforehand
2015-10-28 11:34 GMT+01:00 Tali Yatzkar-Haham <TALI@il.ibm.com>:
Thank you for the clarification.
Can you please try my suggestion? to send the event POST directly to the
CEP as if Orion sent it (with the same data and with the application/xml
header)?
Something like the POST below, but with the right CEP url, and the right
data?
Maybe this will give us a clue what is the problem
POST http://cep.lab.fi-ware.eu:8089/ProtonOnWebServer/rest/events
Content-Type: application/xml
Data:
<notifyContextRequest> ....
....
....
</notifyContextRequest>
Thanks
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com 972-4-8296320
From: Juan Hurtado <juan.hurtadotomero@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 28/10/2015 12:27 PM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Yes, you are right, sorry. Please find below the POST sent to Orion to get
Proton subscribed
curl 192.168.90.4:1026/v1/subscribeContext?notifyFormat=xml-s -S --header
'Content-Type: application/json' --header 'Accept: application/json'
-header 'Fiware-Service: ct_stc' -d @ | python -mjson.tool)
notifyFormat is set to XML and I've checked that Orion is sending XML.
Thanks
2015-10-28 11:19 GMT+01:00 Tali Yatzkar-Haham <TALI@il.ibm.com>:
Thank you for the clarification.
In the STC.json I see that the CEP will send messages to Orion in the xml
format. I understand that this direction works fine. Your issue is with
the other direction, having the CEP process events that are sent from
Orion. This is not part of the CEP definition file (STC.json).
Since you have the event data, could you please try to send it directly to
the CEP (with the application/xml header) using curl or some browser
extension (I'm using Postman extension for Chrome)?
Maybe this will give us some hint on the problem.
Thank you,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com972-4-8296320
From: Juan Hurtado <juan.hurtadotomero@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 28/10/2015 12:05 PM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Thanks for you message. I was having a look at the headers but this is
sent by Orion and I do not think this can be modified or changed.
Aboout the info, it was part of the log I made, sorry for not removing it.
And yes, Content-Type is application/xml as you can see in
STC.json,
Thank you for your help
2015-10-28 10:42 GMT+01:00 Tali Yatzkar-Haham <TALI@il.ibm.com>:
Thank you.
Because the Java exception is invalid stream header: 504F5354, I'm wander
if you know what were the header parameters. Can you see them?
Another question - do you know why the info below says "Este es el Json"?
I want to make sure the data is sent with Content-Type: application/xml
Thanks,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com972-4-8296320
From: Juan Hurtado <juan.hurtadotomero@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 27/10/2015 06:00 PM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Please find below
[Wed, 21 Oct 2015 16:38:35 +0200] INFO 206:Este es el Json:
<notifyContextRequest>
<subscriptionId>5627a36be4ea5f2df9a9eebd</subscriptionId>
<originator>localhost</originator>
<contextResponseList>
<contextElementResponse>
<contextElement>
<entityId type="STCSensor" isPattern="false">
<id>705222424</id>
</entityId>
<contextAttributeList>
<contextAttribute>
<name>Altitude</name>
<type>integer</type>
<contextValue>720</contextValue>
</contextAttribute>
<contextAttribute>
<name>AltitudeDelta1</name>
<type>integer</type>
<contextValue>720</contextValue>
</contextAttribute>
<contextAttribute>
<name>AltitudeDelta2</name>
<type>integer</type>
<contextValue>720</contextValue>
<contextAttribute>
<name>BatteryLevel</name>
<type>integer</type>
<contextValue>2</contextValue>
</contextAttribute>
<contextAttribute>
<name>CO</name>
<type>integer</type>
<contextValue>720</contextValue>
</contextAttribute>
<contextAttribute>
<name>COCal</name>
<type>float</type>
<contextValue>720</contextValue>
</contextAttribute>
<contextAttribute>
<name>CurrentRSSI</name>
And so on. Please let me know if you need the whole file.
Thanks
2015-10-27 13:52 GMT+01:00 Tali Yatzkar-Haham <TALI@il.ibm.com>:
Hi Juan,
I sent it to our development lead to see if she is familiar with this
error.
Meanwhile, I looked in the subscription (at stackoverflow) - where in that
subscription you specify that Proton expects the xml format?
Thanks,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com972-4-8296320
From: Juan Hurtado <juan.hurtadotomero@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 27/10/2015 11:16 AM
Subject: Re: [Proton] The key [Name] was not in the map, reason:
The key [Name] was not in the map (#15)
Dear Tali,
Please find enclosed the logs.
The action I wanted to do is the following:
- I have deployed Orion as a Docker instance in my localhost (Ubuntu
14.04) - I have deployed Proton on Tomcat7 (not using Docker).
- I have created a project (STC, also enclosed json file). This project
consists of sending an alarm (STCAlarm event) to Orion if no STCevent has
been received in the last 10 minutes) - I have modified Proton.properties to point STC.json
- I have restarted Proton and I see Proton sends the STCAlarm to Orion if
no events received. - In parallel, Orion is trying to send Proton events, but Proton is
rejecting those events due to: " the the input stream is down due
to:invalid stream header: 504F5354" - In Stackoverflow you can find the xml Orion is sending to Proton.
Please let me know if you need anything else.
Thanks beforehand[attachment "STC.json" deleted by Tali
Yatzkar-Haham/Haifa/IBM] [attachment "catalina.out" deleted by Tali
Yatzkar-Haham/Haifa/IBM]
[attachment "notifyProton.sh" deleted by Tali Yatzkar-Haham/Haifa/IBM]
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
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: Tali Yatzkar-Haham <TALI@il.ibm.com>]
Activity
- All
- Comments
- History
- Activity
- Transitions