getting "Application error. Destination unavailable" error

[johnreitano]

I have a parent window that dynamically adds an iframe to its body. I'm (intermittently) getting a "Application error. Destination unavailable" when calling a method in the parent window from the iframe.

Here is the code in the parent window:

    pmrpc.register( {
      publicProcedureName: "getProjectInfo",
      procedure: function() {
        console.log( 'received Rpc call getProjectInfo' );
        return "here's the info";
      }
    });

and here is the code in the iframe:

pmrpc.call({
  destination: parent,
  publicProcedureName : "getProjectInfo",
  retries: 40,
  timeout: 40000,
  onSuccess : function(returnObj) { 
    var projectInfo = returnObj.returnValue; 
    console.log("success returned from pmrpc.getProjectInfo with value " + JSON.stringify( projectInfo ) ); 
  },
  onError : function(statusObj) {
    console.log("error received after calling pmrpc.getProjectInfo: " + statusObj.message );
  }
});

As you can see, I get this problem even with very high timeout and retries. I noticed in one of your closed issues that someone had tried changing -1 to -2 in this part of the pmrpc code:

} else if (callObj.retries <= -2) {
  processJSONRpcResponse(...

And that does indeed "fix" the problem, but I'm wondering if there is a better fix, ie, one that would not turn off timeouts.

Thanks!
John

[izuzak]

Hi John, thanks for reporting this. I'll have a better look tomorrow, but in the meantime - can you have a look at these two HTML files which I put together to try to reproduce the issue: https://dl.dropbox.com/u/1657316/parent.html and https://dl.dropbox.com/u/1657316/child.html ? Anyway, this example works for me without errors -- an iframe child is added after 5 seconds in the parent, the code in the iframe calls a procedure in the parent and gets a non-error result. Let me know if I missed anything important, it will help me reproduce the issue and hopefully fix it. Also, can you try wrapping your pmrpc.call invocation in the child within a setTimeout(..., 0) and see if that fixes the issue? Also, is your code live on the Web somewhere, perhaps?

Anyway, I'd love to get to the bottom of this and fix the issue once and for all. It seems that there is something strange happening in some specific cases.

[izuzak]

@johnreitano -- not sure if this still interests you, but I hope I fixed the issue with commit eca09ff (with the help of @jbadeau). cheers!

[johnreitano]

Yes, I am still interested. Thank you so much for putting in the fix. I will check it out and see if it solves our problem.

Thanks,
John