-
November 30th, 2020, 05:16 PM
#1
notifyNewSession getting called continuosuly in a session
So I am new to lightstreamer trying it on my local computer. What I observed while
debugging is it happens that notifyNewSession, notifySessionClose is getting called continuously in a session even if there is no internet fluctuation. My assumption after going through documents is when the client gets connected to server notifyNewSession will be called and when client ask to disconnect notifySessionClose will be called. It will keep connection active through the session. I am confused why it is behaving like this. Have I missed something in doc ? Or is it normal behaviour that it will continuously connect and disconnect even on a good internet connection.
-
November 30th, 2020, 05:28 PM
#2
In fact, notifyNewSession and notifySessionClose are not supposed to be invoked during the life of a session.
Something else must be happening, such as another client struggling to connect.
If you have left the factory log configuration, the log produced during the session life should show that.
-
December 3rd, 2020, 03:08 PM
#3
-
December 3rd, 2020, 03:10 PM
#4
Also one more issue I am facing today, while trying to deploy it locally, it was running fine yesterday.
But today I am facing this error continuosuly
|Unexpected error while managing the request:
java.lang.NoSuchMethodError: com.lightstreamer.interfaces.metadata.TableInfo.<i nit>(ILcom/lightstreamer/interfaces/metadata/Mode;Ljava/lang/String;Ljava/lang/String;IILjava/lang/String
V
at com.lightstreamer.i.b.c.<init>(c.java)
at com.lightstreamer.k.c.g.h(g.java)
at com.lightstreamer.k.c.f.f(f.java)
at com.lightstreamer.k.a.aa.a(aa.java)
at com.lightstreamer.k.a.z.b(z.java)
at com.lightstreamer.g.aw.a(aw.java)
at com.lightstreamer.g.c.i.a(i.java)
at com.lightstreamer.g.r.a(r.java)
at com.lightstreamer.g.r.a(r.java)
at com.lightstreamer.g.r.b(r.java)
at com.lightstreamer.g.r.a(r.java)
at com.lightstreamer.g.a6.a(a6.java)
at com.lightstreamer.e.a.ab.a(ab.java)
at com.lightstreamer.e.a.p.a(p.java)
at com.lightstreamer.e.a.p.a(p.java)
at com.lightstreamer.e.a.k.d(k.java)
at com.lightstreamer.a.a.m.b(m.java)
at com.lightstreamer.a.a.m.run(m.java)
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
at com.lightstreamer.a.a.d.c(d.java)
at com.lightstreamer.a.a.e.c(e.java)
at com.lightstreamer.a.a.b.run(b.java)
What could be possible reason?
-
December 3rd, 2020, 03:49 PM
#5
The signature is that of a previous version.
A possible reason for the error is that the Server in use is version 7.0.x or earlier and the adapter interface jar is for a later Server version.
Obviously, we assume that some change has happened involving the classpath.
For instance, you may have downloaded the latest version of the adapter interface jar from maven or from github and you have placed it before the older at Lightstreamer\lib\ls-adapter-interface.jar.
Similar Threads
-
By EWANG in forum Adapter SDKs
Replies: 5
Last Post: May 28th, 2018, 09:20 AM
-
By kpturner in forum Adapter SDKs
Replies: 2
Last Post: December 3rd, 2012, 09:34 PM
-
By stephenallred in forum Client SDKs
Replies: 1
Last Post: June 7th, 2010, 11:13 AM
-
By jweber in forum Client SDKs
Replies: 10
Last Post: February 10th, 2010, 09:25 AM
-
By CitiMan in forum Adapter SDKs
Replies: 8
Last Post: November 30th, 2006, 04:26 PM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 01:55 AM.
Bookmarks