LS adapter gets stops automatically get function only after restart the LS

Hello,
I'm having an issue on newly installed LS server in cent os 7. In this I have created the remote adapter written using in java and it's working fine for my functionality, but some times getting stops and I need to restart the LS server and adapter. If I need to know the issue means what are all the logs need to be enable and what are all the setting need to be change in log xml.

01-Oct-20 01:15:38,311|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/bind_session.js --> LS_session=Scac7447bd89d6dbcM488T4411914&LS_phase= 2422&LS_cause=ws.error.failure.wsc.unknown&LS_keep alive_millis=5000&LS_content_length=4000000&LS_con tainer=lsc& on "Lightstreamer HTTP Server" from 157.46.93.34:52095
01-Oct-20 01:15:38,311|INFO |L.requests |SERVER POOLED THREAD 1 |Sync error: Can't find session: Scac7447bd89d6dbcM488T4411914 on "Lightstreamer HTTP Server" from 157.46.93.34:52095


01-Oct-20 01:30:01,963|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/control.js --> LS_op=destroy&LS_session=Scac7447bd89d6dbcM488T441 1914&LS_cause=new.timeout.5.2.error&LS_unique=5& on "Lightstreamer HTTP Server" from 157.46.93.232:52112


01-Oct-20 01:33:56,653|INFO |L.requests |SERVER POOLED THREAD 8 |Sync error: Can't find session: S2127168ce79f32c9M488T3346125 on "Lightstreamer HTTP Server" from 157.46.82.181:55838


01-Oct-20 01:33:56,653|INFO |L.requests |SERVER POOLED THREAD 8 |Sync error: Can't find session: S2127168ce79f32c9M488T3346125 on "Lightstreamer HTTP Server" from 157.46.82.181:55838


01-Oct-20 01:34:20,177|INFO |L.requests |SERVER POOLED THREAD 6 |Sync error: Can't find session: S367273aebb31d305M488T3355893 on "Lightstreamer HTTP Server" from 157.46.82.181:55840

The reported log lines tell of client problems that seem unrelated with the Adapter behavior.
What evidence do you have that the Adapter stops?
If your evidence is based on some client not receiving the expected updates, the issue may lie on other parts of the pipeline.

Anyway, if you want to trace the activity of your Remote Adapters, you should leverage the "LightstreamerProxyAdapters" logger.
The factory setting of this logger is INFO, which should already produce log in case of problems.
Do you confirm that you can't see any log from this logger?

You can set this logger at DEBUG level, to see the subscription activity, or even to TRACE level, to see all the update flow.
Then you can evaluate if something is not as expected.
Consider that if the activity is high, this log can be very verbose;
the best condition is if the activity is low, or if you can replicate the issue with a dedicated Server instance.

Please check if your Server is earlier than 6.0, because in that case the loggers were different.

Hello,
By adapter stopping the service to all, by that stock rates not updating to all. I can see my screen also this not getting update the rates. This totally getting issue on my remote adapter I feel.

I need to check my code also whether this causes any issue, could you please help me is the possible to store my java file errors on LS log file.

My code is like,
public class ExternalFeedSimulator {
private static Jedis jedis;
private static JedisPool jedisPool;

public ExternalFeedSimulator() {
JedisPoolConfig poolConfig = new JedisPoolConfig();
poolConfig.setMaxTotal(1000);
jedisPool = new JedisPool(poolConfig, RedisDBConfig.HOST, RedisDBConfig.PORT, RedisDBConfig.TIMEOUT);
}
public static String getJSON() {
try {
jedis = jedisPool.getResource();
ClientsRateRow[] craterows = gson.fromJson(jedis.get("WLallclientsrates"), ClientsRateRow[].class);
for (ClientsRateRow raterow : craterows) {
liveratesnew.put(raterow.client_com_id, raterow);
curclientrates.add(raterow);
}
} catch (IllegalStateException ex) {
ex.printStackTrace();
} catch (JedisConnectionException e) {
e.printStackTrace();
} catch (SecurityException e) {
e.printStackTrace();
} finally {
jedis.close();
}
return null;
}

To check if get any error this need to store into LS log file. Can you help how to store the errors into ls log file from my customer class.

Hello,
To avoid misunderstandings, please confirm if the Adapter under investigation is an in-process Adapter or a Remote Adapter.
If your intention is that the Adapter should produce its log in the same file used by the Server, this is possible (only in some conditions) for an in-process Adapter.
For a Remote Adapter, I don't think that logback offers this possibility. In that case, you can only have the Server log the communication between the Server and the Remote Adapter (i.e. subscriptions and update events) in the way already explained.

I have used only remote adapter to subscribe items. Now I need to store the remote adapter file if anything exception happened need to be store into server log.

Sorry, this is not supported by Lightstreamer directly.
Our policy is that the log file generated by the Server is only owned by the Server and should not be concurrently accessed by other processes, like Remote Adapters.
The Adapter log should be inspected separately (or it may be manually merged with the Server log, but only when the log file is no longer used by the Server).

Since the configuration of the log appenders is free and it is only subject to logback capabilities, you may configure the Server log appenders and the Remote Adapter log in such a way that they are merged in the same file.
But I am not familiar with these techniques.
On the other hand, if you really want to share the same log configuration and the same log interface (via slf4j) used by the Server, you can do that with a fake in-process Adapter; we can expand on this if needed. But you have to send the log from the Remote Adapter to the fake adapter yourself in some way.

Hello,
I don't need to save logs in same file. I need to save in any of the file to check the issue. Please help me to store my remote adapter log in any of the file. My adapter is written in java.

Sorry for the misunderstanding.
If you use Lightstreamer SDK for Java Remote Adapters, the SDK library produces some log and there are instructions on how to configure the verbosity and the log file.
You can find the relevant information in the javadocs for SDK version 1.3.1
https://lightstreamer.com/docs/ls-se...nce/index.html
(see setLoggerProvider)

I'm not sure that this is what you expected.
If you want a facility to write to a file the log produced by your code, this is not provided, but it is the other way round.
In fact, the library doesn't provide a log implementation, but requires that the hosting program provides such implementation for its own log.
In this way, the hosting program can implement a bridge to send the log produced by the library to this implementation.

We show the full process in the examples. See this one.
Look in particular for the custom OutPrintLog class and its uses. Unfortunately, the example is simple and just sends the log to the standard output. To send the log to an implementation like log4j, more custom code is needed.

Please be aware that this matter has undergone a few changes in the latest 1.4.0 version of the SDK, hence, when you upgrade the SDK, a small code change will be needed.

Hello,
Exception in thread "Timer-0" com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 12 at com.google.gson.internal.bind.ReflectiveTypeAdapte rFactory$Adapter.read(ReflectiveTypeAdapterFactory .java:176) at com.google.gson.internal.bind.TypeAdapterRuntimeTy peWrapper.read(Type AdapterRuntimeTypeWrapper.java:40) at com.google.gson.internal.bind.ArrayTypeAdapter.rea d(ArrayTypeAdapter.java:72)at com.google.gson.Gson.fromJson(Gson.java:795)
at com.google.gson.Gson.fromJson(Gson.java:761)
at com.google.gson.Gson.fromJson(Gson.java:710)
at com.google.gson.Gson.fromJson(Gson.java:682)at stocklist.feed_simulator.ExternalFeedSimulator.get JSON(ExternalFeedSimulator.java:98)at stocklist.feed_simulator.ExternalFeedSimulator$1.r un(ExternalFeedSimulator.java:170) at java.base/java.util.TimerThread.mainLoop(Timer.java:556) at java.base/java.util.TimerThread.run(Timer.java:506)
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 12 at com.google.gson.stream.JsonReader.expect(JsonReade r.java:339) at com.google.gson.stream.JsonReader.beginObject(Json Reader.java:322)

I had checked on this and getting this error on screen. When I happened this exception getting stop the LS and adapter.

Hello,
So your suspect that the problem was in the Adapter is correct.
I confirm that the error does not occur in Lightstreamer library code, but in custom code.
Note that, even though you have kept the "ExternalFeedSimulator" class name that we use in our StockListDemo example, the getJSON method reported in the stack trace is not part of the original demo code, as well as the inclusion of the third-party com.google.gson library.
So we have no clue on this error.

Hello,
I have checked well, in my adapter some times exception only happening. I have handled the exception so there is no issue on that. And I have noticed in browser when rates gets stops. I can confirm LS server is working, adapter is not sending the updates. Please look on this below response of browser developer tool

var myEnv = lsc;
var phase = null;
function setPhase(ph) {
phase = ph;
}


var winPhase = {};
function setWin(tbl, ph) {
winPhase[tbl] = ph;
}


var clsd = false;
function c(cod, ph, tbl, its, flds, key, com) {
LS_window.LS_w(cod, ph, tbl, its, flds, key, com);
}


function error(cod, ph, tbl, msg) {
if (tbl != null) {
LS_window.LS_l(cod, ph, tbl, msg);
} else {
LS_window.LS_l(cod, phase, null, msg);
}
}


function start(sID, addr, kaMs, reqLim, srv, ip) {
LS_window.LS_e(1, phase, sID, addr, kaMs, reqLim, srv, ip);
}


function end(cause) {
LS_window.LS_e(4, phase, cause);
}


function loop(holdMs) {
LS_window.LS_e(2, phase, holdMs);
}


function retry() {
LS_window.LS_e(3, phase);
}


function s0() {}


function bw(maxBW) {
LS_window.LS_e(5, phase, maxBW);
}


function y(secs) {
LS_window.LS_s(phase, secs);
}


var unchangedSignal = {};
unchangedSignal.length = -1;
function convert(b, f) {
var a, c, d = f, e = [];
for(a = 0;a < b.length;a++) {
if(a < f) {
e[a] = b[a]
} else {
if(b[a].charAt) {
b[a] == '$' ? e[d] = '' : b[a] == '#' ? e[d] = null : (c = b[a].charAt(0), e[d] = c == '$' || c == '#' ? b[a].substring(1) : b[a]), d++
} else {
for(c = 0;c < b[a];c++) {
e[d] = unchangedSignal, d++
}
}
}
}
return e;
}
function d(tbl) {
try { LS_window.LS_u(winPhase[tbl], convert(arguments || d.arguments, 2)); } catch(exc) {}
}
function z(tbl) {
LS_window.LS_v(winPhase[tbl], convert(arguments || z.arguments, 2));
}
function n(tbl) {
LS_window.LS_n(winPhase[tbl], arguments || n.arguments);
}
function s(tbl) {
LS_window.LS_s(winPhase[tbl], arguments || s.arguments);
}
function r(tbl) {
LS_window.LS_o(winPhase[tbl], arguments || r.arguments);
}
function p() {
LS_window.LS_u(phase, arguments || p.arguments);
}
myEnv.setPhase = setPhase;
myEnv.setWin = setWin;
myEnv.c = c;
myEnv.error = error;
myEnv.end = end;
myEnv.start = start;
myEnv.loop = loop;
myEnv.retry = retry;
myEnv.s0 = s0;
myEnv.bw = bw;
myEnv.y = y;
myEnv.convert = convert;
myEnv.d = d;
myEnv.z = z;
myEnv.n = n;
myEnv.s = s;
myEnv.r = r;
myEnv.p = p;
myEnv.LS_window = LS_window;


// END OF HEADER


setPhase(7703);
start('Scd93873dea9808b9M6deT5148753', null, 5000, 50000);

Hi,

The javascript you showed is the normal reply to a create session request from the client, so it seems ok from that side, and gives us no clue on the actual cause of the issue.
You should make sure that your data adapter continues to work regularly and push updates into the Lightstreamer server.
If we're not sure of that it is difficult to further investigate the problem.
Maybe, when you catch the exception you just discard the update received from the back-end and don't send anything to the server anymore?

Regards,
Giuseppe

Hi,
I have monitor from morning, this was working fine but now suddenly stops the response and showing the below thing when it get stopped

setPhase(34054);start('S10ac9332c76d9c6eMb7dT53073 67', null, 19000, 50000);bw(0.0);setWin(1,1);setWin(2,1);d(2,7,7,'20 20-10-16 19:37:01');d(2,6,7,'2020-10-16 19:37:01');loop(0);end( );


After this above response not working, below things only happening




bind_session
LS_session=S10ac9332c76d9c6eMb7dT5307367&LS_phase= 34322&LS_cause=loop&LS_polling=true&LS_polling_mil lis=0&LS_idle_millis=19000&LS_container=lsc&


setPhase(34320);start('S10ac9332c76d9c6eMb7dT53073 67', null, 19000, 50000);bw(0.0);setWin(1,1);setWin(2,1);loop(0);end ( );


bind_session
LS_session=S10ac9332c76d9c6eMb7dT5307367&LS_phase= 34322&LS_cause=loop&LS_polling=true&LS_polling_mil lis=0&LS_idle_millis=19000&LS_container=lsc&


setPhase(34322);start('S10ac9332c76d9c6eMb7dT53073 67', null, 19000, 50000);bw(0.0);setWin(1,1);setWin(2,1);loop(0);end ( );


setPhase(34266);start('S10ac9332c76d9c6eMb7dT53073 67', null, 19000, 50000);bw(0.0);setWin(1,1);setWin(2,1);d(2,1,'5066 9','50687',6);loop(0);end( );


bind_session
LS_session=S10ac9332c76d9c6eMb7dT5307367&LS_phase= 34058&LS_cause=loop&LS_polling=true&LS_polling_mil lis=0&LS_idle_millis=19000&LS_container=lsc&


setPhase(34056);start('S10ac9332c76d9c6eMb7dT53073 67', null, 19000, 50000);bw(0.0);setWin(1,1);setWin(2,1);d(2,4,'24.4 ','24.44',6);loop(0);end( );


bind_session
LS_session=S10ac9332c76d9c6eMb7dT5307367&LS_phase= 34056&LS_cause=loop&LS_polling=true&LS_polling_mil lis=0&LS_idle_millis=19000&LS_container=lsc&

Hi,

This is strange, because the browser console reports a regular client polling session, and indeed you can see some data received, such as:

d(2,1,'5066 9','50687',6)

and

d(2,4,'24.4 ','24.44',6)

So actually the client keeps getting something from the Lightstreamer server.
Maybe that's not all you expect?
In this case it is necessary to double check the data in the server log to understand what was actually received by the data adapter and routed to the client.
In this case you need the DEBUG level for these loggers:

<logger name="LightstreamerLogger.subscriptions" level="DEBUG"/>

<logger name="LightstreamerLogger.subscriptions.upd" level="DEBUG"/>

Regards,
Giuseppe

Hello,
I'm getting this below log, whether is this any issue, Still I'm having problem some times getting stop on my LS adapter, client not getting any update.
02-Dec-20 05:45:52,193|INFO |L.requests |SERVER POOLED THREAD 5 |Serving request: /lightstreamer/create_session.js --> LS_op2=create&LS_phase=9901&LS_cause=new.timeout.5 .2.error&LS_polling=true&LS_polling_millis=0&LS_id le_millis=19000&LS_cid=pcYgxn8m8 feOojyA1T661k3g2.pz479h8o&LS_adapter_set=WLSTOCKLI ST_REMOTE&LS_old_session=S104d7bf3fcd22bfbM46fT453 4326&LS_container=lsc& on "Lightstreamer HTTP Server" from 106.201.184.128:37002

And also some of the times in my command subscription any one or 2 items are not getting update, this data not receiving to client. Is there any way to find out the reason?

Unfortunately, the client error you mentioned (LS_cause=new.timeout.5 .2.error) is not enough to figure out what is going on.
Indeed, the error means that the client was unable to create the session in the expected time and therefore tries again.
This scenario can be caused both by client-side problems such as poor network conditions, and server-side problems with severe delays on the server.
You should check the server log looking for messages like this "Current delay for tasks scheduled on thread pool SERVER is ... seconds".

About missing updates, still valid my previous reply, with a log configuration good for troubleshooting this kind of issue.

Regards,
Giuseppe

Hello,
I have already added the log configuration as your guidance. And I have downloaded log and searched like Current delay for tasks scheduled on thread pool SERVER but couldn't found anything like this. IS there any other log I need to enable in config.

So, with subscriptions loggers at DEBUG level you should be able to follow the entire flow relating to each Item, starting from the subscription request to the adapter and all the updates received by the server.

Message like this refer to the subscription request forwarded to the Data Adapter: "Subscribing to item <Item> on <AdapterSet.DataAdapter>"

Then you should looking for the replies of the adapter with messages like these:
"INCOMING SNAPSHOT for <Item> on <AdapterSet.DataAdapter> --> ... "
"INCOMING END OF SNAPSHOT NOTIFY for <Item> on <AdapterSet.DataAdapter>"
"INCOMING DATA for <Item> on <AdapterSet.DataAdapter> ... "

With that information you can be sure whether the updates are flowing regularly from the adapter to the server. If so, we'll need to focus on the client side.

Regards,
Giuseppe

Hello,
As per your instruction I have checked the log, now my system didn't work got stopped the pushing rates so suddenly checked log. Please check this log I have attached,
07-Dec-20 04:37:21,331|INFO |L.requests |PUMP POOLED THREAD 1 |Closed session S91a4ff89e6ee459fM656T2306451 with internal cause code: 38/2 (Connection interrupted by client).
07-Dec-20 04:37:23,715|INFO |streamerMonitorText|Timer-1 |Total threads = 92, Total heap = 62914560 (free = 43428880), Sessions = 3 (max = 13, refused = 0), New sessions = [+2, -2], Connections = 3 (max = 18), New connections = [+4, -4], In-pool threads = 32, Active threads = 0, Available threads = 32, Queued tasks = 0, Pool queue wait = 0, NIO write queue = 0, NIO write queue wait = 0, NIO write selectors = 4, NIO total selectors = 16, Subscribed items = 12 (for 36 subscriptions), Inbound throughput = 0 updates/s (pre-filtered = 0), Outbound throughput = 0 updates/s (0.73 kbit/s, max = 50.97), Lost updates = 0 (total = 0), Total bytes sent = 26829363, Client messages throughput = 0 msgs/s (0 kbit/s, max = 0), Total messages handled = 0, Extra sleep = 0, Notify delay = 0
07-Dec-20 04:37:25,159|INFO |L.requests |SERVER POOLED THREAD 8 |Serving request: /lightstreamer/create_session.js --> LS_op2=create&LS_phase=8801&LS_cause=new.api&LS_po lling=true&LS_polling_millis=0&LS_idle_millis=0&LS _cid=pcYgxn8m8 feOojyA1T661j3g2.pz479h7m&LS_adapter_set=WLSTOCKLI ST_REMOTE&LS_container=lsc& on "Lightstreamer HTTP Server" from 1.22.25.136:58569
07-Dec-20 04:37:25,160|INFO |L.requests |SERVER POOLED THREAD 8 |Starting new session: S3e7c8f24186ea3cdM656T3725160 (javascript_client 7.0.4 build 1721) on "Lightstreamer HTTP Server" from 1.22.25.136:58569
07-Dec-20 04:37:25,450|INFO |L.requests |SERVER POOLED THREAD 8 |Serving request: bind_session -> LS_session=S3e7c8f24186ea3cdM656T3725160&LS_phase= 8803&LS_cause=loop1&LS_container=lsc& on "Lightstreamer HTTP Server" from 1.22.25.136:58570
07-Dec-20 04:37:25,450|INFO |L.requests |SERVER POOLED THREAD 8 |Attaching session: S3e7c8f24186ea3cdM656T3725160 on "Lightstreamer HTTP Server" from 1.22.25.136:58570
07-Dec-20 04:37:25,455|INFO |L.requests |SERVER POOLED THREAD 8 |Serving request: control -> LS_mode=COMMAND&LS_id=kgnbull&LS_schema=key%20comm and%20desc%20bid%20ask%20high%20low%20order%20deli very&LS_data_adapter=WLQUOTE_ADAPTER&LS_snapshot=t rue&LS_table=1&LS_req_phase=2&LS_win_phase=1&LS_op =add&LS_session=S3e7c8f24186ea3cdM656T3725160& on "Lightstreamer HTTP Server" from 1.22.25.136:58570
07-Dec-20 04:37:25,455|INFO |L.requests |SERVER POOLED THREAD 8 |Controlling session: S3e7c8f24186ea3cdM656T3725160 on "Lightstreamer HTTP Server" from 1.22.25.136:58570
07-Dec-20 04:37:25,457|INFO |L.requests |SERVER POOLED THREAD 4 |Controlling session: S3e7c8f24186ea3cdM656T3725160 on "Lightstreamer HTTP Server" from 1.22.25.136:58570
07-Dec-20 04:37:46,992|INFO |L.requests |PUMP POOLED THREAD 4 |Closed session S3e7c8f24186ea3cdM656T3725160 with internal cause code: 38/2 (Connection interrupted by client).
07-Dec-20 04:37:51,030|INFO |L.requests |SERVER POOLED THREAD 1 |Starting new session: S2c036881423e770bM656T3751030 (javascript_client 7.0.4 build 1721) on "Lightstreamer HTTP Server" from 1.22.25.136:58610
07-Dec-20 04:37:51,992|DEBUG|L.subscriptions |SERVER POOLED THREAD 4 |Unsubscribing from item kgnbull on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:37:51,992|DEBUG|L.subscriptions |SERVER POOLED THREAD 1 |Unsubscribing from item Marketstatus-kgnbull on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:37:56,468|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/bind_session.js --> LS_session=S2c036881423e770bM656T3751030&LS_phase= 6104&LS_cause=ws.error.failure.wsc.unknown&LS_cont ent_length=4000000&LS_container=lsc& on "Lightstreamer HTTP Server" from 1.22.25.136:58610
07-Dec-20 04:37:56,468|INFO |L.requests |SERVER POOLED THREAD 1 |Attaching session: S2c036881423e770bM656T3751030 on "Lightstreamer HTTP Server" from 1.22.25.136:58610
07-Dec-20 04:37:56,796|INFO |L.requests |SERVER POOLED THREAD 4 |Serving request: /lightstreamer/control.js --> LS_mode=COMMAND&LS_id=kgnbull&LS_schema=key%20comm and%20desc%20bid%20ask%20high%20low%20order%20deli very&LS_data_adapter=WLQUOTE_ADAPTER&LS_snapshot=t rue&LS_table=1&LS_req_phase=2&LS_win_phase=1&LS_op =add&LS_unique=1&LS_session=S2c036881423e770bM656T 3751030& on "Lightstreamer HTTP Server" from 1.22.25.136:58615
07-Dec-20 04:37:56,797|INFO |L.requests |SERVER POOLED THREAD 4 |Controlling session: S2c036881423e770bM656T3751030 on "Lightstreamer HTTP Server" from 1.22.25.136:58615
07-Dec-20 04:37:56,798|DEBUG|L.subscriptions |SERVER POOLED THREAD 1 |Subscribing to item kgnbull on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:37:57,105|DEBUG|L.subscriptions |SERVER POOLED THREAD 4 |Subscribing to item Marketstatus-kgnbull on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:02,614|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/control.js --> LS_op=destroy&LS_session=S84a38836513b0243M656T275 6818&LS_cause=new.timeout.10.1&LS_unique=84& on "Lightstreamer HTTP Server" from 169.149.227.120:35294
07-Dec-20 04:38:02,618|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/create_session.js --> LS_op2=create&LS_phase=42506&LS_cause=create.timeo ut&LS_polling=true&LS_polling_millis=0&LS_idle_mil lis=0&LS_cid=pcYgxn8m8 feOojyA1T661k3g2.pz479h8o&LS_adapter_set=WLSTOCKLI ST_REMOTE&LS_container=lsc& on "Lightstreamer HTTP Server" from 169.149.203.46:35296
07-Dec-20 04:38:02,622|INFO |L.requests |SERVER POOLED THREAD 1 |Starting new session: S10bbf993d030c7feM656T3802622 (javascript_client 7.0.5 build 1722) on "Lightstreamer HTTP Server" from 169.149.203.46:35296
07-Dec-20 04:38:03,273|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/bind_session.js --> LS_session=S10bbf993d030c7feM656T3802622&LS_phase= 42508&LS_cause=loop1&LS_keepalive_millis=5000&LS_c ontent_length=4000000&LS_container=lsc& on "Lightstreamer HTTP Server" from 169.149.203.46:35296
07-Dec-20 04:38:03,273|INFO |L.requests |SERVER POOLED THREAD 1 |Attaching session: S10bbf993d030c7feM656T3802622 on "Lightstreamer HTTP Server" from 169.149.203.46:35296
07-Dec-20 04:38:03,279|INFO |L.requests |SERVER POOLED THREAD 1 |Serving request: /lightstreamer/control.js --> LS_mode=MERGE&LS_id=GOLDFEB%20MGOLD-C%20MGOLD-F%20SILVERMAR%20SILVER-F%20MSILVER-C%20MSILVER-F%20SPOT-GOLD%20SPOT-SILVER%20SPOT-INR&LS_schema=desc%20bid%20ask%20high%20low%20ltp& LS_data_adapter=WLQUOTE_ADAPTER&LS_snapshot=true&L S_table=56&LS_req_phase=57&LS_win_phase=57&LS_op=a dd&LS_unique=85&LS_session=S10bbf993d030c7feM656T3 802622& on "Lightstreamer HTTP Server" from 169.149.227.120:35294
07-Dec-20 04:38:03,279|INFO |L.requests |SERVER POOLED THREAD 1 |Controlling session: S10bbf993d030c7feM656T3802622 on "Lightstreamer HTTP Server" from 169.149.227.120:35294
07-Dec-20 04:38:03,280|DEBUG|L.subscriptions |SERVER POOLED THREAD 3 |Subscribing to item MGOLD-F on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:03,280|DEBUG|L.subscriptions |SERVER POOLED THREAD 8 |Subscribing to item MSILVER-C on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:03,280|DEBUG|L.subscriptions |SERVER POOLED THREAD 4 |Subscribing to item SILVER-F on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:03,659|INFO |L.requests |SERVER POOLED THREAD 4 |Serving request: /lightstreamer/control.js --> LS_mode=MERGE&LS_id=GOLDFEB%20MGOLD-C%20MGOLD-F%20SILVERMAR%20SILVER-F%20MSILVER-C%20MSILVER-F%20SPOT-GOLD%20SPOT-SILVER%20SPOT-INR&LS_schema=desc%20bid%20ask%20high%20low%20ltp& LS_data_adapter=WLQUOTE_ADAPTER&LS_snapshot=true&L S_table=57&LS_req_phase=58&LS_win_phase=57&LS_op=a dd&LS_unique=86&LS_session=S10bbf993d030c7feM656T3 802622& on "Lightstreamer HTTP Server" from 169.149.227.120:35294
07-Dec-20 04:38:03,660|INFO |L.requests |SERVER POOLED THREAD 4 |Controlling session: S10bbf993d030c7feM656T3802622 on "Lightstreamer HTTP Server" from 169.149.227.120:35294
07-Dec-20 04:38:11,243|INFO |L.requests |PUMP POOLED THREAD 4 |Closed session S10bbf993d030c7feM656T3802622 with internal cause code: 38/5 (Connection interrupted by client).
07-Dec-20 04:38:16,243|DEBUG|L.subscriptions |SERVER POOLED THREAD 3 |Unsubscribing from item MGOLD-F on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:16,244|DEBUG|L.subscriptions |SERVER POOLED THREAD 3 |Unsubscribing from item SILVER-F on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:38:16,244|DEBUG|L.subscriptions |SERVER POOLED THREAD 5 |Unsubscribing from item MSILVER-C on WLSTOCKLIST_REMOTE.WLQUOTE_ADAPTER
07-Dec-20 04:39:23,762|INFO |streamerMonitorText|Timer-1 |Total threads = 93, Total heap = 62914560 (free = 41810672), Sessions = 4 (max = 13, refused = 0), New sessions = [+3, -2], Connections = 4 (max = 18), New connections = [+10, -9], In-pool threads = 32, Active threads = 0, Available threads = 32, Queued tasks = 0, Pool queue wait = 0, NIO write queue = 0, NIO write queue wait = 0, NIO write selectors = 4, NIO total selectors = 16, Subscribed items = 12 (for 36 subscriptions), Inbound throughput = 0 updates/s (pre-filtered = 0), Outbound throughput = 0 updates/s (0.98 kbit/s, max = 50.97), Lost updates = 0 (total = 0), Total bytes sent = 26839721, Client messages throughput = 0 msgs/s (0 kbit/s, max = 0), Total messages handled = 0, Extra sleep = 0, Notify delay = 0

I have uploaded full log file in this link http://post.nammauzhavan.com/logs/Lightstreamer.log

As you can see from the log, the messages reporting received updates from the Data Adapter ("INCOMING DATA for ... ") disappear completely from 03:50:01,925; but the rest of the server activity continues regularly.
New client sessions are processed properly, as well as subscriptions and unsubscription requests; just no new data from the Data Adapter were received.

Please you should double check your Data Adapter code and your back-end source of the data to try to figure out where could be addressed the stoppage.

Regards,
Giuseppe

But when I restart the LS and adapter this getting run normally. This is too hard to find out the issue.

Indeed, in this case I would start the investigation from the initialization operations performed in the Adapters, since they seem to fix the issue.

Maybe you have a forever loop that once interrupted is not re-started?
Or a connection to an external service that as well is not restored following a failure?

Hello,
I have attached my full source code in this link http://post.nammauzhavan.com/logs/src.7z Could you please check and help me on this.

Hi rvkvino,

I have just taken a quick review of your code, and indeed I cannot provide a definitive answer but some tips to continue the investigation.
I think you should start by monitoring specifically the getJSON method, that if I am right, is called repeatedly to retrieve data updates from the backend.
I would add some logging in the method; I noticed that in the code you use System.out that should be ok if you have actually access to the console output of the running adapters process.
Just some basic text message in order to verify that the getJSON it is regularly called up for the entire life of the process.

Furthermore, just as a precaution I would add a generic catch to Exception, always in the getJSON method, because this could be the case where an unhandled exception stops the flow of data to the Lightstreamer server.

Regards,
Giuseppe

Hello,
As per your advice I have added the generic catch to Exception and update the adapter and now it's running. I will monitor 2 days and update the feedback.

I have been monitoring since last 10days but this didn't get any issue of stopping the rates. But got any issue like items not displaying in COMMAND mode. Some one items are missing from my adapter and not displaying in view page. This issue only happening nowadays.

This issue is not very clear to me.
Do you mean that some Items subscribed in COMMAND mode, once they are no longer updated from the back-end, also disappear in the client view? This would be unusual behavior that has no explanation.
Please could you detail the scenario a little more specifically?

Thank you,
Giuseppe