Thanks For Explanation Dario..

First, I need to confirm and explanation about view things, that maybe I didn't know..

Is it stream-sense mechanism automatically happen when something happen in network infrastructure, like you said in another thread like "intermediate node (an antivirus, for instance)" ?, How about other caused (client slow connection, tight and long queing message sending, allegro version 1 update item in one second,etc) ?

How Can I knowing sure in the logg, that some session is turn to stream-sense instead normal streaming mode ?

Is stream-sense start with
Code:
Starting new session: Sd83b6032c3f1ee5eT1454966 from 150.70.84.75:51248
28-Apr-10 16:14:54,988 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 5     |Polling (129) to session
And streaming mode start with
Code:
controlling session:
Code below is logged exactly after first client do subscribe :
Code:
.... Subscribe about 600 line item....
30-Apr-10 09:57:56,724 |WARN |rs.remote.data.RemoteDataProvider|#1 Notify Receiver         |Received Remote Server message: 
'0|S|stock_name|S|BOYPAS|S|last_price|S|410|S|time|S|09:58:47|S|pct_change|S|0|S|bid_quantity|S|939|S|bid|S|405|S|ask|S|410|S|ask_quantity|S|24|S|min|S|410|S|max|S|420|S|ref_price|S|415.16|S|open_price|S|410'
30-Apr-10 09:57:56,733 |WARN |rs.remote.data.RemoteDataProvider|#1 Notify Receiver         |Received Remote Server message: '0|S|stock_name|S|BOYULE|S|last_price|S|410|S|time|S|09:58:47|S|pct_change|S|0|S|bid_quantity|S|939|S|bid|S|405|S|ask|S|410|S|ask_quantity|S|24|S|min|S|410|S|max|S|420|S|ref_price|S|415.16|S|open_price|S|410'
30-Apr-10 09:57:56,754 |WARN |rs.remote.data.RemoteDataProvider|#1 Notify Receiver         |Received Remote Server message: '0|S|stock_name|S|BOZBRA|S|last_price|S|410|S|time|S|09:58:47|S|pct_change|S|0|S|bid_quantity|S|939|S|bid|S|405|S|ask|S|410|S|ask_quantity|S|24|S|min|S|410|S|max|S|420|S|ref_price|S|415.16|S|open_price|S|410'
30-Apr-10 09:58:15,945 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (88) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 09:58:46,095 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (301) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 09:59:16,143 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (520) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 09:59:46,240 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (697) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 09:59:50,334 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 7     |Serving request: /lightstreamer/STREAMING_IN_PROGRESS?LS_phase=8902&LS_domain=most.co.id&LS_client_version=4.3&LS_adapter=PROXY_HELLOWORLD_SOCKETS& from 216.104.15.130:24197
30-Apr-10 09:59:50,335 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 3     |Starting new session: S6eec6a4485d4188T5950335from 216.104.15.130:24197
30-Apr-10 10:00:16,344 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 6     |Polling (821) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:00:46,351 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (996) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:01:16,474 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (1228) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:01:46,509 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (1377) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:02:16,553 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 6     |Polling (1613) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:02:46,646 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (1847) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:03:16,762 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 4     |Polling (2022) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:03:46,960 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (2207) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:04:17,303 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 8     |Polling (2378) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:04:47,324 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (2539) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:05:18,525 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 8     |Polling (2734) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:05:48,754 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 8     |Polling (2937) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:06:18,761 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (3148) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:06:48,774 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 2     |Polling (3364) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:07:18,924 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 1     |Polling (3543) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:07:48,969 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 9     |Polling (3757) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:08:19,079 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 4     |Polling (3971) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:08:50,579 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 5     |Polling (4116) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:09:20,793 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 7     |Polling (4302) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:09:50,835 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 2     |Polling (4461) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:10:21,100 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 8     |Polling (4668) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:10:53,349 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 2     |Polling (4877) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:11:23,499 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 8     |Polling (5073) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:11:54,518 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 2     |Polling (5278) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
30-Apr-10 10:12:24,549 |INFO |LightstreamerLogger.requests     |SERVER POOLED THREAD 2     |Polling (5511) to session: S600f412f44bfebd0T5745861 from 10.72.10.18:56411
As you can see, there is Serving Request to 216.104.15.130, before "Starting new session" shown up.. We don't recognize this IP, but if we trace, this IP was located in Japan, and has something todo with "trend-micro", our network using "trend micro", but our network support in our office said that, that is not a problem..

I don't know what this IP doing, maybe it request with multiple instance..

How about your analysis about this ?

At the last reply, like you said, there is 4 session active, my computer in local network, other computer connected through internet provider and this IP 216.104.15.134, 150.70.84.203 (I don't know this either), we are not publishing yet..

I don't expect this application use by one client and 1 session, on the last reply,I thought I connected to lightstreamer with 1 session (actually 4 session like you said). Can Lightstreamer do block certain IP ?

It didn't it happen when I closed any sessions on the client side, but long delay happen in the middle of Polling to Session (Looks like random). The unknown IP that I mention keep try request to server (on the logs).

Our case problem is :
- We need lightstreamer keep in streaming mode and there is no delay
- Client didn't stop suddenly, because open two page browser contain same receiving data from lighstreamer. (Make client open just 1 instance even open two browser, or make 2 instance with no problem). CMIIW If one client open two web page, in one browser, is it automatically create 2 instance... how to make sure client just using 1 instance, we cannot preventing client open 2 browser with one page, isn't



Thank You,

Gani K