LS and adapter are running, but client never gets past CONNECTING

[DarioCrivelli]

Something might have been wrong in the previous Adapters configuration.
In such a case, the Server initialization could have not completed successfully, for instance, because of a block in the "init" method of an Adapter.
Hence, the Server behavior may depend entirely on the Adapter behavior.

The second issue can be related with the client configuration, as I warned in the previous post.
Your page sets a port through

lsEngine.connection.setLSPort("227");

From that, I assume that you have a Web Server (or something equivalent) running on the same machine as Lightstreamer Server and that you get the front-end pages from this Web Server.
May you please confirm the above assumption, first of all?

[thanie2001]

Yes, it's running on the same server. I figured out the firefox issue - it was an issue with making the domain and host match.

I'm trying to debug another problem now. I'm doing paging through AJAX and recreating a Table object with every paging call but I'm not getting subscriptions for anything but the first page.

This is my code that gets called every time:

// create an OverwriteTable; item and field names will be grabbed from
// the corresponding HTML divs
// auctionItems is the new set of items to be added to the list
var table = new OverwriteTable(null, null, "MERGE");
table.setRequestedMaxFrequency(1.0);
table.setPushedHtmlEnabled(true);

table.setDataAdapter("DEFAULT");
table.setSnapshotRequired(false);
pushPage.addTable(table, "main");


I noticed in the StockListDemo page the client script is passing a value to the group and schema paramters , where I'm passing null to those every time. Do I need to be passing values for those on each page change?

Thanks!

[DarioCrivelli]

The null arguments in place of group and schema arguments request Lightstreamer to find the available cells in the page DOM and extract the item and field names from them.
In order to better understand which names have been found, please show us a snippet of the Server log,
in which the first and the subsequent subscription requests related to the various calls to "addTable" can be identified.