Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4997

FIWARE.Request.Tech.Data.CEP.The key [Name] was not in the map, reason: The key [Name] was not in the map (#15)

    Details

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

      Description

      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.com 972-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]

      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

        Hide
        TALI Fabiana Fournier added a comment -

        Answered by e-mail, added in here as well

        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

        Show
        TALI Fabiana Fournier added a comment - Answered by e-mail, added in here as well 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

          People

          • Assignee:
            TALI Fabiana Fournier
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: