Mystery of jsonrpc call that never completes

Recently I came across an interesting problem (to say the least) where jsonrpc call would execute the error call back function, but did not provide the details.  Additionally (as the title suggests) Firebug showed that the call never completed. Firebug continues to show rotating ring next to this call. But server logs suggested that server not only received the call, but it also processed the request completely.

I googled for “jsonrpc never completes” (and other similar terms) But no one had faced the problem. Strange

Normally, when jsonrpc call executes error callback, there would be some error on the server (serving the rpc call) But in this case, the call went thru fine. No error on server.

So I started debugging. First place to look, check server logs. No error there. Added additional debug statements on server. Still no help.

Then I modified the client-side code. Checked if there were additional information in the response sent back. Nothing.

May be there was something wrong with this specific RPC. Just to isolate, I made another RPC, which was known to work at other places. I was so sure that problem would go away, that I was shocked that problem remained.

So clearly it wasn’t the RPC, but the way it was called. So I started looking at surrounding code. Wasn’t any different. So I went further up the stack. It turns out later in the chain – unconditional window.location.reload() was called. This was causing the browser to reload the page even before the jsonrpc would complete.

Looking back – it was obvious. So why did I write this post ? So that someone else who may come across such symptom in future, may have some tips to troubleshoot.

In case you are interested, this was part of this project

Related articles

• Debugging Javascript applications (markos.gaivo.net)
• Firebug Guide for Web Designers (sixrevisions.com)