Genesys Engage on-premises

 View Only

Discussion Thread View
  • 1.  Chat Server disconnections

    Posted 10-30-2018 00:13
    Hi Team,

    I am facing an issue in production where Chat is getting disconnected frequently.
    Chat comes through GMS and then to Chat server.

    Whenever disconnections happens there is an error in Chat server logs .

    requestResult 'ERROR'
    errorID         '8196'
    error           'No such user exists'


    can anyone please tell me what is the meaning of this error ? i cannot find any reference in any of the docs for this error?

    I need to figure out if chat server is causing this disconnect or its the client side sending disconnections.

    Thanks
    #DigitalChannels

    ------------------------------
    [Ankush] [Khare]
    ------------------------------


  • 2.  RE: Chat Server disconnections

    Posted 10-31-2018 06:04
    Could you please describe your GMS and Chat Server architecture? Also, would be great to see logs of GMS and Chat Server covering the issue. There might be a problem with load-balancing on GMS cluster.

    ------------------------------
    Jakub Němec
    Dimension Data Czech Republic s.r.o.
    ------------------------------



  • 3.  RE: Chat Server disconnections

    Posted 11-01-2018 02:28
    Hi Ankush,

    The information which you have shared is not sufficient for us to troubleshoot the issue, please answer my quick question which are listed below:

    1. Is your GMS is connected with chat server proper. (you can see on GMS startup logs)?

    2. Is your chat server generating session?

    3. Are you using any GMS cluster?

    4. Is the interaction getting created on UCS interaction table?

    5. Is the interaction reaching to interaction server for processing?


    Awaiting for your value reply.


    ------------------------------
    Sudherson Nadar
    Moksa Technologies Pvt. Ltd.
    ------------------------------



  • 4.  RE: Chat Server disconnections

    Posted 11-01-2018 02:34
    Hello Guys,

    The chat disconnection is not happening for all chats. It's very random.

    1. Is your GMS is connected with chat server proper. (you can see on GMS startup logs)?  --- > Yes properly as chats works fine. it's random chat disconnections.

    2. Is your chat server generating session?Yes properly as chats works fine. it's random chat disconnections.

    3. Are you using any GMS cluster? Yes GMS Cluster.

    4. Is the interaction getting created on UCS interaction table? Yes

    5. Is the interaction reaching to interaction server for processing? Yes


    I have opened a support ticket for same. 
    I will let you know guys what was the root cause :)

    ------------------------------
    [Ankush] [Khare]
    ------------------------------



  • 5.  RE: Chat Server disconnections

    Posted 11-02-2018 05:12

    Are you sure it's not the customer disconnecting? What value is the Chat Server option flex-disconnect-timeout? This may need to be increased.

     

    What do the Chat Server logs say?

     

    Look for the reasons codes:

    reason code = '0' left

    reason code = '1' left with request to close if no agents

    reason code = '2' left with request to close forcedly

    reason code = '3' left due to disconnect

    reason code = '4' removed by other party

    reason code = '5' removed by the server

    reason code = '6' removed due to bad secure key

     

    if the customer (the CLIENT) is disconnecting you will see something like:

    2018-07-05T12:01:26.352 Int 59256 data: user uid=00B15B3DFA3D0001 (type=CLIENT) removed from session with sid=00B15B3DFA3D0002 and intx=00026aDKPHG00046 with reason=3 (left due to disconnect)



    ------------------------------
    Ian Middleton
    British Telecommunications PLC
    ------------------------------



  • 6.  RE: Chat Server disconnections

    Posted 11-02-2018 05:16
    Hi,

    Yes Customer says they are not disconnecting, Chat session just terminates in between. Flex timeout is set to 10 minutes as of now.

    This is the reason code after disconnection:

    reason code = '2' left with request to close forcedly



    ------------------------------
    [Ankush] [Khare]
    ------------------------------



  • 7.  RE: Chat Server disconnections

    Posted 11-07-2018 14:48
    ​We are having the same error message : (type=AGENT, style=HUMAN) removed with reason=2 (left with request to close forcedly)
    or with reason=3 (left due to disconnect).

    I also noticed the following error : (46 msec elapsed) session restoration failed during 'transcript reconstruction' for intx=0000PaDUD41H0YXE by uid=01415BDC44FB0AF7 due to Bad secure key

    ------------------------------
    Benoit Dupuis
    Hydro Quebec
    ------------------------------



  • 8.  RE: Chat Server disconnections

    Posted 11-08-2018 03:41
    Can you reproduce the error with different browsers?

    ------------------------------
    Sascha Gagalon
    Dimension Data Germany AG & Co. KG
    ------------------------------



  • 9.  RE: Chat Server disconnections

    Posted 11-08-2018 03:54
    ​The reason code 2 for an agent is correct behaviour, it's an option in WDE.

    For every Chat connection, there will be TWO reasons written to the logs.  One is the Client and the other is the Agent.  Check the full string of the loge message:

    2018-07-05T12:01:26.352 Int 59256 data: user uid=00B15B3DFA3D0001 (type=CLIENT) removed from session with sid=00B15B3DFA3D0002 and intx=00026aDKPHG00046 with reason=3 (left due to disconnect)

    2018-07-05T12:01:26.388 Int 59256 data: user uid=00B15B3DFA450003 (type=AGENT) removed from session with sid=00B15B3DFA3D0002 and intx=00026aDKPHG00046 with reason=2 (left with request to close forcedly)

    in the above example the client (customer) ended due to disconnect, which then forced the removal of the Chat from the agent.



    ------------------------------
    Ian Middleton
    British Telecommunications PLC
    ------------------------------



  • 10.  RE: Chat Server disconnections

    Posted 11-08-2018 08:25
    ​That is what I though, but I have been informed that the Customer was typing when suddenly the session stopped... I guess it might be something with the widget or maybe some network glitch??

    I also noticed in the Chat Server logs, when this problem occurs, most of the time we have this error showing : session restoration failed during 'transcript reconstruction' for intx=0000PaDUD41H10QD by uid=01415BDC7EA90B8F due to Bad secure key. Is this "due to Bad secure key" indicate something we should look into?

    Thanks again!

    ------------------------------
    Benoit Dupuis
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources