EMA:Failed to perform transport secure channel connections to hosts. Error: Couldn't add the chan...

zhangqingfeng
zhangqingfeng Newcomer
in EMA

...nel to the token session as the token reissue interval(-2319 ms) is too small.

loggerMsg

ClientName: LoginCallbackClient

Severity: Error

Text: RDMLogin stream was closed with status message

username <not set>

usernameType <not set>

State: Closed/Suspect/Usage error - text: "Failed to perform transport secure channel connections to hosts. Error: Couldn't add the channel to the token session as the token reissue interval(-2319 ms) is too small."

loggerMsgEnd

three question:

one:Why does this happen?

two:How do I catch this exception error?

three:How to handle this error? (Code examples would be great)

Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @zhangqingfeng

    You need to contact the LPC support team via MyRefinitiv to verify the error.

    The error was sent in the login status message with the closed stream state so EMA will not recover the connection. 

    loggerMsg
    ClientName: LoginCallbackClient
    Severity: Error
    Text: RDMLogin stream was closed with status message
    username <not set>
    usernameType <not set>


    State: Closed/Suspect/Usage error - text: "Failed to perform transport secure channel connections to hosts. Error: Couldn't add the channel to the token session as the token reissue interval(-2319 ms) is too small."
    loggerMsgEnd

    However, the application can detect it by registering the login request to receive the login status messages in the callback, as shown in the example 333.

    Then, if the application received the login status message with the closed stream state, the application can create a new consumer to connect to LPC.


Answers

Categories