PureEngage On-Premises

 View Only

Sign Up

  • 1.  Cometd Jetty servers throws 408 error

    Posted 12-01-2017 17:08
    We are using Cometd API's https://docs.genesys.com/Documentation/GMS/latest/API/ChatAPIv2CometD from our client application. We receive notifications from request chat API
    To start receiving notifications, you can either:
    Use the requestChat operation to request a new chat for your channel.

    But we see we are getting some 408's from the cometd server and due to which we are misssing many notifications from the server. Could you please tell us how to solve the issue?


  • 2.  RE: Cometd Jetty servers throws 408 error

    Posted 12-01-2017 17:36
    GMS version used is 8.5.111.08


  • 3.  RE: Cometd Jetty servers throws 408 error

    Posted 12-04-2017 09:01
    Did you configure _enable_notification_mode on chat service options level?


  • 4.  RE: Cometd Jetty servers throws 408 error

    Posted 12-04-2017 17:15
    Yes, the cometd is working fine 80 percent of the time and fails 20 percent of the time. we are thinking it might be realted to jetty timeouts. any clue there?
    The biggest issue is we are missing some notifications because of that.


  • 5.  RE: Cometd Jetty servers throws 408 error

    Posted 12-05-2017 13:38
    What say logs?Did you find out anything wrong there?


  • 6.  RE: Cometd Jetty servers throws 408 error

    Posted 12-05-2017 16:51
    the /meta/connect event fails when we see those 408's. we are not able to find anything useful from logs. Is it some issue with cometd? how to upgrade the verison of cometd to 3.1.2?