Joined: 21/11/2007 12:23:06
(from mail conversation)
Symptom: from client side there is a firing of requests to a client side program (interface management) using CLIENTHTTPSENDER component. After some successul requests subsequent requests are not processed.
Cause: the client side requests were not responded by the client side program, but left open (for kind of long polling reasons). Browsers have a limit of maximal requests they open for one origin ("server") - documentation on how many is not totally consisten. In the concrete case (Edge) we found the number of "6", in the concrete scenario we saw a blocking from "20" open connections on.
So: keep an eye on connection resources if going through long polling scenarios (here: client side)...!
Btw: the same applies when using the LONGPOLLING component in whcih a connection is setup from client side to the server side. If too many requests are kept open, the browser will not communicated to the server anymore... - What's the way out, if you really require such scenarios?
1. you may switch to WEBSOCKETPOLLING - here the number of connections is "quite unlimited"....
2. you may/should think about having one central POLLING connection, which is used for multiple cases (sharing of LONGPOLLINGs)