ejabberd - Comments for "XMLRPC return very slowly sometimes"

Thanks very much for your

elvistest4 — Sat, 08 Oct 2011 07:54:28 +0000

Thanks very much for your suggestion, Badlop.

Now the root cause had been found, it turned out to be the NetScaler Load balancer issue.

Everything goes well after we upgrading the firmware of the netscaler.

elvistest4 wrote: The

mfoss — Sat, 01 Oct 2011 19:24:14 +0000

elvistest4 wrote:

The situation is the query didn't fail, but have very long latency with the response.

And, Is it possible that this is a defect of the ejabberd cluster implementation?

You can try to run the query using ejabberdctl in the node where it usually takes too long. Let's see if the problem is in running that command (and then maybe the problem is in clustering), or if the problem is only when using XML-RPC (and then the problem is related to XML-RPC).

Hi badlop, Thanks for the

elvistest4 — Thu, 29 Sep 2011 02:16:52 +0000

Hi badlop, Thanks for the reply.

1, I am sure both of two nodes of the ejabberd have xmlrpc enabled, since I can call the xmlrpc via the direct URL againt both of these two nodes.

2, what kind of unexpected change could be in the query? The situation is the query didn't fail, but have very long latency with the response.

And, Is it possible that this is a defect of the ejabberd cluster implementation? Thanks, please help, this is urgent to me.

elvistest4 wrote: Important

mfoss — Wed, 28 Sep 2011 17:21:18 +0000

elvistest4 wrote:

Important Note:

This is a cluster environment with 2 nodes. with the same environment, this only happened we I used the load balancer Url to call XMLRpc.

If I used the node URL directly to call XmlRpc, this error didn't happen.

Any idea? Thanks very much.

Maybe you only have xmlrpc enabled in one of the two ejabberd nodes, and the call fails when you query the other.

Maybe the load balancer URL introduces some unexpected change in the query.

Important Note: This is a

elvistest4 — Wed, 28 Sep 2011 10:00:06 +0000

Important Note:

This is a cluster environment with 2 nodes. with the same environment, this only happened we I used the load balancer Url to call XMLRpc.

If I used the node URL directly to call XmlRpc, this error didn't happen.

Any idea? Thanks very much.