AutoRelay with Crypt Failed Messages

Home Forums kbmMW AutoRelay with Crypt Failed Messages

Viewing 2 reply threads
  • Author
    Posts
    • #55274
      Babis Michael
      Participant

      Hello,

      I’m using Server’s AutoRelay to send messages between clients. Using a crypt component to encrypt the connection sometimes it will fail to “decrypt” the messages.

      Client OnMessage with Crypt Log:
      14/12/2020 17:48| Message: MSG.00C4E21786
      14/12/2020 17:48| Message: MSG.00C4E21786
      14/12/2020 17:48| TransportMessageProcessingFailed: MSG.00C4E21786
      14/12/2020 17:49| TransportMessageProcessingFailed: MSG.00C4E21786
      14/12/2020 17:49| TransportMessageProcessingFailed: MSG.00C4E21786
      14/12/2020 17:49| Message: MSG.00C4E21786
      14/12/2020 17:49| Message: MSG.00C4E21786
      14/12/2020 17:49| TransportMessageProcessingFailed: MSG.00C4E21786

      Client OnMessage Without Crypt Log:
      14/12/2020 17:56| Message: MSG.00C4E21786
      14/12/2020 17:56| Message: MSG.00C4E21786
      14/12/2020 17:56| Message: MSG.00C4E21786
      14/12/2020 17:56| Message: MSG.00C4E21786
      14/12/2020 17:56| Message: MSG.00C4E21786
      14/12/2020 17:57| Message: MSG.00C4E21786

      Thank you

    • #55285
      kimbomadsen
      Keymaster

      Hi,

      Is it the relayed message or the original message to be relayed that fails?

      Can you make a very small test application replicating the problem?

      • #55293
        Babis Michael
        Participant

        Hello,
        To be relayed fails. Debugging the code found that for unknown reason it fails to decrypt the relayed message.
        I’ll try to find some free time to make you an example.

        Thank you

    • #55467
      kimbomadsen
      Keymaster

      Hi,

      Did you come around to a sample showing the problem?

      Another option is to manually relay a copy of the message using the ForwardMessage method.

       

      best regards

      Kim/C4D

Viewing 2 reply threads
  • You must be logged in to reply to this topic.