Lost streaming after migrating to Linux and had domain changed

**gerald.logor** · May 15th, 2008, 02:32 AM

Thanks for the prompt response, Mone.

I'm using Mozilla Firefox 5 and Internet Explorer 6. Another observation that I found is that, on Firefox, the main master-page is still able to receive the data stream (but not the children pages as I've mentioned previously). However, on Explorer, it does not receive any streaming at all on the master push-page.

...Please can you post the code as it arrives on the client and not as it is in the jsp?

I'm not quite understanding your request. What "client" code are you referring to? because the .jsp taglib just represents the data it contains, and it might be critical info that is limited to me to share.

-Gerald

**DarioCrivelli** · May 15th, 2008, 08:25 AM

Mone is not at office today, but I can focus on a couple of aspects.

We need the final HTML code mainly to check the consistency of domain, host and port settings. We would just need the same small snippets as above, but grabbed from the browser page. Are domain and host settings among the private information?

Have you assessed the use of "self.parent" in the "seekEngine" call? It seems to us that, in a popup window, "self.opener" should be used instead.

**gerald.logor** · May 15th, 2008, 09:12 AM

Dario,
thanks for the notification.
Attached is the requested snippet.
And regarding the "self.parent", as Mone has said that "thanks to the engine name", the reference should be no problem. But we'll take a look at your suggestion in using "self.opener".

Code:

// Main Page master push-page & master engine

<html>
...
...
...
<script language="JavaScript">
...
...
...
var lsPage = new PushPage();
lsPage.context.setDebugAlertsOnClientError(false);
lsPage.context.setDomain("ciptaonline");
lsPage.onEngineCreation = startEngine;
lsPage.bind();
lsPage.createEngine("RTEngine", "LS/","SHARE_SESSION");
function startEngine(eng) {
	eng.policy.setMaxBandwidth(30);
	eng.policy.setIdleTimeout(30000);
	eng.policy.setPollingInterval(1000);
	eng.connection.setLSHost("cipta-linux2.ciptaonline");
	eng.connection.setLSPort(8080);
	eng.connection.setAdapterName("RT2");
	eng.changeStatus("STREAMING");
}
...
...
...
</script>
...
...
...
</html>



//==========================================================

// Derivative (pop-up) window 

<html>
...
...
...

<script language="JavaScript">
...
...
...
var lsPage = new PushPage();
var debugAlerts = true;
var remoteAlerts = false;
var pushHost = null;
var txtDomain="ciptaonline";
if (location.href.indexOf(txtDomain) > -1) {
	lsPage.context.setDomain(txtDomain);
	debugAlerts = false;
	remoteAlerts = true;
} else {
	lsPage.context.setDomain(txtDomain);
}
lsPage.context.setDebugAlertsOnClientError(debugAlerts);
lsPage.context.setRemoteAlertsOnClientError(remoteAlerts);
lsPage.bind();
lsPage.onClientError = function(mex) {  
     alert("Page SalesPortfolio\n"+mex);  
};  	
lsPage.seekEngine("RTEngine",self.parent);
...
...
...	
</script>
...
...
...
</html>

Thanks again.

**DarioCrivelli** · May 15th, 2008, 02:01 PM

May you please confirm that you use those unusual hostnames (I mean: "cipta-linux2.ciptaonline", rather than something like "cipta-linux2.ciptaonline.com")?
Setting the domain as just "ciptaonline" is not allowed by the browsers; this should cause a javascript error message; can you see an "Invalid argument" or similar message in your console?
This would certainly prevent the pages from working.

If this is the case, the "self.parent" setting is not involved in the problem; however, we still suggest you to check if "this.opener" would be more suitable.

**gerald.logor** · May 16th, 2008, 02:29 AM

Dario,
May you please confirm that you use those unusual hostnames (I mean: "cipta-linux2.ciptaonline", rather than something like "cipta-linux2.ciptaonline.com")?

In our current phase, Yes. Our current development domain is (only) "ciptaonline", and consequently the host address is "cipta-linux2.ciptaonline". Nevertheless, if this is what causes the problem, then why does it work for the master-push-page, and not for its derivatives' windows?

About the "self.parent" vs. "self.opener", we'll try to implement and test your suggestion.
Thanks again.

**gerald.logor** · May 16th, 2008, 05:25 AM

All,
thanks for the helps. We managed to solve the problem by renaming our domain and adding the ".com" (which clearly signifies a valid domain. Doh!)

-Gerald