https://www.ejabberd.im/node/4457 en https://www.ejabberd.im/node/4457#comment-57340 <p>After yet more debugging, it appears that the system is only able to handle a single HTTP request per socket. Basically the pipelining option doesn't actually pipeline, it just processes the requests serially. It's not clear if this is a feature/issue with the gloox SDK or ejabberd.</p> Mon, 16 May 2011 14:17:31 +0000 ryanhope comment 57340 at https://www.ejabberd.im https://www.ejabberd.im/node/4457#comment-57072 <p>We've done some more debugging, and it appears that the response from the client, which is based on the gloox XMPP SDK, is sending a response on one of the HTTP channels, but for some reason the ejabberd server is not receiving the response until a 30 second timeout has expired. When we get in this situation, we see 2 parallel requests open, and can watch the http request leave the client - but nothing shows up in the ejabberd log for around 30 seconds. It's as if the request is somehow cached in the ejabberd's HTTP processing (socket?) and the state machine doesn't get around to looking at it until max requests goes below 2. Is there a way to confirm that's the case, and figure out what the 2 parallel requests are when we get into this situation?</p> Wed, 16 Feb 2011 22:36:20 +0000 ryanhope comment 57072 at https://www.ejabberd.im